Appearance
Where drafts go
Every draft lands in your help desk unsent, on the conversation it answers. You choose its shape: an internal note beside the conversation, or a draft reply sitting in the composer ready to edit and send. Either way the customer sees nothing until someone on your team sends a reply. A reply Overdesk sends itself, once your workspace turns sending on, never becomes a draft at all; this setting decides where every other reply goes.
The two choices
Internal note is the default and works on every help desk. Your team sees the answer along with the model that wrote it and a count of what it drew on. Nothing can reach the customer from a note, so an agent copies what they want into their reply.
Draft reply, ready to edit and send puts the answer in the reply box, so your team edits and sends with no copying and no note to delete. It is not sent until a person sends it. This choice works on Help Scout only. Every other help desk gets a note, whichever you choose.
Either way, each new message from the customer gets a new draft. With notes, a new note is drafted when a customer message arrives after Overdesk's last draft note on the conversation, and the earlier notes stay where they are. With draft replies, each new customer message gets a fresh draft, unless an unsent reply is already waiting in the composer. See Drafts.
What each help desk supports
| Help desk | Internal note | Draft reply in the composer | Editing or discarding in Overdesk updates the help desk copy |
|---|---|---|---|
| Help Scout | Yes | Yes | Yes for a draft reply nobody has changed in the composer, otherwise Overdesk adds a note |
| FreeScout | Yes | No, drafts always arrive as a note | No, Overdesk adds a note recording the change |
| Zendesk | Yes | No, drafts always arrive as a note | No, Overdesk adds a note recording the change |
| Intercom | Yes | No, drafts always arrive as a note | No, Overdesk adds a note recording the change |
Zendesk and Intercom give Overdesk no way to place an unsent reply, and FreeScout gives it no way to place one that is safe, so on those help desks Overdesk posts a note whatever this setting says. See Reviewing drafts for what editing and discarding do.
Change where drafts go
- Open Guardrails. The Send mode tab opens first.
- Under Draft assist, find Where drafts go.
- Pick Internal note or Draft reply, ready to edit and send. The choice saves as soon as you click it.
Only an admin can change this setting. If the workspace is paused, the change takes effect when you resume drafting. The draft reply option stays greyed out until Help Scout is connected. If Zendesk, Intercom or FreeScout is connected as well, the option says that a draft reply there still arrives as a note. A workspace with only FreeScout, Zendesk or Intercom shows Internal note as chosen, even if draft replies were saved earlier, because that is what it gets.
When a draft reply arrives as a note instead
With Draft reply, ready to edit and send chosen, Overdesk still posts an internal note when:
- the conversation is on Zendesk, Intercom or FreeScout (see FreeScout below);
- the conversation has no customer email address to address the reply to;
- the answer still contains one of the placeholders Overdesk uses to mask personal details, which it could not swap back. In the composer that placeholder would be one click from a customer, so the answer goes to a note where it is harmless.
- the answer contains what looks like a licence key, an API key or a code written beside its label, such as a coupon code. In the composer it would be one click from a customer, and the key may have come from another customer's conversation, so the answer goes to a note for your team to check.
FreeScout always gets a note
On FreeScout, every draft and every follow-up nudge Overdesk does not send arrives as an internal note, with sending on or off, whichever choice you made above. Overdesk cannot read which version of FreeScout's API and Webhooks module you run, and a module older than 1.0.103 publishes a draft reply to the customer instead of holding it. A note never reaches your customer on any version. See FreeScout.
Escalations on draft replies
A draft reply holds only the answer, because anything else in the composer would go to the customer when an agent presses send. So when a rule hands a conversation to someone, Overdesk first posts a short internal note headed "Overdesk escalation" naming who should take it and why, then assigns the conversation. With note delivery, that line sits at the top of the draft note instead. See Escalation.
Replies Overdesk held back
With sending on, a reply Overdesk held back arrives as a note or a draft reply as usual, followed by a short internal note headed "Overdesk held this reply" that says why it was not sent. When the conversation is handed to someone for that same reason, the hand-over line says it instead. The held note is separate, so the reason never sits in the composer, and when the conversation is handed to someone, it is there before they are. Overdesk does not count it as a note from your team, and the next draft on the conversation does not read it.
Follow-up nudges
Follow-up nudges arrive the same way as reply drafts: as a note, or as a draft reply where this setting and the help desk allow it, which is Help Scout alone. A nudge Overdesk sends because Also send follow-ups is on does not arrive that way, and a nudge it held arrives this way with the "Overdesk held this reply" note beside it.
What this setting never does
It never sends. Both choices leave the answer unsent, and no value of this setting can make Overdesk reply to a customer; it only decides where your team finds a draft. Sending is a separate choice, under Send mode; see Sending.