Skip to content

Reviewing drafts ​

Most reviewing happens where your team already works: an agent opens the conversation in the help desk, reads the draft, fixes what needs fixing and sends the reply from there. The Agent drafts page in Overdesk adds what the help desk cannot show, such as the sources behind each answer and what your guardrail rules made of it.

The drafts list ​

Agent drafts lists every draft Overdesk has written for your workspace, newest first, 50 to a page. Each row shows:

ColumnWhat it tells you
ConversationThe conversation number, linked to the conversation in your help desk
ModeBatch for a draft from the scheduled run, Real time for one written the moment a message arrived, On demand for a re-draft made on this page
ConfidenceA score for how well the sources Overdesk found match the question, shaded green, amber or red
GuardrailHeld when a topic rule such as Billing matched, Escalated when an escalation rule matched, blank otherwise
ModelThe model that wrote the draft
CostWhat the draft cost on your Anthropic key

Press View on a row to open the draft.

Below the table, Prev and Next move through the pages and the count between them says which page you are on, beside the total number of drafts. The whole history is reachable this way, however far back it goes.

Screened conversations ​

Press Screened above the list to see the conversations Overdesk left a note on instead of drafting, because the customer's latest message looked like mail nobody needs to answer. Each row shows the conversation, linked to your help desk, what the message looked like, the check's confidence score out of 100, and when. If a person wrote one of them, reply from your help desk; their next message is drafted as usual. See Mail that is not support.

A single draft ​

The draft page puts the question above the answer.

  • The conversation is read live from your help desk each time you open the page. A message that arrived after the draft was written is highlighted and marked Arrived after this draft. Check those first: the customer may have solved the problem or changed the question.
  • Draft reply shows the answer as it will look in your help desk. Copy puts it on your clipboard with its formatting, ready to paste into a reply.
  • What this answer is based on lists the help articles, past conversations and saved replies the draft drew on. Help articles link to the page itself.
  • Open ticket takes you to the conversation in your help desk.

With Jira, GitHub or Linear connected, an Engineering card on the same page lets you open an issue from the conversation. See Creating issues from a conversation.

Edit, re-draft or discard ​

Anyone with the agent role or above sees three controls under the draft. Viewers see the draft without them. See Roles and permissions.

  • Edit opens the text for changes. Press Save changes to keep them. Overdesk stores the original beside your version, so grading still compares the reply your team sent with what the AI first wrote.
  • Re-draft writes a fresh draft for the same conversation and opens it. The old draft stays as it was, so you can compare the two, and the copy in your help desk is left alone.
  • Discard marks the draft as discarded. It stays on record, and the change cannot be undone from the page.

What an edit or a discard does in your help desk ​

Overdesk updates the help desk before it saves anything. If the help desk cannot be reached, you see an error and nothing changes in either place.

  • On Help Scout, with drafts arriving as draft replies, when the draft in the composer is still exactly what Overdesk wrote: an edit rewrites it there. A discard replaces its text with "This AI draft was discarded in Overdesk and is not a reply. Please do not send it." Help Scout has no way to delete a draft, so the replacement text is how it is withdrawn.
  • In every other case (notes on any help desk, Zendesk, Intercom and FreeScout, or a composer draft someone has already changed), Overdesk adds a new internal note headed "Overdesk draft update". It carries your edited version, or says the draft was discarded and should not be sent. The original stays where it is.

There is no send button in Overdesk. You edit and reply from your help desk.

Ask Overdesk in a note ​

On Help Scout, Zendesk, Intercom and FreeScout you can ask Overdesk about a conversation without leaving it. Write @Overdesk in an internal note with your question or what to change, for example:

  • "@Overdesk is there a known issue about this?"
  • "@Overdesk what plan is this customer on?"
  • "@Overdesk have we answered this before?"
  • "@Overdesk shorter please"

It works on any conversation in your Allowed inboxes, whether or not Overdesk drafted it. In an inbox outside them it doesn't answer, and posts nothing. On Zendesk a ticket's inbox is its group, and on Intercom only all lets it answer.

Overdesk looks the answer up the way a teammate would. It searches with your words as well as the customer's, and can search again in its own words: your knowledge base (your documentation and the GitHub, Linear and Jira issues you synced), past resolved tickets, saved replies, the customer's past conversations and their account in a connected store, other conversations in your Allowed inboxes, closed ones included (on Help Scout and FreeScout, whose search takes keywords), your connected code, the issues filed from this conversation, and the five most severe issues Overdesk's analyses found in it, resolved and dismissed ones included, each once however many analyses reported it.

It answers in a new internal note headed "Overdesk answer":

  • The answer cites what it relied on as [S1], [S2] and so on, and a list headed "Sources:" links each one that has a page (an article, an issue, a ticket) to the page Overdesk read, and each issue its analyses found to that issue's entry on the Intelligence page. That list links only pages Overdesk read itself, and the answer shows any link it writes as plain text. A file from your code is listed with the release it was read at, when there was one, and the lines the answer rests on.
  • A line headed "Checked:" says what it searched, so an answer that found nothing still tells you where it looked.
  • A question gets an answer and leaves the draft as it is. Ask it to write, change or redo the reply, and it rewrites the draft too.
  • When the answer looked at other customers' conversations, the rewritten draft stays in the note for you to read and copy, and the composer is left as it is. Every later answer on that conversation does the same, because it reads the earlier one.
  • When it read another customer's ticket, it masks that customer's name as the help desk records it, and the email addresses, phone numbers and keys it finds, so nothing read from that ticket can be restored into this reply. A detail nobody listed, such as a first name in a signature, an order number or a phone number written as plain digits, can still appear, so the note asks you to check the draft for another customer's details before you use it.
  • On Help Scout, with drafts arriving as draft replies, a rewritten draft also replaces the one in the composer, when that draft is still exactly what Overdesk wrote. If someone has changed it, or the answer can't be placed there safely, the composer is left as it is and the note says so. Help Scout marks the rewritten draft as edited, and "Show Original" still shows the earlier text.
  • On Zendesk, Intercom and FreeScout, Overdesk cannot edit a message, so the composer is never changed there and a rewritten draft always stays in the note.
  • Overdesk never replies to the customer from a note. The answer is always an internal note.
  • It answers the newest note your team wrote on the conversation, once, within an hour of it being written. Put your question in the latest note, and ask again if it wasn't answered, for example while drafting was paused.
  • Only a note a teammate types in the help desk asks. A note an app or an integration adds doesn't, Overdesk's own notes included, and neither do words you quote from someone else. On FreeScout, a note typed in the web app or sent by email asks, and a note another app adds through the API doesn't.
  • It answers up to 5 notes per conversation in 24 hours, the number set under Replies per conversation on Guardrails → Rules, counted separately from the replies Overdesk sends.
  • It answers even when your workspace only drafts where sources are found. The "Checked:" line shows what it searched, and if nothing was found, a rewritten draft stays in the note rather than the composer.

Asking in a note needs your help desk's webhook, with notes included. On Help Scout, turn on @Overdesk in notes on its page under Integrations and Overdesk adds that webhook for you. On FreeScout, the webhook Overdesk adds when you connect includes notes. On Zendesk, the webhook you set up for real-time updates already carries notes. On Intercom, subscribe that webhook to one more topic, conversation.admin.noted, or your notes are never seen. See Real-time updates with webhooks.

Name a ticket and Overdesk reads it ​

Write a ticket's number with its # (#4521) or paste its link in your note, and Overdesk opens that conversation and reads its latest messages:

  • "@Overdesk this looks like #4521, check how we answered there"

On Zendesk the number is the ticket's number, and the link is the ticket's address in Zendesk. On Intercom, write # and the conversation's id, the number at the end of the conversation's address in Intercom, such as #215467. A pasted Intercom link names a conversation only when it is the kind Overdesk's Open ticket button opens, the one that ends in /inbox/shared/all/conversation/ and the id; a link copied from another inbox view does not, so write the # form.

A number without its #, such as a year or a count, doesn't name a ticket, and neither does a number or link only in text you quoted. Overdesk can also open a conversation its own search found while answering. Either way it opens up to 3 tickets in one answer, and only a ticket that:

  • sits in the same inbox as the conversation you are on (on Zendesk that is the same group, and a ticket with no group never matches);
  • is not spam, a draft or deleted;
  • is not from an excluded sender.

On Intercom the inbox is the team that holds the conversation, so Overdesk opens a conversation held by the same team, and two conversations no team holds count as the same inbox. It does not apply a teammate's own permissions in Intercom beyond that.

When Overdesk looks up a ticket you named and can't read it, it gets the same short reply whatever the reason, so the answer never shows whether that ticket exists or where it is.

How Overdesk grades its drafts ​

The Score drafts against replies job runs each day at 06:30 by default. It looks at conversations closed in the last 14 days, compares the AI draft with the reply your agent actually sent, and tags the conversation in your help desk:

TagMeaning
ai-goodThe reply went out close to how the AI wrote it
ai-editedThe reply went out after real edits
ai-badThe reply that went out has little in common with the draft, or no reply followed it at all

A conversation carries one of these at a time, and a later grade replaces an earlier one. The job follows your Allowed inboxes setting. Pause or re-time it on Schedules.