welcome new contact: Welcome new contact: first message → menu → right sub-flow. Use the welcome template. See why. Read how. Start here. Try WAPilot.
welcome new contact is the canvas job local services brand should ship this week. New chats seeing a campaign blast instead of a hello? Wrong trigger or no Media wastes spend and nights.
Sales and ops both touch this local services brand job. We kept the language on the canvas, not on theory.
You'll map New contact trigger, Media, Interactive Buttons, Run Sub Flow onto one path and reuse the fix local services brand needed after a messy first publish.
local services brand tickets look alike: too many branches, no Media, then an angry screenshot.
Trigger New contact. Short brand hello + optional media. That is enough setup talk for local services brand before the first heading.
this node: first message → menu → right sub-flow. Use the welcome template. local services brand should treat that sentence as the job, not a slide title.
local services brand already saw this fail: welcome plus a sale template immediately The recovery was menu first; drip only after a tap or a day
Sources: Meta’s send-messages guide (session vs template) and messaging limits. Traffic for local services brand is still Cloud API, using New contact trigger, Media, Interactive Buttons, Run Sub Flow.
this step: first message → menu → right sub-flow. Use the welcome template. On the canvas you place New contact trigger, Media, Interactive Buttons, Run Sub Flow. local services brand teams finish one job, then use Media when the customer sends a photo or a rant. Official Cloud API session windows and templates still apply after publish.
Need palette click-path? Use WhatsApp Flow Builder, then return to this local services brand recipe.
In this series — Part 1 of 5 (Support & Welcome). Next: paid vs organic. This is the series start.
Build as if an intern at local services brand edits it in June. Node titles should be jobs, not “step 12.”
Inside local services brand ops, they learned the hard way: welcome plus a sale template immediately. They recovered only after menu first; drip only after a tap or a day. That is the v1 bar for this journey.
Keep New contact trigger, Media, Interactive Buttons, Run Sub Flow visible in the flow name so the next editor knows the job. First moves: Trigger New contact. Short brand hello + optional media.
The step teams skip: Three buttons to sub-flows. local services brand paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Tag source organic. Then Do not enrol a marketing drip in the same second. Agents still work in a WhatsApp Flow Builder after assign.
Attributed example, from a WAPilot local services brand workspace (2026): welcome plus a sale template immediately. menu first; drip only after a tap or a day
Shorter copy cut invalid replies more than another Condition node did for local services brand.
Rule sources: send-messages, message templates, limits. Every send for local services brand should map to one of those—not “the bot felt urgent.”
How we know: this journey going live on customer orgs (including local services brand-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 local services brand. bot to human handover covers the queue.
STOP mid-path at local services brand: suppress, offer a human for account issues, do not loop the menu built from New contact trigger, Media, Interactive Buttons, Run Sub Flow.
After a change, publish v2 and turn v1 off. Two listeners on one local services brand keyword is an outage.
In a local services brand thread (2026), the failure was concrete: welcome plus a sale template immediately. The rewrite that stuck was menu first; drip only after a tap or a day. Repeat that, rather than adding decorative palette icons.
local services brand only needed New contact trigger, Media, Interactive Buttons, Run Sub Flow on the happy path. Day-one order: Trigger New contact. After the hello: Short brand hello + optional media.
Often days of clean chats if people reported local services brand—not an hour. Stopping the flow does not open a new 24-hour window. Wait for inbound or use a fitting approved template.
One New contact flow. Use Condition or copy variants if ads need a different first line—do not run two New contact flows.
No. Assign Agent does not extend Meta’s clock for local services brand. Template or wait. New contact trigger, Media, Interactive Buttons, Run Sub Flow do not change that.
Not safely at scale. Opt-in and quality are per number. Tags do not hide brand B from Meta when local services brand shares the WABA.
Build the five steps for a local services brand-like job, not a museum of nodes. Start a free trial on WAPilot to run this journey 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