Ticket Vouches

What it does

If your server sells things or runs middleman deals, the vouch count is the trust signal. Ticket Vouches ties that count to real tickets: when a deal is done, the person who opened the ticket vouches the staff member who handled it.

One ticket is one vouch. A repeat customer who does five deals leaves five vouches, because each one is attached to a different ticket.

,vouch smooth deal, fast payout

The rules

• Only the ticket creator can vouch. Staff cannot vouch the customer, and nobody else in the ticket can vouch on the creator's behalf.
• The vouch always goes to the claimer. Whoever clicked Claim on the ticket is who gets vouched.
• One vouch per ticket, enforced by the database. Not by a cooldown that can be waited out.
• You cannot vouch yourself.

This is separate from ,vouch @user, the community reputation command. Both still work. ,vouches @user shows them side by side, like 12 deals · 3 community vouches, and ,vouches top deals ranks people by completed deals.

Suggested claimer

Sometimes a staff member handles a whole ticket and never clicks Claim. Without a claimer there is nobody to vouch, so the deal goes unrecorded.

With Suggested claimer on — it lives under Tickets → Claiming, since it is a ticket setting — exceed looks at who actually did the talking in that ticket, checks they are allowed to claim tickets there, and offers them:

Nobody claimed this ticket, so I looked at who actually handled it.

mm_alex sent 34 messages here.

[ Confirm ]  [ Pick someone else ]

The suggestion is never applied silently. The creator confirms it, or picks from a list of everyone else who worked the ticket. Vouches recorded this way are flagged internally as suggested, so you can tell them apart from real claims.

With the toggle off, an unclaimed ticket simply cannot be vouched, and the creator is told why.

When people get asked

If Ask on close is on, the creator gets a DM with a button when their ticket closes. Ticket channels are deleted on close, so this is how a vouch still gets left afterwards. The window defaults to 48 hours and is configurable.

Stopping fake vouches

These vouches are worth money to the people receiving them, so there are guards:

• Minimum ticket age rejects vouches on tickets younger than a set number of seconds, which kills the trick of opening a ticket and instantly vouching yourself a friend. Off by default.
• Require a comment forces the customer to write something rather than click through.
• ,vouch remove <id> (needs manage_guild) takes a vouch back. It is a soft delete: the record stays, the count drops, and the ticket cannot be re-vouched afterwards, so nobody can quietly swap a bad vouch for a good one.

Setting it up

Open your server in the dashboard, go to Tickets — Vouches, and switch on Ticket vouches. Set a vouch channel if you want each one announced publicly. The Suggested claimer switch is on the main Tickets page under Claiming.

Everything else is optional, but on a MM server two settings are worth a look straight away: turn on Require a comment, and set Minimum ticket age to something realistic for how long your deals actually take.