1 Like
Im underrated and if you guys could actually deliver i would be diamond now lol
1 Like
Of course, even such a simple addon as “Responds in” isn’t easy.
Time to make some decisions 
- A) Do we only look at the initial response or at every response in between as well?
e.g.
12:00 Richard sends PM to David
12:05 David responds
12:15 Richard responds
13:05 David responds
If the answer is yes then David’s response time is 5 minutes
If the answer is no then David’s response time is 27.5 minutes (avg of 5 and 50)
I think in the latter case we might be depending too much on external dependencies (such as a service being delivered) so I guess the answer is “initial response only” but I wanted to double check.
- B) in the above example, would this PM from Richard to David affect Richard’s response time as well or would only PM’s to Richard be considered?
If the answer is yes then Richard’s response time would be 10 minutes
If the answer is no then Richard’s response time would be n/a
Same, I assume the answer is no?
- C) good idea to take data from the past 30-60 days, do we also need a minimum amount of samples (i.e. we don’t display anything until there are at least 3 data points).
- D) another idea could be to remove outliers, for instance if we have data points 5, 5, 15, 15, 1000 then the average would be 347. If we remove the obvious weird 1000 then it would be 10.
Proposal is to keep the latter two in mind and implement only when we see weird results.
- E) People could be gaming this by sending PM’s back and forth between two friends, maybe we should adjust the weights to avoid that
(E.g. Goofy sends 10 PM’s to David and David responds within 1 minute each time, then Richard sends a PM to David and he takes an hour to respond. The average would be 10*1 + 1*60 = 70/11 = 6.4 but if we weigh per pair of users the average would be 1+70=35.5
I think we’re going to keep “initial response” only. Many times, users will chat up a storm with one person (thus skewing the data) and ignore ten other PMs they’ve received from others. So, the data will only count response time to new PMs.
5 Likes
And chat response times will not be possible, IMO. Once a chat is started with a user, it’s an endless thread (it never goes new in the system), so there’s no way to measure it.
-Collect first response time in the last 10 dms and make the average.
-Add a profile counter failed/successful tickets
Manually updated by admins^
It also depends on the buyer. If you message me 100 times without providing the necessary requirements that are stated on the topic, then the communication becomes poor and lengthy. I receive a significant number of messages from buyers that simply state “PM me” or “I need” without any further information. This is quite overwhelming. As a result, I often choose not to respond to such messages as in most cases, they are not serious buyers. However, not replying to such messages will negatively affect my “score”.
1 Like
Haha, good one.
1 Like
Thats not hard at all when you close ticket you can add it
I take credits for this idea, I demand 50 auto bump credits.
1 Like
Couldn’t agree more with you @OP . This was a gold mine before 2020, now it’s just resellers and a few genuine sellers. Just recently had bought monetised YouTube account only a month later to receive an email from YouTube that since no activity, unless I up the view to 4000h , ill be loosing monetisation until I reach those goals. In hindsight , what seller advertised was actually delivered, but it’s a far from what I paid the money for. Literally , 5 last attempts to buy something on here have ended up with disappointment, I mean even tried to deal with SWAPD team directly, in relations to crypto and was disappointed with the level of communication, especially since it was about substantial amount of money. Not pointing fingers, just stating what ive gone thru since 2018. Swapd is definitely moving towards something different than initial plan , unwillingly! Peace, love to all.
2 Likes
I’m not seeing the value in suggesting the ‘average response time’ feature, it feels unnecessary. Upwork has it because they lack a ‘last seen’ feature. When I message someone on Swapd, I often rely on their ‘last seen’ status to understand when they were last online, which gives me a sense of when to expect a response.
@SWAPD and the staff team gotta chill with taking every dumb suggestion so seriously. They should just pause for a sec and ask themselves if it’s really needed.
1 Like
Take responsibility for your research, choose reputable vendors, and put in effort to get quality goods. Quality comes at a cost.
1 Like
It would give a buyer a better idea of the seller they’re dealing with and what to expect to make a more educated buying decision. Yes you can be check their last seen but that doesn’t do much if the seller is just ignoring you lol.
I recently bought from a seller who dragged out the 7 day mentorship grace period by replying once per 24 - 36 hours, even though he was on the site all day. If i would have known he operated like that ahead of time i wouldn’t have bought from him.
2 Likes
I vote no on implementing avg response time.
I leave messages unread for a reason. Knowing if someone responds quickly provides little to no value in all reality. And the numbers could be skewered if a bunch of foreign people message someone in the USA in the middle of the night and vice versa.
What makes sense are service/thread based reviews.
2 Likes
Buyers need to make leaving bad reviews the culture across the platform. I posted about the taboo of leaving a bad review probably a year ago, if not longer. Most buyers don’t leave bad reviews because they do not want to jeopardize relationships and are afraid of seller retaliation.
If someone does a terrible job, or if you experience a bad service, leave a less than 5 star review.
5 Likes
Money Meg is my favorite
3 Likes