Booking Flow node: Booking Flow node: connect the appointment config, test the path, then add confirm copy. See why. Read how. Start here. Try WAPilot.
Booking Flow node is the canvas job physio clinic should ship this week. Canvas has Booking Flow but the node still says select config? Wrong trigger or no Simple Text wastes spend and nights.
If you own the shared inbox at physio clinic, this canvas is your problem. Developers can sit this one out.
We review the physio clinic path the same way: trigger, short copy, Simple Text, live test—then maybe more nodes.
This is Cloud API, not a grey sender. physio clinic still obeys windows and templates.
Create appointment config (Guides). Select it on the node. That is enough setup talk for physio clinic before the first heading.
this node: connect the appointment config, test the path, then add confirm copy. physio clinic should treat that sentence as the job, not a slide title.
physio clinic already saw this fail: published with empty config; users saw a dead end The recovery was publish gate: config selected + one live booking
Sources: Meta Cloud API send-messages and messaging limits. physio clinic fails on policy more often than on missing icons in Booking Flow, Simple Text, Delay.
this step: connect the appointment config, test the path, then add confirm copy. On the canvas you place Booking Flow, Simple Text, Delay. physio clinic teams finish one job, then use Simple Text when the customer sends a photo or a rant. Official Cloud API session windows and templates still apply after publish.
Publish buttons live in WhatsApp Flow Builder. Here we only design the physio clinic graph with Booking Flow, Simple Text, Delay.
In this series — Part 3 of 6 (Forms & Booking). Previous: lead-gen form flow. Next: booking confirmation flow. Series start: attach a WhatsApp form.
Name it like booking-flow-node-appo_v1. Steal a preset if physio clinic matches. Every tap needs an edge.
A typical physio clinic publish went wrong because published with empty config; users saw a dead end. Changing the graph to publish gate: config selected + one live booking stopped the screenshot pile-up.
Palette for this job: Booking Flow, Simple Text, Delay. If a node is not in that list, it waits for v2. Start with this: Create appointment config (Guides). Then: Select it on the node.
Unglamorous but required: Test a real slot. Without it, Booking Flow, Simple Text, Delay sit unused and the customer still stalls.
Confirm message after. Handle cancel/reschedule with buttons or agent. If neither is on the canvas, physio clinic will staff chaos from a phone gallery.
Attributed example, from a WAPilot physio clinic workspace (2026): published with empty config; users saw a dead end. publish gate: config selected + one live booking
Recovery was boring: shorter copy, honest Simple Text, and publish gate: config selected + one live booking. Quality stopped sliding.
Rule sources: Cloud API templates and session rules. physio clinic dropped a promo template into this journey and watched quality dip.
How we know: when this canvas double-texts Flow Builder at physio clinic, we see it in the same thread the agent sees.
Turn AI Reply off on the same trigger physio clinic uses, or you greet twice. Priority is a setting, not a wish.
STOP and quiet hours bind this physio clinic path. If campaigns already suppressed the contact, do not continue the pitch here.
QA with a photo, “ok”, and “agent”. Empty Responses at physio clinic usually means the Ask or webhook never saved after Booking Flow.
Inside physio clinic ops, they learned the hard way: published with empty config; users saw a dead end. They recovered only after publish gate: config selected + one live booking. That is the v1 bar for this journey.
Keep Booking Flow, Simple Text, Delay visible in the flow name so the next editor knows the job. First moves: Create appointment config (Guides). Select it on the node.
The step teams skip: Test a real slot. physio clinic paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Confirm message after. Then Handle cancel/reschedule with buttons or agent. Agents still work in a opt-in and opt-out settings after assign.
Days for rating if reports stacked on physio clinic; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.
Multiple configs or an Ask for branch first. One node, one config. Hub can Run Sub Flow per location.
No. Bots share the care window with humans at physio clinic. After it closes, you need a template or a new customer message—not another Booking Flow bubble.
No. Handoff is ownership. Shared numbers still share reports. physio clinic cannot isolate that with a tag on Booking Flow, Simple Text, Delay.
Keep the physio clinic path thin, keep Simple Text, keep the window in mind. Start a free trial if this layer is still missing.
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