How-to · AI-to-human handoff

How to hand off Shopify chat from AI to human — 10-step playbook.

The AI handles 70-85% of conversations autonomously. For the remaining 15-30% — high-value carts, complaints, custom orders, B2B inquiries — you want to step in live. Below: how to configure triggers, set up push notifications, practice takeover etiquette, and review the escalation queue.

Free tier includes live takeover. ~30 minutes to configure properly the first time.

The 10-step setup

  1. 01

    Decide what should trigger handoff

    Don't escalate everything — the agent should handle 70-85% of conversations autonomously. Good triggers: customer types "human/manager/agent/real person", refund/cancel/complaint keywords, high cart value + hesitation pattern, wholesale/B2B signals, your specific high-priority keywords. Bad triggers: any product question, any FAQ-able query.

  2. 02

    Configure trigger rules in Settings → Handoff

    Pre-built rule templates: (1) "talk to human" keyword (default ON), (2) refund/cancel keywords (default ON), (3) after 3 unsuccessful turns (default ON), (4) cart over $X + 2+ minutes idle (configure $X). Custom rules: add your own keywords or patterns. Each rule fires independently.

  3. 03

    Set push notification destinations

    Choose where escalations notify you: (1) browser push (works on desktop + mobile), (2) Shopify Admin notification badge, (3) email (immediate), (4) Slack webhook (if configured). Multiple destinations are fine — first responder wins. Critical: enable mobile push so you can join from anywhere.

  4. 04

    Configure response-time expectations

    In business hours: aim for <60-second response (typically 5-15 seconds is achievable with mobile push). Out of hours: configure the agent to say "we'll join in the morning" rather than appearing slow. Customers respect honesty about availability more than fake instant claims.

  5. 05

    Tag team members who can take over

    Add team members in Shopify Admin → Settings → Users; each gets handoff permission. Multi-person teams: first to claim a handoff owns it; others see "claimed by [name]" in the dashboard. Round-robin assignment optional.

  6. 06

    Practice the takeover flow

    Open Clearly merchant inbox → click a conversation in "needs attention" status → type your reply. Customer sees: "[Your Name] has joined the conversation" + typing indicator + your reply. Same widget, no friction. Practice in a test conversation first.

  7. 07

    Learn handoff etiquette

    Best practices: (1) acknowledge what the AI said before correcting/continuing — don't re-ask the same questions; (2) introduce yourself by name + role; (3) be concise — customers in chat expect short replies; (4) when conversation winds down, hand back to AI for follow-up questions; (5) summarize action items if any (refund issued, replacement shipped, etc.).

  8. 08

    Hand back to AI when done

    Two ways: (a) explicit "Hand back to agent" button — agent resumes, customer's next message gets AI reply with full context; (b) let the conversation naturally close — agent picks up the next message. Customer sees a smooth transition either way.

  9. 09

    Review escalations weekly

    Settings → Handoff → Analytics shows: which triggers fire most, average time to claim, % of escalations that converted to sale. Adjust trigger rules quarterly — kill false-positives (escalations that didn't need you) and tighten high-value triggers.

  10. 10

    Tune for your team size

    Solo founder: aggressive escalation (you want to join high-value conversations). 2-3 person team: medium escalation. 5+ person team: tight escalation (don't flood the inbox with low-value handoffs). Adjust as you grow.

FAQ

How fast should I respond to an escalation?
Industry benchmark: under 60 seconds for in-session escalations. Above that, customers leave. With mobile push notifications, 5-15 seconds is achievable — your phone vibrates, you tap, you're in. Out of business hours: be honest about timing rather than fake responsive.
What if I miss an escalation?
Agent posts an apology + sets expectations ("our team is offline; we'll reply when they're back"). Customer's message stays in the inbox for you to respond when available. Configure auto-reply templates for after-hours so the customer isn't left hanging.
Can the AI keep responding while a human is also active in the chat?
No — the moment a human joins, the AI yields. Prevents conflicting responses. When the human hands back (explicit button or after a quiet period), the AI resumes.
What if my team is overwhelmed by escalations?
Two problems to diagnose: (1) trigger rules too aggressive — tighten them, especially custom keywords; (2) knowledge base too sparse — agent escalates when it should know the answer. Audit which queries are escalating and add them to the knowledge base.
How do I see who took over which conversation?
Merchant inbox shows the operator name + timestamp for every takeover event. Filter by "claimed by [me]" to see your own handoffs. Useful for team-performance review.
Can I limit escalations to certain hours?
Yes — escalations only fire during business hours by default; outside hours, agent gracefully postpones. Configure "always escalate" rules for true emergencies (refund disputes, complaints) if you want 24/7 alerting on those.
Will customers know they're talking to AI before handoff?
Most customers don't need to be told — they get good answers either way. If they ask ("am I talking to a bot?"), agent answers honestly: "I'm an AI assistant for [Brand]; if you'd like a human, I can connect you." Customer-friendly disclosure rather than deceptive bot pretending to be human.