Niches · Customer support & helpdesk
Hand a conversation to a person with context
Four or more companies' docs show a full fit.
What counts as done
The conversation has a human assignee or team, status open or pending as the helpdesk expects, priority set, and an internal note with the summary, and the bot no longer replies on it.
Measured, for our own tests: this takes one or two calls. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: escalate this to a human
, assign to Sam with a summary
, mark this urgent and put it in the billing queue
, take this back from the bot
Does the job 8
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Freshdesk API + MCP D Freshworks Inc. | One Update a Ticket call sets responder_id, group_id, priority and status, and Create a Note (private by default) adds the summary. Freshdesk has no bot owner to clear. source |
| HelpDesk D Text, Inc. | One PATCH /v1/tickets/{id} sets assignment, team, status and priority and adds a message with isPrivate true carrying the summary. source |
| Intercom API + MCP BB Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland) | POST /fin/escalate hands the conversation to a human, summarises it and opens it in the team inbox by default; the assign call sets an admin or a team, and a note is one more call. source |
| Kustomer D Kustomer, LLC | One PUT sets assignedUsers or assignedTeams, queue, status and priority, and Create note within conversation adds the summary as a second call. source |
| Pylon API + MCP C Pylon Labs, Inc. | PATCH /issues/{id} sets assignee_id, team_id and state in one call and /note adds the summary in a second. source |
| Zammad E Zammad GmbH | One PUT on the ticket sets owner, group, state and priority and can carry an article with internal true and type note, so assignment and summary land in one call. source |
| Zendesk Support API B Zendesk, Inc. | One PUT /tickets/{id} sets assignee, group, priority, status and adds a comment with public false. Zendesk has no separate bot ownership, so nothing is left to clear. source |
| Zoho Desk B Zoho Corporation Private Limited | Update Ticket sets assigneeId, departmentId or team, priority and status in one call, and Create ticket comment with isPublic false adds the summary. source |
Does the job, with a limit 13
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.
| Listing | Why |
|---|---|
| Chatway MCP C Poptin Ltd | handoff-to-human, assign-conversation and add-note cover it, but assignment toggles so a repeat unassigns (check assigned_agents first), and there is no priority field. source |
| Chatwoot API D Chatwoot Inc. | Assign sets assignee_id or team_id, and the merged PR 14870 opens the conversation and clears the bot on human assignment; reviewers found races with Captain and auto-assignment. Priority and the private note are further calls, so three calls, not two. source |
| Crisp API + MCP D Crisp IM SAS | PATCH routing assigns an operator, PATCH state sets unresolved or pending, and a note adds the summary: three calls, with no priority field and no bot ownership state. source |
| Dixa D Dixa ApS | PUT transfer/queue moves the conversation to a team queue, claim assigns an agent, and a note adds the summary, but that is three calls with no priority field. source |
| Drag E DragApp.com Ltd | update_card sets an assignee and move_thread changes the column, with add_comment for the summary: three calls, no priority field. source |
| FreeScout F FreeScout | Update Conversation sets assignTo and status, and Create Thread adds a note, two calls, but there is no priority field. source |
| Front API + MCP BB FrontApp, Inc. | assign_conversation and add_comment do it in two calls, and a conversation has one assignee. There is no priority field and no bot-ownership state to clear. source |
| Gladly C Gladly Software, Inc. | PATCH conversation sets assignee and status together and a note adds the summary, two calls, but Gladly has no priority field. source |
| Gorgias API + MCP C Gorgias Inc. | update_tickets sets assignee, priority and status and add_internal_note adds the summary in two calls, but how AI Agent ownership clears on human assignment is not documented in the tool list. source |
| Help Scout API + MCP B Help Scout PBC | JSON Patch on the conversation sets assignTo and status, and Create Note adds the summary, but Help Scout has no priority field and patches go one field at a time, so it is more than two calls. source |
| LiveAgent D Quality Unit, s. r. o. | assign_ticket or transfer_ticket plus add_note does it in two calls, but there is no priority tool and how an AI agent's ownership ends was not documented in the reference. source |
| Missive API + MCP C Heliom Inc. | PATCH /v1/conversations assigns users or a team and reopens, and a post adds the summary as a second call, but there is no priority field. source |
| Plain API + MCP B Not Just Tickets Ltd | Assignment, status, priority and notes are separate mutations, so it is three or four calls; the Customer Agent unassigns itself on handoff, so bot and person don't both own the thread. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Landbot MCP server E Landbot | No tool assigns a conversation to a person or sets its status; any handoff must be built into the bot flow. source |
What stops agents finishing
- assignment call toggles rather than sets, so a repeat unassigns
- bot and person can both own the conversation
- no status value for bot-owned work, so handed-off tickets sit in the main queue
Around it
Before: support.autoresolve-with-escalation, support.triage-and-route. After: messaging.slack-notify.
Where this comes from
Weight 8 of 100 in Customer support & helpdesk: 5 of 42 accounts (acc-01, 03, 28, 36, 37); low count because accounts fold handoff into other jobs, held at 8 because it is a buyer check
The same as data: /api/v1/use-cases/support.handoff-to-person.json, or the MCP tool get_use_case with id support.handoff-to-person. Other jobs in this category: /api/v1/niches?category=support.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.