Tickets that already hold the conversation and the customer. A server-managed clock that SLAs can trust. Macros, routing, and CSAT/NPS across WhatsApp, voice, and email — all over one API.
From a raised ticket to a measured resolution, in four steps.
A ticket can stand alone or hang off the conversation and contact that produced it, so an agent opens the thread and the customer, not a blank form.
First response, resolution, close, and reopen count are stamped by the API when you change status — never sent by hand. That is what makes SLA and CSAT reporting trustworthy.
First-match-wins routing assigns and tags the ticket; a macro sends a canned reply and applies its side-effects — set status, add tags, assign — in one action.
A survey link is minted after the conversation; the customer answers on a page you host, and CSAT/NPS statistics read back against the same lifecycle stamps.
Everything a support team needs, tied to the conversations and contacts it already has.
One unit of support work, optionally linked to its conversation and contact. You change status; the API stamps first_responded_at, resolved_at, closed_at and reopened_count — so the timeline cannot be gamed by editing a field.
Promise a response time and a resolution time, scoped to a priority or left as the catch-all. Deadlines compute against the server-managed stamps and against your business hours, and you can list exactly what is breaching right now.
Canned replies with {{placeholder}} variables that also set status, add tags, or assign a user. A tenant tag vocabulary. A first-match-wins routing engine with a dry-run evaluator so you test a rule before it goes live.
Mint a survey link after a resolution, host the response page yourself against public token endpoints, and read CSAT and NPS statistics back — tied to the tickets they came from.
WhatsApp, voice, email, and web chat all raise tickets against the same contact and timeline, so support is not four inboxes pretending to be one.
Create, filter, assign, and move tickets through their lifecycle programmatically with your cm_ key — the desk is automatable, not just clickable.
See how teams run measured support across verticals.
A return request on WhatsApp opens a ticket linked to the order thread. An SLA policy sets the resolution clock; the breach list surfaces it before the customer chases.
Result
No ticket ages out unseen.
Clinical questions escalate to a ticket with a priority-scoped SLA. Response and resolution stamps are server-managed, so the audit is real.
Result
Compliance-grade timestamps, not honour-system ones.
Macros answer the top FAQs and apply tags; routing sends the rest to the founder. CSAT runs on every resolution from week one.
Result
Support quality you can measure at seed stage.
Separate tenants per brand, each with its own SLA policies, tag vocabulary, and routing rules, all reporting CSAT/NPS the same way.
Result
Consistent measurement across brands.
Tickets, SLA policies, macros, tags, routing, and CSAT/NPS all use the same cm_ key as your LLM calls:
curl https://api.callmissed.com/api/v1/support/tickets \
-H "Authorization: Bearer cm_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"subject": "Refund not received", "priority": "high", "conversation_id": "33cc..."}'Create a ticket via REST API — the lifecycle clock starts server-side
Full field tables and scopes are in the Support Tickets, SLA Policies, Macros, Tags & Routing, and CSAT & NPS references.
Related products
The support desk is part of the same platform as the AI agents and the CRM, so a ticket already knows the conversation and the contact that produced it — nothing to integrate. And because agents handle the front line, tickets are the exceptions that need a human, not every message.
Free tier with 1,000 API credits. Tickets, SLAs, and CSAT from day one.