3
Triggers for handover
Asked, can't answer, or policy
10–25 min
Live request window
Then the agent takes a message
30 min
Silence before hand-back
A teammate who walks away
$0
For your team's replies
Only the agent's work is billed
When should the agent hand over?
Three triggers cover almost every case. The customer asks for a person, in any wording: a representative, a manager, 'a real human'. The agent can't answer from its knowledge, and stopping at 'I don't know' would leave the customer stuck. Or the conversation is one your team wants to own regardless: a complaint, an upset customer, an urgent problem, a contract question, anything touching security or legal.
The first two are behaviours to build in. The third is policy, and in Wiredesk it is written as plain-language instructions to the agent rather than configured in a rules engine: 'if the customer mentions a chargeback, offer to put them through'. Write those instructions the way you would brief a new starter, then test them with the phrasing your customers actually use.
Two failure modes sit either side. An agent that ignores a request for a person and keeps answering is why customers learn to hate bots. An agent that hands over everything the moment it is unsure has only moved your queue.
How a handover is decided
| Inside hours | Outside hours | |
|---|---|---|
| Chat | Flags the conversation, emails or texts the team a link, keeps answering while it waits. | Says nobody can join now and takes a message. |
| Flags the thread. A teammate replies in the same thread, from the agent's address. | Says nobody can be put through now and offers to take a message. | |
| Phone | Tells the caller, then transfers the live call to the agent's handover number. | Transfers anyway if call transfer is on. Switch it off to take a message instead. |
At a glance
One month of handovers: who asked, when, where, and how it ended
- 1Trigger415Asked for a person4.4% of 9,500 conversations: asked outright, couldn't be answered, or your policy said so.
- 2Hours68%Inside business hours284 inside, 131 outside. Outside, chat and email take a message.
- 3Channel
- Chat225
- Email100
- Phone90
- 4Outcome290Reached a person125 left a message instead, so nobody was left waiting on nothing.
- 5Back30 minOf teammate silenceThen the agent picks the chat or email back up. A transferred call stays with you.
How many conversations actually need a person? A worked month
Here is the month, split by channel:
| Channel | Conversations | Asked for a person | Rate | Inside hours | What happened |
|---|---|---|---|---|---|
| Chat | 3,750 | 225 | 6.0% | 153 | 130 joined live (85%); 23 timed out and became messages; 72 out-of-hours messages |
| 5,000 | 100 | 2.0% | 70 | 70 flagged and answered in the thread; 30 messages taken out of hours | |
| Phone | 750 | 90 | 12.0% | 61 | 61 transferred to the desk line; 29 out of hours transferred to the on-call phone |
| All | 9,500 | 415 | 4.4% | 284 | 290 reached a person live or in the thread; 125 left a message |
In this month, callers ask for a person at twice the rate of chat users: many of them called because they already wanted to talk. Email barely asks at all, because email is already asynchronous: the customer is waiting for a reply either way.
When chat customers ask for a person
- Inside 9:00–18:00: 153 requests (68%)
- Outside: 72 requests (32%)
The chart answers the staffing question. The busiest hour of the day collects 19 requests across a whole month, which is fewer than one a day. One person on a rota can take every live chat handover with time to spare, as long as the notification reaches them. The 23 that timed out were the ones nobody saw in time, and the fix for those is the notification route, not more people.
What context has to travel with the customer?
Enough that the person picking up can start at the customer's problem rather than their name. That means who they are and how to reach them, which channel they came in on, a two-line summary of what they want and what has already been tried, and the full transcript for anything the summary missed. Summary first, because that is what gets read. Transcript underneath, because that is where the detail lives.
When Wiredesk opens a ticket in a connected helpdesk (Zendesk, Freshdesk, HubSpot, Intercom, Help Scout, Gorgias or Odoo) the ticket carries exactly that: the agent's summary, the customer's name, email and phone where it has them, the channel, a link back to the conversation, and the whole transcript. In Zendesk the transcript goes in as a private note, so the customer's 'we got your request' email doesn't repeat the conversation back to them. The agent then gives the customer the ticket number, so they leave with a reference.
What the ticket carries
- Requester
- Dana Whitfield · dana@example.com · +1 555 0142
- Channel
- Website chat
- Summary
- Wants to swap a 2-person tent bought 12 days ago for the 3-person model, which is out of stock in green. Has read the returns page; asking whether the swap can be held until restock.
- Conversation
- Link back to the conversation in Wiredesk
- Private note
- The full transcript, 14 messages
Should handover be live or asynchronous?
Live when someone is there to take it and the customer needs it now. Asynchronous, meaning a message taken or a ticket opened, when nobody is, or when the answer needs research anyway. The mistake is promising live and delivering async. A customer told 'someone will be right with you' who then waits twenty minutes has been treated worse than one told 'I'll pass this to the team and they'll email you today'.
So give live handover a clock. In Wiredesk chat, a request for a person flags the conversation, notifies your team by email or SMS with a link straight to it, and shows the customer that someone is being asked to join. The agent keeps answering while it waits, because a request is not a pause, and asks for a name and a way to reach them so nothing is lost. If nobody joins in time, the request times out somewhere between ten and twenty-five minutes after it was made, and the agent says plainly that nobody is free and asks how to follow up.
A live chat handover, start to finish
- 0 minCustomer asks for a personThe conversation is flagged in the inbox.
- 0 minTeam notifiedBy email or SMS, with a link straight to the conversation.
- While waitingAgent keeps answeringAnd asks for a name and a way to reach them, so nothing is lost.
- When a teammate joinsAgent stopsTheir replies appear in the customer's widget. The conversation just carries on.
- 10–25 min, nobody joinedRequest times outThe agent says plainly that nobody is free and asks how to follow up.
- 30 min of teammate silenceHanded back to the agentSo a teammate pulled away never strands the customer.
The analytics page counts every request for a person and what share of them a person answered, with the typical wait. That figure tells you whether live handover is a promise your team can keep.
How is handover different on phone, chat and email?
On the phone, handover is a transfer. A caller can't be parked in a widget, and 'someone will call you back' is a step down from a person now. Wiredesk's phone agent tells the caller it is putting them through, then transfers the live call to the handover number set for that agent. It is a direct transfer: the person who answers gets the caller, not a spoken briefing, and the transcript and summary land on the conversation in the dashboard. If the transfer fails, the agent apologises and takes a message instead. The handover number must be a different line from the one forwarded to the agent, or the call would come straight back, and Wiredesk checks for that before it transfers.
There is one handover number per agent. If billing and technical support need different people, route that inside your own phone system, or run a separate agent for each line.
In chat, a teammate claims the flagged conversation or simply replies from the dashboard. The agent stops answering the moment they do, and their replies appear in the customer's widget, so from the customer's side the conversation just carries on.
Email is already asynchronous, so handover is quieter. The thread is flagged, a teammate replies from the dashboard, and the reply reaches the customer in the same thread, sent from the agent's address. Nobody needs to be told to hold.
| Chat | Phone | ||
|---|---|---|---|
| What handover means | A teammate joins the conversation | A teammate replies in the thread | The live call is transferred |
| Who is told | The team, by email or SMS | The thread is flagged in the inbox | The person on the handover number |
| If nobody is free | Times out after 10–25 minutes; the agent says nobody is free | Times out on the same clock; no email is sent | Transfer fails, message taken |
| Out of hours | Message taken | Message taken | Transfers if call transfer is on |
| How it comes back | Handed back, or after 30 minutes of silence | Handed back, or after 30 minutes of silence | It doesn't; the caller is on your line |
What should happen after hours?
Nobody is there, so don't offer anybody. In Wiredesk you set business hours per agent, in your own time zone. Outside them, chat and email stop offering a person at all; the agent says it can't put anyone through right now and offers to take a message. A taken message records the customer's name, a callback number or email (on a call, it can use the number they are calling from) and what they need, and your team is notified.
Phone is the exception to watch. Business hours govern chat and email handover, not call transfer: if a handover number is set and call transfer is on, the agent will transfer at three in the morning. Point that number at somebody on call, or switch call transfer off so the agent takes a message instead. Harbor & Pine chose the first: its 29 out-of-hours calls rang the on-call phone, which is why phone is the one channel where every request reached a person.
How does the conversation get back to the agent?
Deliberately, or by default. A teammate who has finished hands the conversation back from the dashboard and the agent resumes. One who simply gets pulled away doesn't strand the customer: after half an hour of silence from the person who took it, Wiredesk hands the chat or email back to the agent automatically. A transferred call doesn't come back, because the caller is on your line now, and it is filed as handed over.
Nothing is billed for the human part. Replies your team types aren't metered, and a transferred call stops counting minutes when the caller leaves the agent.
How do you set up handover in Wiredesk? Step by step
Step 1: Set the transfer number and business hours
Open the agent and go to Handoff. The page has one section per route to a person:
- On a call. Enter the number calls transfer to: a cell or a desk line, never the number customers dial, or the transfer loops back to the agent. Without a number, the agent takes a message instead.
- In chat, email and WhatsApp. Switch on A person in chat & email only if somebody watches the Inbox; the agent takes a message either way. Then set business hours per day, in your time zone. Phone transfers ignore them.
- In your helpdesk. Covered in step 3.

Step 2: Write your policy as instructions
In Instructions, write the conversations your team wants to own, in plain words, the way you would brief a new starter:
If the customer mentions a chargeback, a safety problem with a product, or a complaint about a member of staff, apologise, say you're putting them through to the team, and hand over.
Step 3: Connect your helpdesk
If your team works in a helpdesk, use Open tickets under In your helpdesk on the same page. It is an action: connect Zendesk, Freshdesk, HubSpot or another helpdesk, then say when to open a ticket. A handover then becomes a ticket with the agent's summary and the whole conversation on it, rather than a conversation in a second inbox.
Step 4: Test it with your customers' words
In Tests, write tests that ask for a person the way your customers do ('can I talk to someone', 'this is ridiculous', 'I want a refund now') and the policy topics from step 2. Check the agent hands over, and check it doesn't hand over the questions it should answer itself.
Step 5: Answer from the conversation, then watch the numbers
A request for a person marks the conversation Needs human in the list. Open it and the agent's So far card sits above the reply box: what the customer wants, what the agent already did, and the details it collected. Sending a reply pauses the agent, and the customer sees it in their widget. I'll take this one pauses the agent and tells the customer you've joined.


Then read Analytics. Handover rate is the share of conversations that went to a person. Median time to a person is how long those customers waited. Answered by a person is the share of requests a teammate answered, which is the number that says whether live handover is a promise your team can keep.
