Niches · Customer support & helpdesk

Draft a reply a person sends

Four or more companies' docs show a full fit.

9companies, full fit
12companies, fit with a limit
21companies carry the tag
20share of the category's work
10first-hand accounts

What counts as done

A draft or private note containing the reply is on the ticket, nothing has been emailed to the customer, and the person can send it from the helpdesk with one action.

Measured, for our own tests: the draft or note is on the ticket within 30 seconds of the trigger. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: draft a reply to this ticket, write a response for me to check, suggest an answer and leave it on the ticket, answer this in my voice but don't send it

Does the job 9

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

ListingWhy
FreeScout F
FreeScout
Create Thread takes state draft (default published), so a reply thread can be saved unsent for an agent to send; type note gives an internal note instead. Needs the paid API & Webhooks module. source
Front API + MCP BB
FrontApp, Inc.
create_draft (MCP) and POST /conversations/{id}/drafts store a reply that does not send; send_message needs the separate send scope, and the person sends the draft from Front. add_comment is the internal-note route. source
Help Scout API + MCP B
Help Scout PBC
Create Reply Thread with draft true stores a draft reply that sends nothing and leaves the owner unchanged until a person publishes it. This needs the REST Inbox API; the MCP server is read-only. source
Kustomer D
Kustomer, LLC
POST /v1/customers/{id}/drafts saves an outbound draft with status draft; it sends only with sendAt now or a scheduled time, and note drafts are also supported. Keys carry only the roles granted. source
Missive API + MCP C
Heliom Inc.
POST /v1/drafts stores a reply unsent unless send true is passed, and the MCP server separates Create drafts from Send messages so a connection can draft without being able to send. source
Plain API + MCP B
Not Just Tickets Ltd
Suggested replies (generatedReply:create) put a draft on the thread for a user to review, edit and send, and the API key can be a machine user scoped to that permission plus thread:read. source
Pylon API + MCP C
Pylon Labs, Inc.
POST /issues/{id}/draft-reply creates or updates a draft reply that a person sends from Pylon, separate from /reply (sends, can't be unsent) and /note (internal). A token can have its own identity. source
Zammad E
Zammad GmbH
PUT /api/v1/tickets/{id}/shared_draft stores an unsent article (body, type, internal, to) that agents see and send from the ticket. Note that internal true on an email article still sends. source
Zoho Desk B
Zoho Corporation Private Limited
POST /tickets/{id}/draftReply stores an email reply without sending, with update, delete, sendDraft and sendForReview operations; sendReply is the separate sending call. acc-41 shows workflow rules can't do this, but the API can. source

Does the job, with a limit 12

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.

ListingWhy
Chatway MCP C
Poptin Ltd
No draft object. The repository's skills draft in the chat and use add-note for a private note; send-message runs on the first call, so the person copies the note or approves a send. source
Chatwoot API D
Chatwoot Inc.
No draft object; the only non-sending route is a message with private=true, which the person must copy into a reply. private has no documented default and the examples send private=false, so a missing flag goes to the customer. source
Crisp API + MCP D
Crisp IM SAS
No draft object; the non-sending route is a message of type note (or send_conversation_message_note on MCP), which the person must copy. type is required, so nothing defaults to public, but text sends at once. source
Dixa D
Dixa ApS
No draft object in the v1 OpenAPI file. Internal notes (POST /conversations/{id}/notes) hold the reply for the person to copy; an outbound message is sent at once. source
Drag E
DragApp.com Ltd
Shared drafts exist in the product, but neither the 47 MCP tools nor REST v2 create one; reply_to_thread sends. The non-sending route is add_comment, an internal comment the person copies. toggle_ai_drafts only switches Drag's own AI drafts on a board. source
Freshdesk API + MCP D
Freshworks Inc.
No draft endpoint in the reference. Create a Note defaults to private true, so a note holds the reply, but the person must copy it into Create a Reply to send. source
Gladly C
Gladly Software, Inc.
No draft object. POST /conversations/{id}/notes adds an internal note the person must copy; POST /conversation-items/{id}/reply sends to the customer. source
Gorgias API + MCP C
Gorgias Inc.
No draft object in the REST or MCP docs. add_internal_note posts a private note the person copies; a REST message defaults to public true and is sent by Gorgias unless sent_datetime is set. source
HelpDesk D
Text, Inc.
No draft object in the Ticketing OpenAPI. PATCH /v1/tickets/{id} with a message and isPrivate true adds a private note the person copies; without isPrivate the message goes to the requester. source
Intercom API + MCP BB
Intercom, Inc. (with Intercom R&D Unlimited Company in Ireland)
No draft object. The non-sending route is add_internal_note on MCP or a REST reply with message_type note, which the person must copy into a reply; message_type comment sends to the customer. source
LiveAgent D
Quality Unit, s. r. o.
No draft tool or endpoint was found. MCP add_note stores an agents-only note the person copies; reply_via_email sends at once. MCP needs Business or Enterprise. source
Zendesk Support API B
Zendesk, Inc.
No draft object; the route is a comment with public false (an internal note) the person copies, as acc-40 and Zendesk's own AI workflow page describe. A comment's default follows the ticket's first comment, so a missing flag can go public. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
Landbot MCP server E
Landbot
The MCP tools build and publish bots and AI agents (create_bot, add_draft_blocks, publish_bot); none reads a conversation or leaves a reply on one. 'Draft' here means an unpublished bot flow. source

What stops agents finishing

  • no draft object, so the only non-sending route is an internal note the person must copy
  • reply endpoint defaults to public and emails the customer
  • token is personal with full access, so the draft appears as the person

Around it

Before: support.research-context, knowledge.search, crm.lookup. After: support.handoff-to-person, email.send.

Where this comes from

Weight 20 of 100 in Customer support & helpdesk: 12 of 42 accounts (acc-14, 15, 19, 27, 35, 37, 38, 39, 40, 41 plus the r/Zendesk snippet and Zoho forum); the single most described job, and the pattern every vendor page recommends

The same as data: /api/v1/use-cases/support.draft-reply-for-review.json, or the MCP tool get_use_case with id support.draft-reply-for-review. Other jobs in this category: /api/v1/niches?category=support.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.