What actually happens
When the AI agent cannot finish, it hands the conversation to a human rather than guessing or stalling. Two things happen at once:1
The conversation reopens and gets routed normally
It does not sit in an unassigned pile waiting to be noticed. It goes through the same
assignment path as any other open conversation — see Assignment policies
— so it lands with whoever is actually next in line.
2
The human inherits the whole thread, not a blank one
Because Tied threads by person rather than by ticket, the agent picking this up sees everything
the AI agent already tried, on any channel, in order — not a summary standing in for the
original. See Inbox for why that is the default rather than a feature.
Once a person is in the thread, the AI agent steps back
While a human owns the conversation and is actually on shift, the AI agent stops replying to the customer. It already said someone was coming; continuing to answer over that person’s head would make that untrue, and would hand the human a conversation that kept moving without them. Outside those hours, there is nobody yet to hand off to — so rather than leaving the customer stuck until morning, the AI agent keeps answering. The hours it checks are the same ones configured in Teams and business hours.The billing consequence
Handoff is free. Not a reduced charge, not a routing fee, not a partial-credit charge. Zero.
And if a human sends a message into that conversation before the resolution is confirmed, the resolution
is not billable at all (once confirmed, the fee is locked, though a reopen or a negative survey can still cancel it) — see What counts as a resolution.
Next
What counts as a resolution
The four signal tiers, and why a human message is always Tier 0.
AI agents
What the agent can do before it ever reaches this point.