keyword menu hub: One keyword menu hub: a single “hi” (or menu) keyword, then Run Sub Flow to booking, catalog, or support. See why. Read how. Start here.
keyword menu hub is the canvas job multi-service agency should ship this week. Five flows all listening to hi, all greeting at once? Wrong trigger or no Interactive List wastes spend and nights.
Skip it if you only blast lists. multi-service agency needs a chat path, not a campaign.
Stay on this multi-service agency job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in multi-service agency reviews would rather ship a thin v1 than hoard unpublished nodes.
Turn off other hi listeners. Hub trigger contains hi, hello, menu. That is enough setup talk for multi-service agency before the first heading.
One this node: a single “hi” (or menu) keyword, then Run Sub Flow to booking, catalog, or support. multi-service agency should treat that sentence as the job, not a slide title.
multi-service agency already saw this fail: welcome flow + shop flow + book flow all on hi The recovery was one hub; others started only as sub-flows
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—multi-service agency on a grey gateway is another product.
One this step: a single “hi” (or menu) keyword, then Run Sub Flow to booking, catalog, or support. On the canvas you place Trigger keywords, Interactive List, Run Sub Flow. multi-service agency teams finish one job, then use Interactive List when the customer sends a photo or a rant.
Need palette click-path? Use WhatsApp Flow Builder, then return to this multi-service agency recipe.
In this series — Part 3 of 6 (Assemble a Flow). Previous: flow architecture. Next: lead capture flow. Series start: build a flow.
Order: trigger, hello, Turn off other hi listeners., then Interactive List. That is v1 for multi-service agency.
Inside multi-service agency ops, they learned the hard way: welcome flow + shop flow + book flow all on hi. They recovered only after one hub; others started only as sub-flows. That is the v1 bar for this journey.
Keep Trigger keywords, Interactive List, Run Sub Flow visible in the flow name so the next editor knows the job. First moves: Turn off other hi listeners. Hub trigger contains hi, hello, menu.
The step teams skip: List rows call sub-flows. multi-service agency paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Keep the hub stupid on purpose. Then Document the keyword in the team wiki. Agents still work in a WhatsApp drip sequences after assign.
Attributed example, from a WAPilot multi-service agency workspace (2026): welcome flow + shop flow + book flow all on hi. one hub; others started only as sub-flows
multi-service agency also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: Cloud API templates and session rules. multi-service agency dropped a promo template into this journey and watched quality dip.
How we know: WAPilot implementation plus inbox on official Cloud API—human handover, Flow Builder, Flow Builder. multi-service agency here matches those queues and Meta’s public docs, using Trigger keywords, Interactive List, Run Sub Flow.
One sentence? Use human handover. A week of follow-ups? Flow Builder. Branches and Interactive List stay on the canvas for multi-service agency.
Do not park multi-service agency reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after Trigger keywords.
Walk the false branch. A multi-service agency path that only works on perfect taps will strand the first typo after Hub trigger contains hi, hello, menu.
In a multi-service agency thread (2026), the failure was concrete: welcome flow + shop flow + book flow all on hi. The rewrite that stuck was one hub; others started only as sub-flows. Repeat that, rather than adding decorative palette icons.
multi-service agency only needed Trigger keywords, Interactive List, Run Sub Flow on the happy path. Day-one order: Turn off other hi listeners. After the hello: Hub trigger contains hi, hello, menu.
List rows call sub-flows. Do that before you add another Condition. multi-service agency already tried the pretty version.
Days for rating if reports stacked on multi-service agency; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.
New contact can show the same menu once. Returning users type hi. Do not run both on the first inbound without testing double greetings.
No. Bots share the care window with humans at multi-service agency. After it closes, you need a template or a new customer message—not another Trigger keywords bubble.
No. Handoff is ownership. Shared numbers still share reports. multi-service agency cannot isolate that with a tag on Trigger keywords, Interactive List, Run Sub Flow.
Keep the multi-service agency path thin, keep Interactive List, 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