referral ask flow: Referral ask: after booking or order success, a later Delay, share prompt, tag. Do not tax people mid-task. See why. Read how. Start here.
referral ask flow is the canvas job salon members should ship this week. Asking for referrals in the same bubble as the booking confirm? Wrong trigger or no Simple Text wastes spend and nights.
Skip it if you only blast lists. salon members needs a chat path, not a campaign.
Stay on this salon members job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in salon members reviews would rather ship a thin v1 than hoard unpublished nodes.
Trigger from booking/pay success path. Delay a day. That is enough setup talk for salon members before the first heading.
Referral ask: after booking or order success, a later Delay, share prompt, tag. Do not tax people mid-task. salon members should treat that sentence as the job, not a slide title.
salon members already saw this fail: referral before the haircut happened The recovery was ask after completed status + delay
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—salon members on a grey gateway is another product.
Referral ask: after booking or order success, a later Delay, share prompt, tag. Do not tax people mid-task. On the canvas you place Delay, Simple Text, Update Tag, Add To Group. salon members teams finish one job, then use Simple Text when the customer sends a photo or a rant.
Publish buttons live in WhatsApp Flow Builder. Here we only design the salon members graph with Delay, Simple Text, Update Tag, Add To Group.
In this series — Part 5 of 5 (Support & Welcome). Previous: NPS feedback flow. Series start: welcome new contact.
Order: trigger, hello, Trigger from booking/pay success path., then Simple Text. That is v1 for salon members.
A typical salon members publish went wrong because referral before the haircut happened. Changing the graph to ask after completed status + delay stopped the screenshot pile-up.
Palette for this job: Delay, Simple Text, Update Tag, Add To Group. If a node is not in that list, it waits for v2. Start with this: Trigger from booking/pay success path. Then: Delay a day.
Unglamorous but required: One ask; accept no. Without it, Delay, Simple Text, Update Tag, Add To Group sit unused and the customer still stalls.
Tag advocates. Never gate support on a referral. If neither is on the canvas, salon members will staff chaos from a phone gallery.
Attributed example, from a WAPilot salon members workspace (2026): referral before the haircut happened. ask after completed status + delay
salon members also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: send-messages, message templates, limits. Every send for salon members should map to one of those—not “the bot felt urgent.”
How we know: WAPilot implementation plus inbox on official Cloud API—human handover, Flow Builder, Flow Builder. salon members here matches those queues and Meta’s public docs, using Delay, Simple Text, Update Tag, Add To Group.
One sentence? Use human handover. A week of follow-ups? Flow Builder. Branches and Simple Text stay on the canvas for salon members.
Do not park salon members reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after Delay.
Walk the false branch. A salon members path that only works on perfect taps will strand the first typo after Delay a day.
Inside salon members ops, they learned the hard way: referral before the haircut happened. They recovered only after ask after completed status + delay. That is the v1 bar for this journey.
Keep Delay, Simple Text, Update Tag, Add To Group visible in the flow name so the next editor knows the job. First moves: Trigger from booking/pay success path. Delay a day.
The step teams skip: One ask; accept no. salon members paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Tag advocates. Then Never gate support on a referral. Agents still work in a WhatsApp Flow Builder after assign.
Often days of clean chats if people reported salon members—not an hour. Stopping the flow does not open a new 24-hour window. Wait for inbound or use a fitting approved template.
If you promise cash/credit, ops must honour it. Otherwise keep the ask social (“forward our menu”).
No. Assign Agent does not extend Meta’s clock for salon members. Template or wait. Delay, Simple Text, Update Tag, Add To Group do not change that.
Not safely at scale. Opt-in and quality are per number. Tags do not hide brand B from Meta when salon members shares the WABA.
Build the five steps for a salon members-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