ada chatbot handoff failed: no agent available

TL;DR

'No agent available' means the handoff fired correctly but the other end was empty: no agents online, no queue with capacity, or the routing sent the chat somewhere nobody staffs. The bot did its job; the staffing or routing didn't. Fix it by defining what happens when nobody's there: a queue with a wait message, an offline form, or a callback offer. Never leave the customer at a dead end.

The query

ada chatbot handoff failed: no agent available

Use this when

• Ada handoffs fail with 'no agent available'
• Customers get stuck at the handoff step
• Handoffs fail only outside business hours

Not for

• Handoff routing sending to the wrong team
• Chat widget not loading on the page
• Agent platform API errors

Steps

1. Check agent schedules and queue capacity

Look at the target queue during the failure window: were any agents logged in and available? Most 'no agent available' clusters map to shift gaps, lunch hours, or a queue nobody was assigned to. The data is in your agent platform's availability reports.

Expected output: the failure timestamps mapped against agent availability.

2. Build the nobody-available path

In Ada, add a fallback for the failed handoff: offer a callback, open an email ticket with the transcript attached, or give a wait-time estimate. Test it by handoff with zero agents online. This path is the actual fix.

Expected output: a tested fallback that captures the customer when no agent is online.

3. Set handoff hours honestly

If agents only cover 9 to 5, the bot should say so before offering a handoff, not after it fails. Gate the handoff offer on business hours and route to the fallback outside them.

Expected output: the bot offering handoff only when agents are actually staffed.

4. Alert on handoff failure rate

A trickle of failures is normal; a spike means a shift didn't start or a routing change broke. Alert when the failure rate crosses your baseline so ops notices before customers complain.

Expected output: an alert on handoff failure rate with a sane threshold.

Variant phrasings

ada handoff to agent not working

Step 2 is the fix; steps 1 and 3 prevent recurrence.

ada chatbot escalation no agents online

Step 3 covers the hours gating; step 2 covers the fallback.

Why it happens

Handoffs are designed for the happy path: bot gives up, agent picks up. But agent availability is the least reliable part of the chain, and bot builders test handoffs during business hours when agents are obviously online. The failure mode only appears at night, on weekends, and during the shift nobody wanted.

Edge cases

• Holiday schedules need their own config. The bot doesn't know it's Thanksgiving.
• Multi-queue setups fail when the handoff targets a queue id that was renamed. Audit routing quarterly.
• Transcripts must follow the handoff. A successful handoff that loses context is barely better than a failed one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_W-wSNGUvbx6jdXMShDjV-g