# Answer customers directly and escalate the rest

> Answer customers directly and escalate the rest: 1 companies fully do it, 9 with a limit, 21 carry the tag. Every listing in Customer support & helpdesk with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/support.autoresolve-with-escalation/
- Markdown: https://www.anchorterminal.com/niches/support.autoresolve-with-escalation/index.md (~1,900 tokens)
- Slim: https://www.anchorterminal.com/niches/support.autoresolve-with-escalation/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/support.autoresolve-with-escalation/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 9 | 21 | 15 | 7 |

## What counts as done

Within the first response the customer gets an answer or an explicit handoff, every unanswered conversation reaches a person's queue with status open and a summary, and the share resolved without a person is reported.

How agents ask for it: answer common questions before a person sees them; let the bot handle level-0 and hand the rest to us; deflect password resets

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Gorgias API + MCP (Gorgias Inc.)**: MCP tools change AI Agent tone, handover topics and per-channel enablement, preview it in test sessions, and report outcomes and handover patterns. Billing is $0.85 to $1.00 per automated interaction.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Chatway MCP (Poptin Ltd)**: The README pairs webhooks with an outside agent that answers through send-message, and handoff-to-human hands a conversation from Chatway's AI assistant to people, but MCP-handled conversations count toward a monthly cap (50 on Free) and nothing reports resolution share.
- **Chatwoot API (Chatwoot Inc.)**: An outside agent can run as an Agent Bot on an inbox; since PR 14870 (merged 2026-08-07) bot assignment sets pending and human assignment opens. Captain has no API in the Swagger, and acc-28 reports every custom tool reaching every assistant.
- **Crisp API + MCP (Crisp IM SAS)**: An outside agent can answer by REST and assign routing, and Crisp's own AI agent can be given tools through the Hugo MCP API, but no endpoint to configure, pause or report on its resolutions was found.
- **Dixa (Dixa ApS)**: GET /v1/ai-agents lists Mim and external chatbot agents, and queue transfer hands a conversation on, but nothing configures, pauses or reports on Mim through the API.
- **Intercom API + MCP (Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland))**: Fin Agent API has ask, reply, run procedure and escalate, and escalation sets ai_agent.resolution_state. Access is by request, Fin bills $0.99 an outcome, and acc-03 reports customers unable to reach a person.
- **Kustomer (Kustomer, LLC)**: The AI API lists AI automations, runs evaluations and returns AI summaries, but no endpoint to change, pause or hand off a customer-facing agent was found; AI Agents for Customers cost $0.60 an engaged conversation.
- **Landbot MCP server (Landbot)**: The server builds the customer-facing agent itself: create_ai_agent, knowledge sources, REST API actions and publish_ai_agent, under agents:read and agents:write scopes. Handoff states and resolution reporting are not covered.
- **Plain API + MCP (Not Just Tickets Ltd)**: The Customer Agent answers, then on handoff sends a message, unassigns itself and never continues, with a workflow trigger on handoff and a knowledge-gaps API. Its settings are documented as UI pages; no API to configure or pause it was found.
- **Pylon API + MCP (Pylon Labs, Inc.)**: Pylon's AI Agent runs on issues, and MCP exposes list_agents, variations, backtests and playground, but no tool to change, pause or hand off from an agent was found; settings are built in the app.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **LiveAgent (Quality Unit, s. r. o.)**: The tools reference shows LiveAgent AI agents can be given selected MCP tools and authored messages carry the ai_agent type, but handoff behaviour and resolution reporting were not found in what was read.

- not this job: Drag (DragApp.com Ltd): No customer-facing AI agent that answers and hands off appears in the MCP or REST docs; Drag's AI drafts and summaries assist agents, and toggle_ai_drafts is the only AI control.
- not this job: FreeScout (FreeScout): FreeScout has no customer-facing AI agent and the API has nothing for one; an outside agent would have to publish replies itself with no bot-owned state.
- not this job: Freshdesk API + MCP (Freshworks Inc.): The API reference has no endpoint for Freddy AI Agent settings, handoff or resolution reports; an outside bot (acc-19) must reply through the ticket API itself with no bot-owned state.
- not this job: Front API + MCP (FrontApp, Inc.): No endpoint or MCP tool configures, pauses or reports on Autopilot, and Front has no bot-owned status; an outside agent would have to send replies itself with the send scope.
- not this job: Gladly (Gladly Software, Inc.): The reference covers public answers search and messaging, but nothing configures, pauses or reports on Gladly's AI agent, and there is no bot-owned conversation state.
- not this job: Help Scout API + MCP (Help Scout PBC): The Inbox API endpoint list has nothing to configure, pause or report on AI Answers, and no bot-owned status; an outside agent would have to publish replies itself.
- not this job: HelpDesk (Text, Inc.): The Ticketing API has nothing to configure, pause or report on an AI agent and no bot-owned status; an outside agent would have to reply itself.
- not this job: Missive API + MCP (Heliom Inc.): Missive has no customer-facing AI agent in the API or MCP docs, and no bot-owned conversation state; an outside agent would have to send through drafts with send true.
- not this job: Zammad (Zammad GmbH): The API docs list no endpoint for a customer-facing AI agent, its settings or handoff; Zammad's AI functions reached through the API are ticket summaries.
- not this job: Zendesk Support API (Zendesk, Inc.): The Support API reference has no endpoint to configure, pause or hand off from Zendesk's AI agents, and no bot-owned status; an outside agent would have to post public comments itself.
- not this job: Zoho Desk (Zoho Corporation Private Limited): The OpenAPI files expose IM bots read-only (get and list) and nothing to configure, pause or report on Zia or a customer-facing AI agent.

## What stops agents finishing

- customer cannot reach a person after asking
- per-resolution pricing with no cap
- vendor agent configured only in the UI, nothing for an outside agent to call

## Around it

Before: knowledge.ingest, chat.widget-message. After: support.handoff-to-person, support.summarise-and-report.

## Where this comes from

Weight 15 of 100 in Customer support & helpdesk: 7 of 42 accounts (acc-01, 02, 03, 19, 28, 36, 37); strongest numbers in the set (two thirds of questions on Fin) and the strongest complaints

As data: https://www.anchorterminal.com/api/v1/use-cases/support.autoresolve-with-escalation.json, or the MCP tool get_use_case with id support.autoresolve-with-escalation. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
