NPS feedback flow: NPS/feedback: Delay → Ask List → Google Sheets. Ask once, then stop. See why. Read how. Start here. Try WAPilot. Guide 2026. This week.
NPS feedback flow is the canvas job clinic after visit should ship this week. Survey emails nobody opens while WhatsApp just closed a ticket? Wrong trigger or no Ask List wastes spend and nights.
Teams like clinic after visit 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 clinic after visit.
When this journey collided with campaigns in workspaces like clinic after visit, this is the rewrite that stuck.
Delay until a weekday after the job is done. Ask List 1–5 or labels. That is enough setup talk for clinic after visit before the first heading.
NPS/feedback: Delay → Ask List → Google Sheets. Ask once, then stop. clinic after visit should treat that sentence as the job, not a slide title.
clinic after visit already saw this fail: NPS the same night as surgery consult The recovery was delay +48h weekday; detractors to owner
Sources: send-messages (care window) and limits. clinic after visit hit both when this path kept talking after the chat went cold.
NPS/feedback: Delay → Ask List → Google Sheets. Ask once, then stop. On the canvas you place Delay, Ask List, Google Sheets, Update Tag. clinic after visit teams finish one job, then use Ask List 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 clinic after visit recipe.
In this series — Part 4 of 5 (Support & Welcome). Previous: AI support handoff. Next: referral ask flow. Series start: welcome new contact.
Five nodes beat fifteen. clinic after visit learned that after publishing dead ends on Delay.
Inside clinic after visit ops, they learned the hard way: NPS the same night as surgery consult. They recovered only after delay +48h weekday; detractors to owner. That is the v1 bar for this journey.
Keep Delay, Ask List, Google Sheets, Update Tag visible in the flow name so the next editor knows the job. First moves: Delay until a weekday after the job is done. Ask List 1–5 or labels.
The step teams skip: Low scores Assign Agent. clinic after visit paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Sheets for the CX lead. Then No second survey in the sequence. Agents still work in a opt-in and opt-out settings after assign.
Attributed example, from a WAPilot clinic after visit workspace (2026): NPS the same night as surgery consult. delay +48h weekday; detractors to owner
They kept the flow on only after a test number survived typos, images, and “agent” for clinic after visit.
Rule sources: Cloud API templates and session rules. clinic after visit dropped a promo template into this journey and watched quality dip.
How we know: Meta developer docs plus WAPilot orgs already running Delay for clinic after visit. We do not invent recovery hours.
human handover owns one-shot FAQs. Flow Builder owns the week-long nudge. This canvas owns the interactive clinic after visit 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. clinic after visit learned that loudly.
Preview is not Cloud API. clinic after visit must run on the live number. They found missing edges from a customer screenshot.
In a clinic after visit thread (2026), the failure was concrete: NPS the same night as surgery consult. The rewrite that stuck was delay +48h weekday; detractors to owner. Repeat that, rather than adding decorative palette icons.
clinic after visit only needed Delay, Ask List, Google Sheets, Update Tag on the happy path. Day-one order: Delay until a weekday after the job is done. After the hello: Ask List 1–5 or labels.
Low scores Assign Agent. Do that before you add another Condition. clinic after visit already tried the pretty version.
The adult move: Sheets for the CX lead. After that, No second survey in the sequence. Ask List remains the escape when the answer is messy. See also WhatsApp drip sequences.
Days for rating if reports stacked on clinic after visit; minutes for inbound to reopen session. Killing the flow does not gift free-form sends.
If the window is closed, you need an approved template that is not a disguised promo. Prefer in-session after a thank-you.
No. Bots share the care window with humans at clinic after visit. After it closes, you need a template or a new customer message—not another Delay bubble.
No. Handoff is ownership. Shared numbers still share reports. clinic after visit cannot isolate that with a tag on Delay, Ask List, Google Sheets, Update Tag.
Keep the clinic after visit path thin, keep Ask List, 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