Handling time affected by Snooze | Community
Skip to main content
Question

Handling time affected by Snooze

  • April 21, 2026
  • 1 reply
  • 39 views

I have a workflow set up as follows:
If the customer has been unresponsive for 30 seconds → Snooze (4 hours) → Closing message → CSAT → Close.

The issue I’m facing is that when the snooze timer ends, the conversation is assigned to another teammate (e.g. Bryan) before the closing message and subsequent actions are triggered.

For example, Anthony handles the conversation for 10 minutes and then snoozes it. When the snooze ends, it gets assigned to Bryan (because Anthony at assignment limit/ away status). The bot then sends the automated closing message and completes the closing actions. As a result, Bryan’s handling time shows as 0–10 seconds (depend how long it takes for the bot to take the subsequent actions), even though he did not actually handle the conversation. However, he is still included in the report because the conversation was assigned to him. This impacts his handling time metrics, as the average is calculated based on total conversations.

I have tried adding an “Assign to Catherine” action after the snooze ends (Snooze 4 hours → Assign Catherine → Closing message → CSAT → Close), but this does not override the assignment triggered when the snooze ends. In practice, the flow behaves as follows: Snooze 4 hours → Assign Bryan → Assign Catherine → Closing message → CSAT → Close.

Has anyone encountered this issue or found a solution for it?

1 reply

Forum|alt.badge.img+5
  • Intercom Team
  • April 23, 2026

Hey ​@Lawrence Toh 

What you’re seeing is expected behaviour, but I agree it’s not ideal for teammate-level handling time.

Here are some workarounds you could consider:

  1. Route auto-close flows away from human assignees
    Just before you snooze for auto-closure, reassign to a neutral team/teammate used only for automation, e.g.:

    Assign to team "Automation" → Snooze (4 hours) → Closing message → CSAT → Close

    That way, the final few seconds of “handling” live on a bot/automation owner, not on another human teammate.

  2. Avoid auto-reassignment on unsnooze where possible
    If the goal is for Anthony to “own” the conversation end-to-end, keep them in Away (not “Away & reassigning”) and/or adjust assignment limits so the conversation isn’t reassigned when the snooze ends.

  3. Use Adjusted handling time (if enabled)
    If your workspace has Adjusted teammate handling time turned on, you can base performance views on that metric. It excludes idle time between “ready” events (assign/unsnooze/reopen) and when a teammate actually resumes work, so teammates who never open the conversation again will show ~0s adjusted handling time for that leg.