I can see the comments in the PMs in the upcoming weeks:
Buyer: WHY is your success ratio so low bro?
Seller: Bro tHaT WaS jUsT fRom oNe bAd SeRvIcE bRo sWaPD plUGin StupID NoT cONNecTed to thREADS.
If you want to be considered a good seller, do good, and do good ALL THE TIME.
Waiting for this update.
I simply cringe looking at some sellers ticket history, all cancelled stuff, meanwhile he/she is opening 4 more tickets with a claimed 99% success rate. This plugin will stop (or severely limit) this from now on! If you consider that useless, YOU ARE GAY!
Amazing feature
Thank you sir @Swapd
Users rn
Great Feature @SWAPD Ignore The Haters!
There might be a workaround to link historical tickets to sales threads, at least for a large portion of them.
It depends on how the data is structured on the backend, but hear me out @SWAPD.
Here’s a visual breakdown of the idea
[ Public Sales Thread by SellerX ]
│
▼
[ Buyer clicks on SellerX's profile ]
│
▼
[ Buyer clicks "Message" ]
│
▼
[ Message auto-includes public thread URL ]
│
▼
[ Buyer sends DM with auto-included link ]
│
▼
[ Seller replies, Deal made → Checkout started from message thread ]
│
▼
[ Ticket Created ]
│
▼
[ Checkout Bot includes link back to sales thread ]
There are some limitations to this:
Possible solution to avoid “Cross-thread confusion”: Add a validation check to ensure the linked thread was originally posted by the same seller as the one involved in the ticket.
Even if not universally applicable, this approach would allow us to measure the success rate of sales threads where:
For tickets that can’t be traced to a specific thread, they could still contribute to the seller’s general success rate on their profile.
For tickets that can be traced, we could introduce a per-thread success rate, giving buyers more insight and allowing credible sellers to shine in the areas they’re strongest.
Here’s a visual breakdown of the idea
┌──────────────────────────────────────────────┐
│ Sales Thread X – “Some Service” │
├──────────────────────────────────────────────┤
│ 🔁 Total Transactions: 120 │
│ ✅ Successful Deliveries: 102 │
│ ❌ Failed/Disputed: 18 │
│ 📈 Actual Success Rate: 85% │
└──────────────────────────────────────────────┘
Moving forward, when a ticket is opened, the seller should link the relevant sales thread.
This will make the ticketing process more structured, reduce ambiguity, and improve tracking across services.
–
Introduce a Seller Ticket History section that publicly displays selected metrics from past transactions, without revealing private details.
This can be accessed directly from the seller’s profile, alongside the global success rate feature that’s currently being rolled out.
If a seller’s overall success rate appears low, but it’s due to offering services with inherently low success rates, this breakdown will make that clear, and no excuses can be made up, providing important context and transparency.
Conversely, if a seller is consistently failing tickets that were expected to have high success rates, this helps buyers spot potential red flags.
What could be shown:
Date of ticket
Ticket success rate (as reported at the time)
Final outcome (whether it succeeded or failed)
Optional: Deal value, promised timeline, actual timeline
A seller with a low success rate for one service but strong delivery elsewhere shouldn’t be penalized across the board.
Transparency helps build trust, and lets serious sellers stand out.
Could look something like this
┌────────────────┬────────────────────┬────────┬──────────────────┬────────────────────┬────────────────┐
│ Date Started │ Ticket Success Rate│ Value │ Promised Timeline│ Actual Timeline │ Outcome │
├────────────────┼────────────────────┼────────┼──────────────────┼────────────────────┼────────────────┤
│ Apr 4 │ 90% │ $500 │ 5 days │ On-time │ ✅ Success │
│ Apr 2 │ 70% │ $300 │ 3 days │ 2 days late │ ❌ Failed │
│ Mar 30 │ 95% │ $750 │ 7 days │ 1 day late │ ✅ Success │
│ Mar 27 │ 85% │ $400 │ 4 days │ 2 days early │ ✅ Success │
│ Mar 24 │ 80% │ $220 │ 2 days │ 3 days late │ ❌ Failed │
│ Mar 20 │ 92% │ $600 │ 6 days │ On-time │ ✅ Success │
│ Apr 5 │ 88% │ $480 │ 5 days │ In progress │ ⏳ In Progress │
└────────────────┴────────────────────┴────────┴──────────────────┴────────────────────┴────────────────┘
These are just my thoughts on how things could be best implemented. What are your thoughts?
Less than 15% of people use the checkout button within PMs, they mostly go directly to /start. So while your idea is solid, its not worth dumping money into.
What about this approach
That sounds cool actually. May consider it for future updates. For now, SWAPD devs are booked for a line of things we’ve already agreed on, I don’t want to add to their workload (and what you are proposing sounds time extensive to develop). We are six months behind on stuff we’ve promised, and April is the month where we catch up. After that, devs move onto our Lusty.com project :)
Thanks for suggestions though, saving it in our maybe jar for the next line of updates.
Sounds good!
I do think this small change could still be added, that way, if you ever decide to display success rates per sales thread in the future, the data will already be properly structured to support it.
THE SUCCESS PLUGIN IS LIVE! Refresh and post your success ratio! As expected, staff is receiving a ton of complains, from sellers!
@swapd Top sellers showing around 50% success rates is kinda funny. 
63% ain’t bad :D
SAD you mean!
We have received a report that in some (one) case, not all tickets were counted. We’ve contacted the devs, but if I had to guess, it’s because things are still being counted (the plugin has only been live for one hour). Stats update every 24-48h.
This happens when you change your username your old sales and tickets basically disappear. So anyone who’s switched names won’t have their past activity showing. Bit of a flaw in the new tool, but should be fixable since most people don’t really change usernames anyway.
