Follow-ups
A follow-up is a scheduled nudge that brings a conversation back when a customer goes quiet or a promise needs chasing. It stops the most common support failure: a conversation that is technically open and practically forgotten.
Setting and cancelling
Set a follow-up from the conversation. Before you commit, a preview shows when the follow-up will fire, so you see the actual time rather than guessing what "in three days" means. While a follow-up is pending, the conversation shows a follow-up status badge.
If the customer replies first, or the issue resolves itself, cancel the pending follow-up from the same place. A stale follow-up produces a pointless notification that trains your team to ignore them.
What happens when it fires
The conversation comes back to the team's attention instead of sitting indefinitely in a waiting state. It is a reminder, not an automatic action — someone still decides what to do.
Patterns worth using
Chasing information — follow up two to three business days after asking a customer for details they have not supplied.
Confirming a fix — follow up after shipping a change to check it actually worked for the customer who reported it.
Low ratings — follow up on a poor CSAT rating while the context is fresh.
Renewal or deadline context — when the customer named a date, schedule the follow-up before it passes.
Combining follow-ups with other mechanics
Set status waiting when the ball is in the customer's court, and use the follow-up as the backstop that pulls it back.
If a follow-up fires and you still cannot progress, escalate with a macro or reassign rather than snoozing again.
If the cause is a bug, create a task from the conversation and let the follow-up remind you to check on the task.
Snoozing and follow-ups are not the same thing: snooze hides a conversation until a time, a follow-up resurfaces it for action.
Permissions
Setting and cancelling a follow-up requires support edit access.
Related pages
Was this article helpful?