Click-to-WhatsApp flow: CTWA flow: ad click → New contact → menu. CTWA is not a trigger type; first journey is New contact. See why. Read how. Start here.
Click-to-WhatsApp flow is the canvas job clinic CTWA should ship this week. Paying Meta for chats that land on a keyword flow nobody triggers? Wrong trigger or no Interactive Buttons wastes spend and nights.
Sales and ops both touch this clinic CTWA job. We kept the language on the canvas, not on theory.
You'll map New contact, Interactive Buttons, Update Tag, Assign Agent onto one path and reuse the fix clinic CTWA needed after a messy first publish.
clinic CTWA tickets look alike: too many branches, no Interactive Buttons, then an angry screenshot.
One New contact flow for paid chat. First line matches the ad. That is enough setup talk for clinic CTWA before the first heading.
CTWA flow: ad click → New contact → menu. CTWA is not a trigger type; first journey is New contact. clinic CTWA should treat that sentence as the job, not a slide title.
Sources: Meta’s send-messages guide (session vs template) and messaging limits. Traffic for clinic CTWA is still Cloud API, using New contact, Interactive Buttons, Update Tag, Assign Agent.
CTWA flow: ad click → New contact → menu. CTWA is not a trigger type; first journey is New contact. On the canvas you place New contact, Interactive Buttons, Update Tag, Assign Agent. clinic CTWA teams finish one job, then use Interactive Buttons when the customer sends a photo or a rant.
This is not a campaign. Canvas setup for clinic CTWA: WhatsApp Flow Builder.
In this series — Part 1 of 7 (Meta Ads Flows). Next: welcome message sequences. This is the series start.
Build as if an intern at clinic CTWA edits it in June. Node titles should be jobs, not “step 12.”
In a clinic CTWA thread (2026), the failure was concrete: only “hi” keyword flow; ad users never typed hi. The rewrite that stuck was New contact welcome matching the ad headline. Repeat that, rather than adding decorative palette icons.
clinic CTWA only needed New contact, Interactive Buttons, Update Tag, Assign Agent on the happy path. Day-one order: One New contact flow for paid chat. After the hello: First line matches the ad.
Tag CTWA/source. Do that before you add another Condition. clinic CTWA already tried the pretty version.
The adult move: Menu or book. After that, Staff during the ad flight. Interactive Buttons remains the escape when the answer is messy. See also WhatsApp Flow Builder.
Attributed example, from a WAPilot clinic CTWA workspace (2026): only “hi” keyword flow; ad users never typed hi. New contact welcome matching the ad headline
Shorter copy cut invalid replies more than another Condition node did for clinic CTWA.
Rule sources: send-messages, message templates, limits. Every send for clinic CTWA should map to one of those—not “the bot felt urgent.”
How we know: this journey going live on customer orgs (including clinic CTWA-shaped ones), transcripts checked against send-messages. No unofficial connector.
Hand to the inbox, do not argue with it. After assign, canned replies are the agent’s tool at clinic CTWA. bot to human handover covers the queue.
STOP mid-path at clinic CTWA: suppress, offer a human for account issues, do not loop the menu built from New contact, Interactive Buttons, Update Tag, Assign Agent.
After a change, publish v2 and turn v1 off. Two listeners on one clinic CTWA keyword is an outage.
A typical clinic CTWA publish went wrong because only “hi” keyword flow; ad users never typed hi. Changing the graph to New contact welcome matching the ad headline stopped the screenshot pile-up.
Palette for this job: New contact, Interactive Buttons, Update Tag, Assign Agent. If a node is not in that list, it waits for v2. Start with this: One New contact flow for paid chat. Then: First line matches the ad.
Unglamorous but required: Tag CTWA/source. Without it, New contact, Interactive Buttons, Update Tag, Assign Agent sit unused and the customer still stalls.
Menu or book. Staff during the ad flight. If neither is on the canvas, clinic CTWA will staff chaos from a phone gallery.
Often days of clean chats if people reported clinic CTWA—not an hour. Stopping the flow does not open a new 24-hour window. Wait for inbound or use a fitting approved template.
On the contact (ads attribution), not as a Flow Builder trigger. You still tag and assign in the flow.
No. Assign Agent does not extend Meta’s clock for clinic CTWA. Template or wait. New contact, Interactive Buttons, Update Tag, Assign Agent do not change that.
Not safely at scale. Opt-in and quality are per number. Tags do not hide brand B from Meta when clinic CTWA shares the WABA.
Build the five steps for a clinic CTWA-like job, not a museum of nodes. Start a free trial on WAPilot to run Click-to-WhatsApp flow on Cloud API.
ads to booking flow: Ads → catalog or booking: paid chat that sells the thing in the ad—slot or product—then human if needed. See why. Read how. Start here.
Read MoreStart automating your WhatsApp marketing today with WA-Pilot. Join thousands of businesses already growing with our platform.
Start Free Trialassign ads leads: Assign and tag ads leads: source label in the flow, Meta ad routing in Team Assignment, then sub-flow for the product. See why. Read how.
Read MoreCAPI in ads flow: Meta CAPI in an ads flow: fire Lead/Purchase after chat qualify so Ads Manager sees the WhatsApp truth. See why. Read how. Start here.
Read More