How to Build bot-to-human handoff on WhatsApp in Wapilot

bot-to-human handoff is the canvas job shared support team should ship this week. Agent opening a chat and asking name again after the bot collected it? Wrong trigger or no Update Tag wastes spend and nights.

Written for people who will publish this shared support team journey this week—not for a strategy offsite.

You get a five-step build, the real nodes (Update Contact, Update Tag, Assign Agent, Simple Text), and why shared support team had to cut half the graph.

We would rather shared support team publish with Update Contact and an agent exit than collect features “for later.”

Write fields to CRM before assign. Tag intent. That is enough setup talk for shared support team before the first heading.

this node: Assign Agent after Update Contact/Tag so variables are on the card, plus one summary line. shared support team should treat that sentence as the job, not a slide title.

What is bot-to-human handoff?

Sources: WhatsApp messaging limits and Cloud API send-messages. That pairing explains why shared support team goes quiet after a day of silence on Update Contact.

this step: Assign Agent after Update Contact/Tag so variables are on the card, plus one summary line. On the canvas you place Update Contact, Update Tag, Assign Agent, Simple Text. shared support team teams finish one job, then use Update Tag when the customer sends a photo or a rant.

This is not a campaign. Canvas setup for shared support team: WhatsApp Flow Builder.

In this series — Part 1 of 5 (Handoff & Scale). Next: canned commands. This is the series start.

How do you go from blank to a live path?

If a template already includes Update Contact, start there and delete what shared support team does not need.

1. First. Write fields to CRM before assign.
2. Then. Tag intent.
3. Next. Text: “Passing you to a person.”
4. After that. Assign Agent.
5. Finally. Train agents to read the card first.

In a shared support team thread (2026), the failure was concrete: assign first, update later—race left cards empty. The rewrite that stuck was CRM nodes then Assign Agent, never reverse. Repeat that, rather than adding decorative palette icons.

shared support team only needed Update Contact, Update Tag, Assign Agent, Simple Text on the happy path. Day-one order: Write fields to CRM before assign. After the hello: Tag intent.

Text: “Passing you to a person.” Do that before you add another Condition. shared support team already tried the pretty version.

The adult move: Assign Agent. After that, Train agents to read the card first. Update Tag remains the escape when the answer is messy. See also bot to human handover.

What fails once real customers tap?

Attributed example, from a WAPilot shared support team workspace (2026): assign first, update later—race left cards empty. CRM nodes then Assign Agent, never reverse

shared support team then judged the path on finished jobs and escapes to humans—not on bot bubble count.

Rule sources: Cloud API templates and session rules. shared support team dropped a promo template into this journey and watched quality dip.

How does this sit next to replies and drips?

How we know: canvas coaching for shared support team. The path either qualifies, books, or routes, or it is theatre. Source of truth is Cloud API docs.

Campaigns open the door. This path walks Update Contact, Update Tag, Assign Agent, Simple Text. Pasting blast copy into the shared support team journey is how reports start.

One WABA, two brands, two shared support team-style journeys: quality is still one score. Split numbers before you publish.

Test on a cheap SIM for shared support team: Write fields to CRM before assign. then garbage input. Confirm tags on the contact before you spend on ads.

A typical shared support team publish went wrong because assign first, update later—race left cards empty. Changing the graph to CRM nodes then Assign Agent, never reverse stopped the screenshot pile-up.

Palette for this job: Update Contact, Update Tag, Assign Agent, Simple Text. If a node is not in that list, it waits for v2. Start with this: Write fields to CRM before assign. Then: Tag intent.

Unglamorous but required: Text: “Passing you to a person.” Without it, Update Contact, Update Tag, Assign Agent, Simple Text sit unused and the customer still stalls.

Assign Agent. Train agents to read the card first. If neither is on the canvas, shared support team will staff chaos from a phone gallery.

FAQs

How long does recovery take after you stop a bad bot at shared support team?

Days for rating if reports stacked on shared support team; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.

Does handoff open a new Meta window?

No. Same thread, same clock. Agents should not wait for a “fresh 24 hours.”

Can this flow send free-form chat after 24 hours of silence?

No. Bots share the care window with humans at shared support team. After it closes, you need a template or a new customer message—not another Update Contact bubble.

Does Update Tag reset the customer care window?

No. Handoff is ownership. Shared numbers still share reports. shared support team cannot isolate that with a tag on Update Contact, Update Tag, Assign Agent, Simple Text.

Keep the shared support team path thin, keep Update Tag, keep the window in mind. Start a free trial if this layer is still missing.