Customer verification
Control who can open Customer support tickets. Four methods — pick the one that fits your sales flow.
Role verification
The simplest method. A user must already hold a specific Discord role in your server to open a Customer ticket. Assign the role manually, via another bot (e.g. Tebex webhook), or through Discord's built-in role award systems.
- 1In your category settings, set Track to Customer.
- 2Under Verification, select Role.
- 3Pick the Discord role that represents a verified customer.
- 4Save. Users without that role see an error when they try to open a ticket.
Manual verification
Staff review and approve each customer request manually. When a user requests access, a ticket is created in a private intake channel. A staff member clicks Approve or Deny. Approved users receive the customer role.
- 1Set verification method to Manual in your category settings.
- 2Configure a staff intake channel where requests appear.
- 3Optionally set an intake form to collect proof of purchase.
- 4Staff approve/deny from the ticket or from the dashboard.
Email verification
The user enters an email address. Tixora sends a one-time code. On successful verification the configured role is assigned. Useful for license-key or newsletter-based access control.
- 1Configure an outbound email provider in workspace Settings.
- 2Set verification method to Email in category settings.
- 3Optionally map email domains to specific roles.
- 4The bot DMs the user a verification link valid for 15 minutes.
API / Webhook verification
Your own backend decides whether to grant access. When a user requests a Customer ticket, Tixora POSTs to your verification endpoint with the user's Discord ID. Your server returns approved or denied. Compatible with Tebex, Gumroad, Stripe, and any custom billing system.
- 1In workspace Settings → Verification API, register your endpoint URL and signing secret.
- 2Tixora sends a signed POST with { discordId, guildId, categoryId, timestamp }.
- 3Your server responds with { approved: true } or { approved: false, reason: "..." }.
- 4On approval, the role is assigned and the ticket is created automatically.