A customer spends ten minutes explaining a problem with their integration to your website chat. The assistant cannot solve it and offers to connect them with support. The support agent's first message: "Hi, could you describe the issue you're having?" The customer sighs and starts again.
Escalation with context is the difference between a support experience customers tolerate and one they appreciate. The handover itself is where most teams lose goodwill.
Step 1: decide when to escalate
Clear rules prevent two failures: escalating too much, which defeats the purpose of self-service, and too little, which traps customers. Common triggers:
- The assistant cannot find an answer in your docs.
- The customer asks for a person.
- The topic is sensitive: billing disputes, data loss, security, cancellations.
- The customer seems frustrated.
Step 2: pass everything
A good handover includes:
- The full conversation.
- The customer's name, email and account.
- A one-line summary of the problem.
- What was already suggested and whether it helped.
- Urgency.
SpideyChat for SaaS companies opens a ticket or hands the conversation to a person with the exchange attached, so the agent starts with the full picture.
Step 3: tell the customer what happens next
Assistant: I can't solve this one from the docs, so I've passed it to the support team with our conversation. Someone will reply by email within two hours during business hours. You won't need to explain it again.
Setting expectations reduces follow-up messages and anxiety.
Want a 24/7 AI Employee for Your Website?
See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.
Step 4: prioritise escalated tickets
A customer who has already tried self-service has been waiting longer than one who opened a ticket directly. Put escalated tickets near the front of the queue.
Step 5: route to the right person
Some escalations are support problems, others are sales questions or account management. Routing them correctly, as covered in how SaaS teams route chat to sales or support, stops a second handoff.
Step 6: learn from escalations
Each escalation is a question your docs could not answer. Review them weekly. Some reveal documentation gaps, others bugs, others product confusion. Reducing avoidable escalations is part of cutting the cost described in the cost of answering the same how-to question daily.
Handovers outside working hours
Many escalations happen when your team is offline. The handover should still work: the ticket is created with the conversation attached, and the customer is told honestly when to expect a reply. Avoid promising a person "shortly" at 2am. A clear "the team is online from 9am and will reply first thing" sets the right expectation, and customers are generally fine with that if their problem is not urgent.
For urgent problems out of hours, such as an outage or data loss, decide in advance whether someone is on call and how they are alerted. Writing that rule down turns a stressful moment into a routine.
Handovers in smaller businesses
Handover matters just as much when the "team" is one person. A solo store owner who receives a question with the full conversation attached can reply in one message, as shown in running a one-person store without living in your inbox. For more on how chats become tickets, see support tickets from chat.
What customers notice
Customers rarely remember that they talked to an assistant first. They remember whether they had to repeat themselves, and how long they waited for a person. Get those two things right and escalation becomes a strength. To see how the handover works, try an assistant on your site, or read about tickets and handoff.