Retire the #support channel.
Members press a button. Your team gets a queue, an AI that works it with you, and a transcript of every conversation.
brineshrimp opened #ticket-0413
A button opens a ticket. Your form fills it in.
Build panels visually: buttons or dropdowns, wired to ticket types you define. Multi-page forms collect what staff always have to ask for, before anyone says hello.
Forms with real fields
Selects, checkboxes, file uploads and validation, across multiple pages when one modal is not enough.
Abuse handled at the door
Per-member open limits, cooldowns and blacklists, so a bad night does not become forty tickets.
Channels or threads
Each ticket type picks its venue, with categories that overflow as you grow.
Every string yours
Rename, rewrite or translate anything the bot says, per server.
Report a bugmara claimed #ticket-0413
Staff work it like a queue, not a group chat.
The answers arrive up front. Claim it so nobody doubles up, keep notes members never see, and let Ticki draft the reply when the answer is already written down.
Claim and priorities
One owner per ticket, priority markers in the channel name, auto-unclaim when someone goes quiet.
Internal notes
Staff-only rows in the conversation. The member's transcript copy never contains them.
Discord or dashboard
Every control exists as a button, a slash command, and a dashboard action, under the same permissions.
Permissions that fit your roles
Staff groups map your Discord roles to exactly what each team may do, per ticket type if you want.
@brineshrimp thanks for the report. The team can see this channel; nobody else can.
Claimed. Checking the reward table now, this looks like the migration.
Only staff can see this note.
Draft reply ready: the payout cron was disabled during the update window.
#ticket-0413 closed · transcript ready
Every ticket ends as a receipt, not a deleted channel.
Closing generates a web transcript with the files preserved, DMs the opener their copy, and asks for a rating. Staff keep the full record; members get theirs.
Driftwatch · Ticket #0413
Report a bug · opened by brineshrimp · closed by mara · 41 messages
brineshrimp 4:20 PM
The /daily command hasn't paid out since the update.
screenshot.png · 412 KBmara 4:24 PM
Found it: the payout cron was paused during the update window. Fixed, and your streak is intact.
Attachments survive
Files are archived the moment they arrive, before Discord's links expire.
Staff notes stay staff-only
The opener gets their own copy of the record. Internal notes and edit history were never in it.
Download and keep
A single file that opens offline, with retention you set per plan.
Support that doesn't start at a panel, covered.
A DM becomes a modmail thread your team answers from a forum. And the AI is not an autocomplete: it works tickets to rules you set.
Modmail
A member DMs the bot and the conversation lands as a forum post with claim tags. Reply as yourself or anonymously; blocks and appeals are built in.
hey, I think my friend's account got compromised, who do I tell?
AI support, triage to frontline
You choose its reach per ticket type: sort and route quietly, draft for staff, or answer members from your knowledge base with the source named. It asks when it's missing something, never closes without the member's ok, and goes quiet the moment staff step in. Runs on our keys or yours.
if I boost the new server do I lose my perks here?
No: boosts are per server, so your perks here stay until your boost here lapses. Moving a boost means removing it from one server and adding it to the other.
Answered from the server guide: "Boosts and perks"
Paused: mara is replying. Staff can resume it with /ai resume.
Automation you can read at 3am.
Workflows are linear steps in plain language: a trigger, a condition, actions. SLA policies escalate on their own, and signed webhooks reach the rest of your stack.
Route billing tickets
enabled- whena ticket is openedstep ran
- ifthe form answered topic = "billing"step ran
- thenassign round-robin from the billing teamstep ran
- thennotify #billing-queuestep ran
- thenstart the 2-hour first-reply clockstep ran
run finished · 5 steps · all ok
Catch a missed deadline
enabled- whena first reply runs latestep ran
- thenbump the ticket's prioritystep ran
- thenping the on-call groupstep ran
run finished · 3 steps · all ok
Set up in an evening.
Three steps, no config files. The free plan asks for no card.
- step 1 of 3
Invite the bot
Sign in with Discord and add Ticki to your server. The setup wizard checks permissions and creates the channels it needs.
- step 2 of 3
Design your panel
Build the buttons and forms visually, with a live Discord preview that is the same renderer you saw above.
- step 3 of 3
Deploy it
One click posts the panel. From then on, every press opens a ticket your team works from Discord or the dashboard.
Common questions.
The free plan runs real tickets on a small server: two ticket types, a panel, transcripts, modmail. Paid plans raise limits and add AI allowance, SLAs and BYOK. Billing is per server, not per person.
Enough to create the ticket channels and read the conversations it mirrors: manage channels and roles within your ticket categories, plus message content for tickets and modmail. The setup wizard checks and explains each one.
On Ticki's servers, scoped to your server's staff. The opener gets a tokenized link to their own copy, which expires on a schedule you set and never includes staff notes.
If you let it. Its reach is a per-ticket-type setting: triage-only never speaks, assistant drafts for staff, frontline answers members from your knowledge base and asks clarifying questions. It names the article it answered from, never closes a ticket without the member confirming, and every message it sends carries a talk-to-a-human button. A staff reply pauses it immediately.
There is no importer, honestly. Old tickets stay where they are; you rebuild panels and types in the visual editor, which most servers finish in an evening. Both bots can run side by side while you switch.
Rename it, recolour embeds, and put your name on transcripts on paid plans. Running fully under your own bot token is a Business feature currently marked 'not shipped yet' on the pricing page, and it stays marked until every server can switch it on.
Plans
Give your members somewhere to press.
Free for small servers. Set up in the dashboard, deploy a panel, done.