ask question: The Ask Question node captures free-text into a variable you can map to CRM and later messages. See why. Read how. Start here. Try WAPilot.
ask question is the canvas job coaching discovery should ship this week. Agents re-asking name and email that the bot already collected? Wrong trigger or no Flow Builder wastes spend and nights.
Written for people who will publish this coaching discovery journey this week—not for a strategy offsite.
You get a five-step build, the real nodes (this node, Update Contact, Simple Text), and why coaching discovery had to cut half the graph.
We would rather coaching discovery publish with Update Contact and an agent exit than collect features “for later.”
Ask one thing at a time (name, then email, then city). Name the variable clearly (lead_email, not q1). That is enough setup talk for coaching discovery before the first heading.
The this step node captures free-text into a variable you can map to CRM and later messages. coaching discovery should treat that sentence as the job, not a slide title.
Sources: WhatsApp messaging limits and Cloud API send-messages. That pairing explains why coaching discovery goes quiet after a day of silence on that component.
The the canvas action node captures free-text into a variable you can map to CRM and later messages. On the canvas you place this path, Update Contact, Simple Text. coaching discovery teams finish one job, then use Flow Builder when the customer sends a photo or a rant. Official Cloud API session windows and templates still apply after publish.
Publish buttons live in WhatsApp Flow Builder. Here we only design the coaching discovery graph with this node, Update Contact, Simple Text.
In this series — Part 1 of 5 (Ask & Variables). Next: ask buttons. This is the series start.
If a template already includes this step, start there and delete what coaching discovery does not need.
A typical coaching discovery publish went wrong because five questions before any value. Changing the graph to name + goal only, then Booking Flow stopped the screenshot pile-up.
Palette for this job: that component, Update Contact, Simple Text. If a node is not in that list, it waits for v2. Start with this: Ask one thing at a time (name, then email, then city). Then: Name the variable clearly (lead_email, not q1).
Unglamorous but required: Update Contact so the inbox shows the fields. Without it, the canvas action, Update Contact, Simple Text sit unused and the customer still stalls.
Validate lightly in copy (“use digits only”) rather than punishing typos. Always allow skip-to-agent after two asks. If neither is on the canvas, coaching discovery will staff chaos from a phone gallery.
Attributed example, from a WAPilot coaching discovery workspace (2026): five questions before any value. name + goal only, then Booking Flow
coaching discovery then judged the path on finished jobs and escapes to humans—not on bot bubble count.
Rule sources: send-messages, message templates, limits. Every send for coaching discovery should map to one of those—not “the bot felt urgent.”
How we know: canvas coaching for coaching discovery. The path either qualifies, books, or routes, or it is theatre. Source of truth is Cloud API docs.
Campaigns open the door. This path walks this path, Update Contact, Simple Text. Pasting blast copy into the coaching discovery journey is how reports start.
One WABA, two brands, two coaching discovery-style journeys: quality is still one score. Split numbers before you publish.
Test on a cheap SIM for coaching discovery: Ask one thing at a time (name, then email, then city). then garbage input. Confirm tags on the contact before you spend on ads.
Inside coaching discovery ops, they learned the hard way: five questions before any value. They recovered only after name + goal only, then Booking Flow. That is the v1 bar for this journey.
Keep this node, Update Contact, Simple Text visible in the flow name so the next editor knows the job. First moves: Ask one thing at a time (name, then email, then city). Name the variable clearly (lead_email, not q1).
Often days of clean chats if people reported coaching discovery—not an hour. Stopping the flow does not open a new 24-hour window. Wait for inbound or use a fitting approved template.
Usually no. Confirm only if the number failed delivery. Re-asking every field trains people to hate the bot.
No. Assign Agent does not extend Meta’s clock for coaching discovery. Template or wait. Ask Question, Update Contact, Simple Text do not change that.
Not safely at scale. Opt-in and quality are per number. Tags do not hide brand B from Meta when coaching discovery shares the WABA.
Build the five steps for a coaching discovery-like job, not a museum of nodes. Start a free trial on WAPilot to run ask question 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