Feedback
Ask for a rating when a ticket closes: stars, thumbs or emoji, with an optional comment. Every rating feeds your statistics and the agent leaderboard.
Members open a ticket from your panel or a DM and stay in their inbox. Your team gets a tagged forum thread with their answers and payment details already attached. Clarify carries every reply between the two.
The member never leaves their DMs. Your team never leaves the forum. Clarify carries every message across and adds the context your team needs to answer.
A member picks a category on your panel, or simply sends the bot a DM.
A short form asks what this category needs: the Stripe order ID and what went wrong.
The member gets a “Ticket Opened” card in their DMs and keeps talking there.
Your team gets a tagged forum post with the member’s answers already on it.
Payment, customer and product from Stripe are on the thread before anyone replies.
Team replies arrive in the member’s DM. Their answers show up in the thread under their own name.
The member gets one card with the transcript, a reopen button and a rating.
Every module is optional. A short wizard sets it up, then it gets its own settings page in the dashboard, with the docs right next to every field.
Ask for a rating when a ticket closes: stars, thumbs or emoji, with an optional comment. Every rating feeds your statistics and the agent leaderboard.
Pass a ticket to another support tier: same ticket, same member, new team. Each handover carries a reason, tiers have their own budgets, and the next team gets an arrival card.
Every closed ticket keeps its full conversation on a transcript page. You decide who can open it, what it shows and where the link goes.
Schedules per category in your timezone, holidays included. Outside those hours members see a notice, a warning or a hard stop, whichever you choose.
Agents claim tickets, you assign them by hand, or Clarify distributes them per category. Tags and thread markers show at a glance who owns what.
Add an integration’s ready-made input to a category and the member’s order, subscription or membership is on the ticket the moment it opens. Lookups, refunds and payment links run as slash commands, right inside Discord.
Payment, customer and subscription are on the ticket as it opens. Send invoices and checkout links with /stripe; the card switches to paid as soon as Stripe confirms.
Create payment links from any ticket with /paypal. Clarify confirms the payment on its own when it arrives.
Look up payments and subscriptions, refund, pause or cancel them, and create checkouts without leaving the ticket.
The member’s tier appears on the ticket, matched through their linked Discord account. Nobody has to ask.
Turn a bug report into a GitHub issue with /issue, using your repository’s own issue templates.
Signed ticket events, sent to your own HTTPS endpoint. Verify the signature and react anywhere in your stack.
Connect your own shop, CRM or license server and its data appears on the ticket, right where your team works. You set it up by clicking, not coding.
Paste the endpoint of your shop, CRM or license server and add its credentials. Any JSON API works.
Run a test fetch, click the fields you want on the ticket, and Clarify builds the card blueprint for you.
Attach a connector to a category and it runs the moment a ticket opens, using the member’s Discord ID or their answers.
Credentials are encrypted at rest and never sent back to your browser. When you edit a connector, the field simply reads “leave blank to keep”.
Click the fields you need in your system’s response and Clarify posts them as a card on every ticket.
Start free with every module and integration. Go Premium when you want Clarify to run as your own bot.
No payment method required
Everything you need to run support on your server.
Server subscription in the Discord store
For communities that want Clarify under their own name.
Price and taxes are shown in the Discord store. Manage or cancel your subscription in Discord.