Docs/Verification
Guide

Customer verification

Control who can open Customer support tickets. Four methods — pick the one that fits your sales flow.

Role verification

All plans

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.

  1. 1In your category settings, set Track to Customer.
  2. 2Under Verification, select Role.
  3. 3Pick the Discord role that represents a verified customer.
  4. 4Save. Users without that role see an error when they try to open a ticket.

Manual verification

All plans

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.

  1. 1Set verification method to Manual in your category settings.
  2. 2Configure a staff intake channel where requests appear.
  3. 3Optionally set an intake form to collect proof of purchase.
  4. 4Staff approve/deny from the ticket or from the dashboard.

Email verification

Pro+

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.

  1. 1Configure an outbound email provider in workspace Settings.
  2. 2Set verification method to Email in category settings.
  3. 3Optionally map email domains to specific roles.
  4. 4The bot DMs the user a verification link valid for 15 minutes.

API / Webhook verification

Business+

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.

  1. 1In workspace Settings → Verification API, register your endpoint URL and signing secret.
  2. 2Tixora sends a signed POST with { discordId, guildId, categoryId, timestamp }.
  3. 3Your server responds with { approved: true } or { approved: false, reason: "..." }.
  4. 4On approval, the role is assigned and the ticket is created automatically.