What you can build against
Two entry points, aimed at different callers.REST API
For your own systems. Raise a ticket when a job fails, sync a reply into
your CRM, or move a conversation along when a customer upgrades.
MCP server
For AI agents. Let Claude or ChatGPT look through your queue, search your
reference documents, and prepare a draft reply for review.
The pieces
1
A workspace
One holds everything. Your team, tickets, reference documents, and API keys
all live here.
2
Channels
How conversations arrive. A chat widget, a contact form, an email address,
or the API. Run all of them at once if you like; they all land in one inbox.
3
Tickets
A single conversation with a single person. No subject line is needed. The
first message defines the ticket, and the requester is the identity.
4
Messages
public ones reach the customer on their original channel. internal
ones are notes for your team only. Neither the API nor the MCP server will
ever return an internal note.A note on what the AI can and cannot do
Read this before connecting anything, because the whole API surface follows from it. An AI agent on MCP can read your queue and write a draft. Sending is off the table. You cannot grant that as a permission: no send tool exists, and the only path from draft to real message goes through a person pressing send or through an automation gate. That means a connected agent cannot be manipulated into emailing your customers, not even by a hostile ticket body. The reasoning is written up here.Start here
Quickstart
Grab a key, open your first ticket. Five minutes, give or take.
Set up a channel
Put chat on your site, add a contact form, or forward a support address.