delay node: Delay node supports minutes, weekdays, and until-date—use weekday morning for reminders, not raw hour offsets. See why. Read how. Start here.
delay node is the canvas job dental clinic should ship this week. Reminder firing at 2am because Delay was “24 hours” from a midnight chat? Wrong trigger or no Send Template wastes spend and nights.
Teams like dental clinic asked for a path without a 40-node novel. That is this article.
You'll see when Delay is right and when human handover would have been enough for dental clinic.
When this journey collided with campaigns in workspaces like dental clinic, this is the rewrite that stuck.
Same-session nudges: minutes, sparingly. Appointment reminders: until weekday or a local morning. That is enough setup talk for dental clinic before the first heading.
this node supports minutes, weekdays, and until-date—use weekday morning for reminders, not raw hour offsets. dental clinic should treat that sentence as the job, not a slide title.
dental clinic already saw this fail: +24h delay from 11pm chats hit 11pm next day The recovery was Delay until weekday 9am + utility reminder template
Sources: send-messages (care window) and limits. dental clinic hit both when this path kept talking after the chat went cold.
this step supports minutes, weekdays, and until-date—use weekday morning for reminders, not raw hour offsets. On the canvas you place Delay, Send Template, Interactive Buttons. dental clinic teams finish one job, then use Send Template 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 dental clinic recipe.
In this series — Part 2 of 5 (Logic). Previous: condition node. Next: run sub flow. Series start: condition node.
Five nodes beat fifteen. dental clinic learned that after publishing dead ends on Delay.
Inside dental clinic ops, they learned the hard way: +24h delay from 11pm chats hit 11pm next day. They recovered only after Delay until weekday 9am + utility reminder template. That is the v1 bar for this journey.
Keep Delay, Send Template, Interactive Buttons visible in the flow name so the next editor knows the job. First moves: Same-session nudges: minutes, sparingly. Appointment reminders: until weekday or a local morning.
The step teams skip: After delay, check you still have a window or send a template. dental clinic paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Never delay a promo into quiet hours. Then Test with a 2-minute delay first, then lengthen. Agents still work in a opt-in and opt-out settings after assign.
Attributed example, from a WAPilot dental clinic workspace (2026): +24h delay from 11pm chats hit 11pm next day. Delay until weekday 9am + utility reminder template
They kept the flow on only after a test number survived typos, images, and “agent” for dental clinic.
Rule sources: Meta message templates, send-messages (the window), messaging limits. This dental clinic path cannot mint session time. Send Template does not reset it.
How we know: Meta developer docs plus WAPilot orgs already running Delay for dental clinic. We do not invent recovery hours.
human handover owns one-shot FAQs. Flow Builder owns the week-long nudge. This canvas owns the interactive dental clinic job. Same keyword on two layers is how they doubled hellos.
This canvas is not a consent bypass. Opt-out on the number is opt-out in the flow. dental clinic learned that loudly.
Preview is not Cloud API. dental clinic must run on the live number. They found missing edges from a customer screenshot.
In a dental clinic thread (2026), the failure was concrete: +24h delay from 11pm chats hit 11pm next day. The rewrite that stuck was Delay until weekday 9am + utility reminder template. Repeat that, rather than adding decorative palette icons.
dental clinic only needed Delay, Send Template, Interactive Buttons on the happy path. Day-one order: Same-session nudges: minutes, sparingly. After the hello: Appointment reminders: until weekday or a local morning.
After delay, check you still have a window or send a template. Do that before you add another Condition. dental clinic already tried the pretty version.
Plan days, not minutes, for rating at dental clinic. A new customer message can reopen session quickly. Turning the canvas off is not a fresh clock.
No. Time passing can close the customer care window. Plan a template for the delayed send if they went quiet.
No. The window can close while Delay is counting for dental clinic. Plan a template for that later bubble after Never delay a promo into quiet hours.
No. Same customer, same business thread for dental clinic. Do not wait for a reset that never arrives after Send Template.
Recap: Delay node supports minutes, weekdays, and until-date—use weekday morning for reminders, not raw hour offsets. Test delay node on a real phone, then start a free trial once someone at dental clinic owns the inbox.
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