Auto-Assist (AI ticket helper)

An AI co-worker that reads incoming ticket messages and either auto-replies from your server's knowledge base or escalates to a human. Cuts the routine "I can't change my password" / "how do I link my account?" tickets off your staff queue.

Free during early access

Auto-Assist is positioned as a premium feature at launch, but it's free during Phantom's early-access period. Nothing to top up or maintain — just enable it and use it. See Pricing & early access for what changes at launch.

How it works

1. A member opens a ticket; their first message lands.
2. Auto-Assist reads the message + your knowledge base (server-specific FAQs you've uploaded).
3. It decides: reply (it's confident enough to answer), ask_for_info (it needs one more piece of info from the user), offer_close (the user signalled the issue is resolved), or escalate (it can't help; staff please look).
4. On reply, it posts the answer in the ticket as the bot. On escalate, it pings your configured staff role.

Auto-Assist's answers are written by an AI model picked for fast support replies. You don't manage the model — Phantom handles it.

Where it lives

Dashboard: Tickets → Settings → Auto-Assist (global toggle) + per ticket type (knowledge base + behavioural overrides).

Setup

1. Open the ticket type you want Auto-Assist on.
2. Enable Auto-Assist for that type.
3. Upload one or more knowledge bases — markdown documents containing your FAQs / SOPs / known answers.
4. Pick a staff role to ping on escalation.
5. Save.

The next time a member opens a ticket of that type, the bot reads their message and acts.

Knowledge bases

A knowledge base is a markdown document up to several thousand words long, scoped to your server. Phantom indexes the knowledge base on save and pulls the most relevant sections for the question being asked, so answers cite the right policy.

Good knowledge bases:

• Concrete answers, not pointers ("To reset your password, go to X" not "See our password reset page")
• Written in your support team's voice
• Updated when your processes change
• Cover the 80% of repeat questions, not every edge case

You can have multiple knowledge bases per ticket type — useful for "general policy" + "this specific game's rules" + "billing FAQ" as separate documents.

What it can't do

• Take actions in your server (it only posts replies, never bans / kicks / changes roles)
• Reach into other tickets (each ticket is isolated)
• Look up real-time info (it only knows what's in the KB)
• Replace your team for anything non-routine

Costs

During early access: nothing. Auto-Assist is free to use as much as your server wants.

Launch pricing is still being decided and will be announced ahead of any change. Until then, there's nothing to top up or maintain.

Tuning behaviour

Two settings per ticket type:

• Escalation threshold — how confident the AI has to be before replying. Higher = escalates more often; lower = answers more often (more false confidence risk).
• Max turns — how many back-and-forths before forced escalation. Default 3. Keeps the AI from looping forever.

Audit pane

Each ticket type's settings has a Phantom AI audit view. Shows every AI reply with confidence score, the knowledge-base section it referenced, and the user message that triggered it. Useful for debugging "why did it reply with X?"

Permissions

• tickets.view — see Auto-Assist settings + knowledge bases
• tickets.edit — toggle, upload KBs, change behaviour

Privacy

• Ticket messages are never used to train any AI model.
• Knowledge bases are stored encrypted, scoped to your server only.
• No cross-server data ever flows between knowledge bases.

Limits

• Knowledge base: up to a few hundred KB of content per server (the dashboard shows your current usage).
• 12 turns of conversation history per ticket retained as context for the AI.
• A per-server rate limit applies so one busy server can't crowd out others.

Related pages

• Tickets overview
• Panels & types
• Pricing & early access — current status + launch billing