Niches · Customer support & helpdesk
Classify, tag, prioritise and route new tickets
Two or three companies' docs show a full fit.
What counts as done
Each new ticket has tags, priority and assignee or group set by a call that changed only those fields, and a note or log says why.
Measured, for our own tests: the fields are set within 60 seconds of creation. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: tag and prioritise everything that came in overnight
, route billing tickets to the billing team
, apply the refund macro to this ticket
, flag angry customers
Does the job 3
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Gorgias API + MCP C Gorgias Inc. | MCP update_tickets sets status, priority and assignee and adds tags in one call for one or many tickets, and apply_macro applies a macro; REST Update a ticket covers the same fields. Rate limit is 40 requests per 20 seconds. source |
| HelpDesk D Text, Inc. | A tickets.create webhook fires on new tickets, and one PATCH sets status, priority, teamIDs, tagIDs, assignment and a private message with the reason. Macros and rules are listable; PATCH also accepts an actions array. source |
| Zendesk Support API B Zendesk, Inc. | zen:event-type:ticket.created webhooks fire on new tickets, one PUT /tickets/{id} sets status, priority, assignee, group and tags, and GET .../macros/{id}/apply previews a macro's changes; acc-35 shipped that two-step apply. source |
Does the job, with a limit 18
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 | Webhooks on new messages and conversations are on every plan, and tags, notes and assignment are tools, but each is a separate call, tags need a paid plan, assign-conversation toggles, and there is no priority. source |
| Chatwoot API D Chatwoot Inc. | conversation_created and message_created webhooks exist, but priority, labels, assignee and status are separate calls (Update Conversation, Add Labels which overwrites, Assign, Toggle Status). Canned responses are listable; no macro-apply endpoint. source |
| Crisp API + MCP D Crisp IM SAS | message:send and session events reach web hooks, but segments (Update Metas), routing assignment, inbox and state are separate PATCH calls, Crisp has no priority field, and no macro apply exists. source |
| Dixa D Dixa ApS | Tags (bulk), custom attributes and queue transfer are separate calls, Dixa has no priority field in the conversation API, and templates can be listed but not applied. Outbound webhooks exist; the event list was not read. source |
| Drag E DragApp.com Ltd | MCP adds labels, moves threads between columns (bulk too) and update_card sets assignee and due date, each a separate call; automations can be toggled, not run, there is no priority, and no webhook is documented, so an agent must poll. source |
| FreeScout F FreeScout | convo.created webhooks fire and Update Conversation sets status, assignTo and mailbox, but tags are a separate call, FreeScout has no priority field in the API, and there is no saved-reply or workflow apply call. source |
| Freshdesk API + MCP D Freshworks Inc. | Update a Ticket sets status, priority, group, agent and tags in one call and bulk_update exists, but scenario automations can only be listed, new-ticket webhooks come from admin automation rules, and MCP allows 1,200 actions a year on Growth. source |
| Front API + MCP BB FrontApp, Inc. | inbound_received application webhooks fire on new mail, and PATCH /conversations/{id} sets assignee_id, status_id, tag_ids and custom_fields in one call, but Front has no priority field and rules can be listed, not applied. source |
| Gladly C Gladly Software, Inc. | MESSAGE_RECEIVED and conversation events reach webhooks, and PATCH conversation sets assignee and status in one call, but topics are separate calls, there is no priority field and no macro or answer apply endpoint. source |
| Help Scout API + MCP B Help Scout PBC | convo.created webhooks fire on new conversations and manual workflows can be run by API, but tags, status and assignee are separate calls (Update Tags, JSON Patch per field), and each write counts double against the rate limit. source |
| Intercom API + MCP BB Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland) | conversation.user.created and ticket.created webhooks exist, but tags, assignment and attributes are separate calls; macros can be listed and read, not applied. A run-assignment-rules call can route by the workspace's own rules. source |
| Kustomer D Kustomer, LLC | PUT /v1/conversations/{id} sets status, priority 1 to 5, assigned users and teams, queue and tags in one call, and outbound webhooks exist, but no shortcut or macro apply endpoint was found and updates are capped at 100 per object per 10 minutes. source |
| LiveAgent D Quality Unit, s. r. o. | MCP has add_tags_to_ticket, assign_ticket, transfer_ticket and set_ticket_field_value, each a separate call, with no priority or macro tool; a new-ticket webhook was not found in what was read. source |
| Missive API + MCP C Heliom Inc. | PATCH /v1/conversations assigns, labels, moves to a team and closes in one silent call, but Missive has no priority field, and new-message webhooks come from admin-built rules on Productive or Business, not an API subscription. source |
| Plain API + MCP B Not Just Tickets Ltd | Thread created webhooks fire, and assignment, labels, priority and thread fields are each their own mutation, so one triage is several calls. Snippets are readable; no macro apply was found. source |
| Pylon API + MCP C Pylon Labs, Inc. | PATCH /issues/{id} sets state, assignee, team, tags and custom fields in one call (bulk for 100), but macros can be listed, not applied, and new-issue events come from triggers built in Pylon rather than a webhook subscription API. source |
| Zammad E Zammad GmbH | PUT /api/v1/tickets/{id} sets group, owner, state and priority, but tags use a separate call, no macro endpoint appears in the API docs, and webhooks are fired by triggers set up in the admin UI. source |
| Zoho Desk B Zoho Corporation Private Limited | Ticket_Add webhooks and Update Ticket (status, priority, assignee, department, fields) exist, plus updateMany, but webhooks need Professional or higher and no macro or canned-response apply operation is in the OpenAPI files. 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 lists, tags, prioritises or assigns conversations; the server covers bots, AI agents, knowledge, channels and integrations. source |
What stops agents finishing
- per-ticket update cap such as 30 updates per 10 minutes per user
- no webhook for new tickets on the plan, so the agent must poll
- metered action allowance on MCP such as 1,200 calls a year
Around it
Before: support.webhook-on-new, decision-models.classify. After: support.draft-reply-for-review, support.handoff-to-person, messaging.slack-notify.
Where this comes from
Weight 18 of 100 in Customer support & helpdesk: 9 of 42 accounts (acc-04, 11, 12, 16, 35, 37, 39, 40 and the Chatwoot bot-assignment PR); second most described, mostly through n8n and in-house tools
The same as data: /api/v1/use-cases/support.triage-and-route.json, or the MCP tool get_use_case with id support.triage-and-route. 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.