flow design
WhatsApp Flow Builder: Design Rules, Lookups and Handoffs
Write the decision path before designing a canvas: what starts the conversation, what data the task needs, which actions are permitted and when a person should take over. A flow diagram helps review those choices; it does not prove that every node is available.
Confirm the visual editor, node types, integrations, AI options and plan terms enabled for your account. This page describes designs to scope, not a deployed agent, unlimited integration access or measured savings.
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Illustrative workflow
Define the trigger
Choose an eligible incoming message, supported event or schedule. Confirm payload and permission scope.
Branch on verified data
Validate required fields, retrieve only authorized records and define missing/stale/error paths.
Perform a permitted action
Use an eligible message format or supported API action. Keep financial or destructive decisions within explicit authority.
Hand off and review
Carry the relevant context to a designated person; evaluate failed and uncertain paths before wider use.
Fixed rules, an automation graph or an in-app form?
Choose the tool around the task. Visual design does not remove the need for integration work and access controls.
On a narrow screen, scroll the table horizontally to read every column.
| Approach | Useful for | Constraint |
|---|---|---|
| Fixed reply/menu | Known questions and stable choices | Define unmatched input and human help |
| Automation graph | Branching, data lookups and action sequencing | Confirm nodes, limits, auth and failure paths |
| WhatsApp Flows | Structured in-app interactions where supported | Confirm the actual form, data exchange and platform contract |
| AI assistance | Varied wording or document retrieval | Evaluate accuracy, allowed actions and escalation |
Separate the canvas, AI and provider access
These are different setup questions. Confirm each enabled feature and its cost rather than treating them as one default bundle.
Visual canvas
If available, confirm trigger/action/condition editing, versioning, test mode, loop guards and who can publish a change.
AI with a knowledge base
Retrieval-Augmented Generation (RAG) retrieves document context for a model response. It can still retrieve incomplete information or produce a wrong answer; require evaluation and a no-answer/handoff path.
Bring Your Own API
If supported, scope the AI provider, credentials, quota and billing separately. Direct provider billing does not prove a fixed saving, data residency or regulatory compliance.
Map the node contract before connecting it
Candidate node roles include trigger, condition, message action, HTTP lookup, data mapping and human routing. Obtain the current list supported by the editor; confirm authentication, payload schemas, timeout, rate limit and permissions for every external action.
Data and HTTP
An order lookup needs an authorized customer match and an endpoint contract. A provider name does not establish a prebuilt connector or access to every API.
Routing
Define the handoff queue, staffed hours and fallback if nobody is available. A sentiment signal may assist routing but must not be the only way to ask for a person.
A knowledge base needs its own checks
Agree the permitted documents, ingestion method, retrieval freshness, source attribution and access boundaries. PDFs, URLs or other sources must be supported by the enabled setup. Test missing answers and contradictory documents; retrieval does not guarantee accuracy.
On a narrow screen, scroll the table horizontally to read every column.
| Stage | Question to settle |
|---|---|
| Source | Which permitted documents and versions are included? |
| Index | How are documents prepared and refreshed? |
| Retrieve | How is a relevant authorized passage selected? |
| Generate | What may the model answer or act on? |
| Review | What happens when evidence is missing or confidence is low? |
Use cases to evaluate in a permitted pilot
Hypothetical designs: a cart follow-up checks contact permission and purchase state; lead qualification captures a request and routes it to sales; support retrieves an authorized order status and escalates a dispute. No ticket deflection, response-time, conversion or recovered-revenue result is supplied.
Adapt the task without assuming industry compliance
An ecommerce status lookup, real-estate enquiry or appointment change needs a specific data contract and routing owner. Sensitive financial or health information requires its own review; an industry label is not approval for autonomous decisions.
Review permissions, providers and records
Confirm contact permission, message/template eligibility, credential storage, processing locations, retention and access controls. Do not infer DLT registration, DPDP compliance or India residency from a flow, an opt-in node or a chosen AI provider.
Illustrative missing-order path
Hypothetical customer question: “I ordered a blue shirt last Tuesday but have not received it.” Verify the customer and order match; retrieve the authorized order/dispatch record; answer only from current fields. If the match or delivery date is unclear, say so and route to support. No actual order, live tracking or successful resolution is shown.
Messaging and setup conditions
A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.
Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Onboarding, verification, template review and integration timing depend on the account, provider, workflow and outstanding approvals. Confirm the scope and schedule with the team; no instant approval, fixed waiting period or go-live deadline is promised.
Questions about flow design
Does a visual flow mean no integration work?
No. A supported editor may simplify design, but lookups still need endpoint schemas, credentials, permissions, data mapping and failure handling.
Does RAG prevent hallucinations?
No accuracy guarantee is made. Retrieval adds document context, but the source may be stale or incomplete and the model can answer incorrectly. Test source-grounded answers and escalation.
Does using my own AI key guarantee savings?
Confirm whether that option is supported, then compare provider usage, platform fees, integration and review costs. No fixed percentage saving or residency assurance follows from a key.
Is this the same as WhatsApp Flows?
A business automation graph and a supported in-app form solve different tasks. Confirm the actual editor/node contract and Meta Flows support before choosing how they connect.
Can the flow activate a service from this page?
No. This page explains a design. Send an enquiry to confirm enabled tools, commercial terms, a permitted test environment and who authorizes publication.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support in your signed service agreement.
Discuss your flow design setup
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Send an enquiry