Glossary

The Discord webhook (named "Clarify Anonymous") that posts a member's message into the team's forum thread wearing the sender's own name and avatar — so the thread reads like a real conversation. See The middleman.

A data connector feature that recognises the member who opened the ticket and looks up their record for you automatically, with no ID to paste. See Discord auto-detect.

A reusable Discord "Components V2" template that Clarify fills with live data to build a result card or a panel. See Cards and placeholders.

The formatted message Clarify posts on a ticket to show looked-up data — a payment, a customer, a membership or your own connector data. Built from a blueprint.

A ticket type — such as billing, tech or reports — with its own fields, forum channel and embeds, so every ticket arrives pre-labelled. Also called a tag. See Categories.

The Stripe account you link to Clarify through Stripe Connect. Clarify stores only an account reference, never a Stripe key. See Stripe.

A no-code HTTP integration you build to pull information from your own shop, CRM or API and show it on a ticket. See Data connectors.

A Discord setting (User Settings → Advanced → Developer Mode) that lets you right-click a user, role or channel and Copy ID — needed whenever a field asks for a Discord ID.

A module that lets staff move a ticket to another support tier — same ticket, same customer conversation, new team — under the rules you set. See Escalation.

The team's view of a ticket: one thread inside a forum channel, holding the full conversation and context. See How Clarify works.

A built-in connection to an outside service — Stripe, PayPal, Tebex, Patreon or GitHub — for payment lookups and issue creation. See Integrations.

Fetching a member's record — a payment, customer, subscription or membership — and showing it on the ticket, either automatically on open or on demand. See Integrations.

Clarify's core idea: the bot sits between the member and your team, mirroring messages both ways so staff never DM from their personal accounts. See The middleman.

An optional feature you switch on and configure — Feedback, Transcripts, Escalation, Assignment or Opening hours. Each active module uses one feature token. See Modules overview.

A module with per-category schedules that decides what happens to a ticket opened outside your hours — a notice inside it, a warning first, or no ticket at all. See Opening hours.

A message with a button or dropdown that members click to open a ticket in a server channel. See Panels.

A %token% in a card or thread name — such as %amount% or %status% — that Clarify replaces with real data. See Cards and placeholders.

An extra security step (Proof Key for Code Exchange) used on some data-connector OAuth links to make sign-in safer. See Data connector security.

Another name for the middleman — Clarify passing messages between the member and the team.

A single support conversation: a member's DM or panel click on one side, a forum thread for your team on the other. See Tickets and modes.

A question a member answers when opening a ticket — text, a dropdown, a user/role/channel pick or a file upload — so tickets arrive complete. See Ticket inputs.

Where the customer's side of a ticket lives: DM Tickets (their DMs, mirrored into your forum — the default), Thread Mode (a private thread in a container channel) or Server Channels (a channel per ticket). See Tickets and modes.

The saved conversation of a ticket, opened from the Transcript button on the closing card by the ticket's participants and your server's administrators. See Transcripts.

Running Clarify under your own Discord bot application, so members see your brand instead of Clarify's. See White label.