send template: Send Template inside a flow must match the window: utility for status, marketing only when policy and opt-in allow. See why. Read how. This week.
send template is the canvas job ecommerce COD team should ship this week. Dropping a marketing template into an open support chat because the flow “needed a header”? Wrong trigger or no Flow Builder wastes spend and nights.
Skip it if you only blast lists. ecommerce COD team needs a chat path, not a campaign.
Stay on this ecommerce COD team job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in ecommerce COD team reviews would rather ship a thin v1 than hoard unpublished nodes.
If the customer just wrote, prefer session Simple Text. Outside the window, pick an approved template category that matches content. That is enough setup talk for ecommerce COD team before the first heading.
this node inside a flow must match the window: utility for status, marketing only when policy and opt-in allow. ecommerce COD team should treat that sentence as the job, not a slide title.
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—ecommerce COD team on a grey gateway is another product.
this step inside a flow must match the window: utility for status, marketing only when policy and opt-in allow. On the canvas you place that component, Delay, Simple Text. ecommerce COD team teams finish one job, then use Flow Builder when the customer sends a photo or a rant.
This is not a campaign. Canvas setup for ecommerce COD team: WhatsApp Flow Builder.
In this series — Part 5 of 6 (Message Components). Previous: interactive list. Next: invalid reply fallback. Series start: simple text node.
Order: trigger, hello, If the customer just wrote, prefer session Simple Text., then Flow Builder. That is v1 for ecommerce COD team.
In a ecommerce COD team thread (2026), the failure was concrete: marketing template used for “your order shipped”. The rewrite that stuck was utility template for shipping; marketing stayed in campaigns. Repeat that, rather than adding decorative palette icons.
ecommerce COD team only needed the canvas action, Delay, Simple Text on the happy path. Day-one order: If the customer just wrote, prefer session Simple Text. After the hello: Outside the window, pick an approved template category that matches content.
Map variables exactly as Meta approved them. Do that before you add another Condition. ecommerce COD team already tried the pretty version.
The adult move: Do not mix a promo body into a utility template. After that, Test expiry: wait out the window on a test chat. Flow Builder remains the escape when the answer is messy. See also WhatsApp drip sequences.
Attributed example, from a WAPilot ecommerce COD team workspace (2026): marketing template used for “your order shipped”. utility template for shipping; marketing stayed in campaigns
ecommerce COD team also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: templates when silent; send-messages when the window is live; limits if ecommerce COD team nags. Read those before stacking Delay after this path.
How we know: WAPilot implementation plus inbox on official Cloud API—drip sequences, human handover, Flow Builder. ecommerce COD team here matches those queues and Meta’s public docs, using this node, Delay, Simple Text.
One sentence? Use drip sequences. A week of follow-ups? human handover. Branches and Flow Builder stay on the canvas for ecommerce COD team.
Do not park ecommerce COD team reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after this step.
Walk the false branch. A ecommerce COD team path that only works on perfect taps will strand the first typo after Outside the window, pick an approved template category that matches content.
A typical ecommerce COD team publish went wrong because marketing template used for “your order shipped”. Changing the graph to utility template for shipping; marketing stayed in campaigns stopped the screenshot pile-up.
Palette for this job: this node, Delay, Simple Text. If a node is not in that list, it waits for v2. Start with this: If the customer just wrote, prefer session Simple Text. Then: Outside the window, pick an approved template category that matches content.
Stop it, staff the inbox for ecommerce COD team, template only when needed. Rating can take days. Delay nodes do not rewrite Meta’s window.
It can, but you usually should not. Session messages are free-form and cheaper in spirit. Save templates for when the window is closed.
Delay until a weekday, then a utility template if ecommerce COD team went quiet. Do not assume session is still alive after Send Template.
No. One thread, one clock. Two brands on one WABA share quality too. Split numbers before ecommerce COD team collides with another brand’s promos.
send template only counts live. When you want Send Template on official Cloud API for ecommerce COD team, start a free trial on WAPilot.
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