Skip to main content

WhatsApp Flows

WhatsApp Flows (/whatsapp-business/flows) implements Meta's interactive screen flows—multi-step forms inside WhatsApp for bookings, surveys, and lead capture. Flows complement Conversation Builder branching: use Flows when you need structured fields; use Conversation Builder for lighter bot paths.

Video

Video coming soon for this topic

Who can do this​

WhatsApp Business admins.

Before you begin​

  • Business account connected
  • Meta Flow requirements met (business verification, approved use case)
  • Entry point planned (template button, ad, QR)

What you'll accomplish​

  • Flow designed, published to Meta, and attached to an entry point
  • Test submission captured in CRM or webhook destination

Step-by-step procedure​

Create a Flow​

  1. Open WhatsApp Flows (/whatsapp-business/flows).
  2. Select Create Flow.
  3. Add screens: titles, inputs, validation, submit actions.
  4. Map completion data to workspace fields or integrations.
  5. Publish to Meta—wait for approval if required.

Attach entry points​

  1. Edit related Template CTA or Conversation Builder node.
  2. Link published Flow ID.
  3. Send test template to internal number; complete Flow on device.

Monitor​

  1. Review completions in Analytics (/whatsapp-business/analytics).
  2. Cross-check contacts created via Smart Flows triggers.

Extended guidance​

Flows excel at structured data—use them when Conversation Builder free-text becomes unmanageable. Pilot with internal numbers before attaching Flow CTAs to paid ads. Archive draft Flows seasonally so Meta review queues stay uncluttered.

Practice scenarios​

Publish a two-screen Flow, attach to a template button, complete it on mobile, confirm CRM field population.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Flow status Published in Meta
  • Test submission visible in CRM
  • Error rate low in analytics

Tips​

important

Flows must comply with Meta commerce and data policies—avoid collecting sensitive categories without legal review.

Troubleshooting​

| Flow rejected | Simplify fields; resubmit in Meta | | Button does not open Flow | Template not synced after publish | | Data missing in CRM | Check Flow webhook / Smart Flow mapping |

See also​