Skip to content

Overview ​

Overdesk writes a reply to each new customer message and leaves it unsent in your help desk. Someone on your team reads it, edits it if it needs editing, and sends it. The drafting happens in the background, so on most conversations the answer is already waiting when an agent opens it.

Until your workspace turns sending on, every draft waits for a person. Once it is on, Overdesk sends the replies your guardrails approve and every other draft still waits; see Sending. See Where drafts go for where a draft lands on each help desk.

What drafting needs ​

Drafting starts once these are in place:

  • A connected help desk. See Connect your help desk.
  • Your Anthropic API key, saved in Settings → AI. Drafting runs on your own key. See Add your Anthropic API key.
  • A documentation source, set in Settings → Knowledge base. Drafts are grounded in your docs, so drafting waits until a docs address is set; see Point Overdesk at your docs. It does not wait for the first crawl, and by default a conversation your knowledge base has nothing on is still drafted: see Only draft when sources are found.
  • At least one inbox named in Allowed inboxes, under Settings → General. While that field is empty, no reply is drafted automatically, in any inbox. Follow-up nudges are still written in every inbox, but Overdesk sends one only in an inbox named there. See Allowed inboxes.

When drafts are written ​

Overdesk checks your queue every 15 minutes. Each run looks at the open conversations in your allowed inboxes that were updated in the last 14 days, and drafts up to 25 of them, most pressing first. Conversations tagged as urgent, as bug reports or as billing questions move up the list, and a customer who has waited a long time or written in more than once moves up too. The tags come from Triage.

Assigned conversations get drafts as well. A conversation someone has picked up is usually the one they are about to answer.

With webhooks set up, Overdesk also drafts the moment a new conversation or a customer reply arrives, instead of waiting for the next run. See Real-time updates with webhooks.

How often a conversation is drafted depends on where drafts go. Each new customer message gets a new draft. With internal notes, a new note is drafted when a customer message arrives after Overdesk's last draft note on the conversation. With draft replies, each new customer message gets a fresh draft, unless an unsent reply is already waiting in the composer. A Help Scout live chat is drafted once, the first time Overdesk reads it. For a fresh answer on any conversation, use Re-draft on the draft page in Overdesk.

To start a run straight away, press Run auto-draft on the Agent drafts page.

What arrives in your help desk ​

By default each draft arrives as an internal note. It opens with an "AI Draft Response" heading, the model and the date, then gives the answer, then a line counting what it drew on: docs, history, threads, past resolutions and saved replies. On Help Scout and FreeScout you can have drafts arrive as an unsent reply in the composer instead. See Where drafts go.

Overdesk adds the ai-reply tag to each conversation it drafts, and lists the draft on the Agent drafts page, where you can check its sources, edit it or discard it. See Reviewing drafts.

When a conversation gets no draft ​

  • The workspace is paused. Choosing Paused under Guardrails → Send mode stops all drafting until you switch back to Draft assist. See Guardrails.
  • Its inbox is not named in Allowed inboxes.
  • The newest message in the conversation is a reply Overdesk already sent, so there is nothing new to answer. A real-time run says so under Details on the Runs page. A draft you ask for yourself, from Slack or with Re-draft, is still written.
  • The newest message is a reply a teammate wrote to the customer, in the help desk or by email, and the customer received it. The teammate has answered, so the conversation waits for the customer. The same goes for a conversation a teammate started with the customer, until the customer writes. A real-time run says so under Details on the Runs page, and a draft you ask for yourself is still written. A message from your help desk's workflows, triggers or automations, or one posted through the API, is not a teammate's reply and still gets a draft.
  • It was last updated more than 14 days ago.
  • It already has a draft. With internal notes, that means an Overdesk draft note anywhere on the conversation. With draft replies, it means a draft since the customer last wrote, and any unsent reply in the composer counts, including one a teammate has started.
  • It comes from a sender on Excluded senders. See Excluded senders.
  • It looks like mail nobody needs to answer. It gets a note instead; see Mail that is not support.
  • Nothing relevant turned up and you have asked Overdesk to draft only when it finds relevant sources. The run says how many conversations it skipped on the Runs page. See Only draft when sources are found.

Mail that is not support ​

Before it drafts a conversation on its own, Overdesk checks the customer's latest message. Marketing and sales mail, spam and scams, automatic notices from a website or service, bounces, out-of-office replies and other help desks' receipts get no draft. The conversation gets an internal note instead, headed "Overdesk skipped drafting", saying what the message looks like and that nothing was sent, and the ai-not-support tag. Every one is listed under Screened on the Agent drafts page.

Claude Sonnet 5.5 reads the message on your key, with its subject when the customer opened the conversation with it, and screens it only when it is confident; otherwise the conversation is drafted as usual. A message in any language is read the same way. Each message is checked once, and again only when a check could not be made.

A new message from the customer is checked on its own, so a person who writes after an automatic reply gets a draft. A draft you ask for yourself, from Slack or with Re-draft, is always written. To turn the check off, clear Screen out non-support mail in the Draft replies card on the Customize AI page.

If a drafting run fails, Overdesk raises a "Drafting failed" alert and records what went wrong on the Runs page, such as which help desk connection it could not reach, or that a help desk's subscription is inactive and needs renewing with the help desk.