Skip to content

Follow-up nudges ​

Some customers go quiet after your team replies. Follow-up nudges spot those conversations and draft a short, friendly check-in asking whether the customer still needs help, so nobody has to remember to chase. Like every draft, the nudge waits unsent for someone on your team to send, unless your workspace has chosen to have Overdesk send nudges. See Sending nudges.

What a nudge needs ​

Nudges need a connected help desk and your Anthropic API key. They do not need a documentation source: a nudge is written from the conversation itself, not from your knowledge base, so nudges start as soon as your key is saved, before you have pointed Overdesk at your docs.

The Follow-up nudges job runs daily at 09:00 in your workspace's timezone. You can change the time or pause it on Schedules. See Schedules.

Which conversations get a nudge ​

A conversation gets a nudge when all of this is true:

  • It is pending in your help desk, waiting on the customer.
  • It is in an inbox the job may work in. With Allowed inboxes empty, that is every inbox. See Allowed inboxes.
  • It was updated in the last 30 days.
  • A reply reached the customer, from your team or from Overdesk, at least 3 days ago. A reply that bounced, or that is still an unsent draft, does not count.
  • The customer has not written since that reply.
  • It is not tagged waiting-for-release. Add that tag to any conversation you are holding until a fix ships.
  • It has not been nudged before. If your drafts arrive as draft replies, no unsent reply is already waiting in the composer either.
  • The customer is not under Excluded senders, and has not been erased. See Privacy and data and Erasure and deletion requests.
  • A quick check by the model does not find the conversation already resolved.

Each run works through up to 50 conversations across your help desks.

What arrives ​

The nudge arrives the same way your reply drafts do: as an internal note headed "AI Follow-Up" by default, or, on Help Scout, as an unsent draft reply if you have chosen that. On FreeScout every nudge Overdesk does not send is an internal note. See Where drafts go. Overdesk also tags the conversation ai-followup.

Nudges are written with your drafting model and follow your settings on Customize AI, so the tone and rules you set for replies apply to them too. See Customize AI.

One nudge per conversation ​

Overdesk nudges a conversation once. It keeps its own record, so deleting the note or sending the nudge does not bring the conversation back for a second one.

Sending nudges ​

By default a nudge never goes to the customer on its own: a person reads each one and decides whether to send it. A workspace that has turned on sending can also have Overdesk send them, which takes two things: sending is on, and the rule Also send follow-ups is on. It is a rule under Answer automatically when on Guardrails → Rules, and it starts off for every workspace. A workspace on Draft assist keeps every nudge unsent whatever the rule says. The dashboard describes that group as "Replies the reviewer approves, and follow-ups if you switch them on. They are sent only when automatic sending is on for your workspace." The rule's own line reads "Matches when the message is a follow-up Overdesk wrote on its own."

With sending on and the rule on, the daily run sends a nudge only where Overdesk itself answered the customer's last message. Everywhere else, for example where your team answered it by hand, the nudge is placed unsent, as it is with the rule off. On Decisions that hold reads The customer's last message was not one Overdesk answers on its own.

Two more things hold a nudge, and nothing in your workspace switches them off:

  • A teammate wrote in the conversation (a note or a reply) after Overdesk's reply. Someone is working it, so the nudge waits, and a nudge is only ever a follow-up to Overdesk's own reply. If Overdesk cannot read which replies it sent itself, the nudge waits too. On Decisions: A teammate wrote in the conversation after Overdesk's reply.
  • The last reply told the customer, in wording Overdesk recognises in English, that your team would get back to them. A nudge on top of that nags someone who was asked to wait. On Decisions: The last reply told the customer your team would get back to them.

Sending a nudge also needs the screen to have read the customer's last message as a request for support. With Screen out non-support mail off, no new message is screened, so a nudge on a message that arrived while it was off has no screen to read, is held as Not a request for support and is placed unsent.

Your gates and the rules that read tags, keywords or the customer, the holds that read a nudge's own words and the send-time holds all apply to a nudge, and the rules that allow a reply never allow a nudge. A nudge also follows only a message those rules already cleared. A rule that matches on tags, keywords or the customer holds a nudge in the same way, so with the starter rules Urgency unknown holds a nudge on a conversation with no urgency tag, and High urgency holds an urgent one. A rule that reads the reviewer's answer about a draft, such as a topic, a request for a person or how the customer sounds, cannot match a nudge, because a nudge has no such review.

A nudge gets the check a reply gets for talking about its own sources or caution, and Overdesk's own checks on the words: it may not claim to be a person, promise anything your team has to do, repeat what only your internal notes say, or go against what your team told the customer. A nudge whose check could not be answered is not sent. See Holds on what a reply says.

The checks on Sending apply as well, including the channel the conversation is on, your hourly limit and the limit per conversation. A nudge counts toward both. A workspace sends at most 5 nudges a day, in your workspace's time zone, and never more than half your hourly limit, rounded down, so an hourly limit below 2 sends no nudges. Once the day's share is spent, the conversations still waiting, other than a forwarded one, are left for the next run: nothing is written for them and nothing is decided.

  • Allowed inboxes. With the field empty, nudges are written in every inbox, and a nudge that would otherwise be sent is placed unsent, and that hold reads The conversation changed while we were deciding on Decisions. With inboxes named, they are written, and can be sent, only there, as a reply is. See Allowed inboxes.
  • Weekends. A workspace that sends nudges sends none on a Saturday or Sunday in its time zone, which is UTC until you set Timezone in Settings → General. For such a workspace the run that day does nothing at all, and the next weekday's run picks the conversations up. A workspace that does not send nudges is nudged on any day.
  • Unsent drafts. A conversation with an unsent draft reply in the composer gets no nudge, because a second message beside it would be a second voice in the customer's inbox.
  • Forwards. A conversation a teammate forwarded still gets its nudge, and the nudge is placed unsent, never sent.
  • After the send. The status you chose under After Overdesk sends a reply applies to a sent nudge as it does to any reply. Overdesk tags the conversation ai-followup and ai-sent, as it does a reply it sends, and the conversation is not nudged again. A nudge placed unsent gets ai-followup only.
  • Escalate rules. A rule under Escalate when applies to a nudge as it does to a reply: when one matches a nudge Overdesk would have sent, nothing is sent, the nudge is placed unsent with a note naming the target, and an alert is raised. See Escalation.
  • Held nudges. A nudge Overdesk would have sent but held is placed unsent, as a note or a draft reply, with a short internal note headed "Overdesk held this reply" that says why. See Where drafts go.

What stops nudges ​

  • Pausing the workspace in Guardrails → Send mode stops nudges along with reply drafts.
  • Pausing the Follow-up nudges row on Schedules stops nudges and leaves drafting running.
  • Turning Also send follow-ups off, or sending off, goes back to nudges placed unsent for a person.

With the rule off, which is how every workspace starts, nudges never go to the customer on their own. A person reads each one and decides whether to send it.