automation priority: Wapilot automation priority is AI Reply, then Basic Replies, then Automated Flows. Design for that order so customers get one voice.
automation priority is the canvas job multi-brand salon group should ship this week. AI, basic replies, and a flow all firing on “hi”—who wins? Wrong trigger or no Basic Replies wastes spend and nights.
Skip it if you only blast lists. multi-brand salon group needs a chat path, not a campaign.
Stay on this multi-brand salon group job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in multi-brand salon group reviews would rather ship a thin v1 than hoard unpublished nodes.
Open settings and confirm this node: AI → basic replies → flows. Decide which layer owns greetings; turn the others off for that keyword. That is enough setup talk for multi-brand salon group before the first heading.
Wapilot this step is AI Reply, then Basic Replies, then Automated Flows. Design for that order so customers get one voice. multi-brand salon group should treat that sentence as the job, not a slide title.
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—multi-brand salon group on a grey gateway is another product.
Wapilot that component is AI Reply, then Basic Replies, then Automated Flows. Design for that order so customers get one voice. On the canvas you place AI Reply, Basic Replies, Flow Builder. multi-brand salon group teams finish one job, then use Basic Replies when the customer sends a photo or a rant.
This is not a campaign. Canvas setup for multi-brand salon group: WhatsApp Flow Builder.
In this series — Part 3 of 5 (What to Automate). Previous: auto-reply vs flows. Next: keyword menu. Series start: WhatsApp automation.
Order: trigger, hello, Open settings and confirm the canvas action: AI → basic replies → flows., then Basic Replies. That is v1 for multi-brand salon group.
In a multi-brand salon group thread (2026), the failure was concrete: AI and a welcome flow both greeted every new chat. The rewrite that stuck was they switched AI off for the welcome keyword and let the flow own the menu. Repeat that, rather than adding decorative palette icons.
multi-brand salon group only needed AI Reply, Basic Replies, Flow Builder on the happy path. Day-one order: Open settings and confirm this node: AI → basic replies → flows. After the hello: Decide which layer owns greetings; turn the others off for that keyword.
Give AI a knowledge boundary and an escalate phrase. Do that before you add another Condition. multi-brand salon group already tried the pretty version.
The adult move: Keep flows for structured jobs the AI should not improvise. After that, Test “hi”, a FAQ, and “agent” in a real thread before publish. Basic Replies remains the escape when the answer is messy. See also WhatsApp drip sequences.
Attributed example, from a WAPilot multi-brand salon group workspace (2026): AI and a welcome flow both greeted every new chat. they switched AI off for the welcome keyword and let the flow own the menu
multi-brand salon group also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: Cloud API templates and session rules. multi-brand salon group 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-brand salon group here matches those queues and Meta’s public docs, using AI Reply, Basic Replies, Flow Builder.
One sentence? Use human handover. A week of follow-ups? Flow Builder. Branches and Basic Replies stay on the canvas for multi-brand salon group.
Do not park multi-brand salon group reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after AI Reply.
Walk the false branch. A multi-brand salon group path that only works on perfect taps will strand the first typo after Decide which layer owns greetings; turn the others off for that keyword.
Days for rating if reports stacked on multi-brand salon group; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.
Not in product settings. If a flow must win, disable AI Reply and basic replies for that trigger, or use a keyword the other layers ignore.
No. Bots share the care window with humans at multi-brand salon group. After it closes, you need a template or a new customer message—not another AI Reply bubble.
No. Handoff is ownership. Shared numbers still share reports. multi-brand salon group cannot isolate that with a tag on AI Reply, Basic Replies, Flow Builder.
Keep the multi-brand salon group path thin, keep Basic Replies, 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