WhatsApp Flow Published but Not Working? Troubleshooting Guide
A WhatsApp Flow can be created and published successfully but still fail to work when a customer tries to use it.
The important thing is to identify where the flow breaks.
Is the Flow itself broken?
Or is the problem with the trigger?
Or the template?
Or the webhook?
Use the steps below to isolate the problem.
First: define the symptom
Start with one question:
What exactly isn't working?
For example:
Flow doesn't open.
Button doesn't launch Flow.
Flow opens but submission fails.
Flow works manually but not automatically.
Website form doesn't trigger it.
Flow works for one customer but not another.
Different symptoms have different causes.
Problem 1: Flow doesn't open from a keyword
Check the chatbot trigger.
Make sure:
Correct keyword is configured.
Keyword is connected to the intended bot flow.
Bot flow contains the correct WhatsApp Flow.
The bot is active.
The current reference troubleshooting workflow specifically recommends checking the keyword mapping to the correct bot flow and verifying the trigger phrase.
Problem 2: Template button doesn't open the Flow
This usually means the template and bot flow aren't connected correctly.
Check:
WhatsApp Template
↓
Button
↓
Correct Bot Flow
↓
WhatsApp Flow
The current troubleshooting reference identifies incorrect template-to-flow mapping as a common reason for this failure.
Problem 3: Template isn't triggering at all
Check the WhatsApp template.
Make sure it is:
Approved
Active
The expected template
Configured with the appropriate button
If you're using a template outside the normal customer-service window, remember that WhatsApp messaging rules still apply.
See WhatsApp Message Templates: Complete Guide.
Problem 4: Flow works in testing but not from Live Chat
Check whether the Flow is:
Published
Assigned to the correct WhatsApp bot/account
Available in the Live Chat interface
The current platform troubleshooting guidance specifically calls out unpublished or incorrectly assigned flows as causes of missing manual-flow options.
Problem 5: Flow opens but cannot be submitted
Check the form itself.
Make sure:
Required fields are configured correctly.
The field values are valid.
A Submit Button exists.
The current WhatsApp Flow builder requires a Submit Button before a form can be saved successfully.
Problem 6: Flow opens but the wrong confirmation appears
Check:
Reply Sent After Form Submit
Make sure it is pointing to the intended reply.
Remember that creating the form and configuring the post-submission reply are separate settings.
Problem 7: Website form does not trigger WhatsApp Flow
If the Flow is started from a website webhook, check the whole chain:
Website Form
↓
Webhook URL
↓
Webhook Workflow
↓
Field Mapping
↓
Phone Number
↓
Template
↓
Bot Flow
↓
WhatsApp Flow
A problem at any point can stop the process.
Problem 8: Webhook receives nothing
Submit a test form.
Then inspect the webhook workflow.
You need to confirm that ZazzyAgent actually received the request.
The current workflow uses a sample submission to capture the raw webhook data before mapping fields.
Problem 9: Webhook receives data but phone isn't mapped
This is a very common problem.
Check the phone field.
Make sure the form sends the customer's WhatsApp number in the expected international format.
For example:
+919XXXXXXXXX
rather than a local format such as:
09XXXXXXXX
The current website-to-WhatsApp workflow specifically requires the phone number to be passed in international format.
Problem 10: Webhook data exists but Flow variables are empty
The webhook may be receiving the information correctly while the field mapping is wrong.
Open the webhook workflow.
Capture a fresh sample submission.
Then map the received fields to the correct variables.
For example:
name
email
phone
service
should be mapped intentionally rather than assuming the field names match automatically.
Problem 11: The Flow works manually but not after a website submission
This is useful diagnostic information.
If:
Manual Flow → Works
but:
Website → Flow → Doesn't work
the problem is probably not the Flow itself.
Focus on:
Webhook URL
Field mapping
Phone number
Template
Button mapping
Bot Flow attachment
Problem 12: Flow doesn't appear after publishing
Refresh the WhatsApp Flow area.
Confirm the status.
Then check whether the published Flow belongs to the correct WhatsApp setup.
Don't create a second copy immediately.
Problem 13: Flow changed but customers see the old version
Check whether you edited the correct Flow and whether the latest version was saved/published as required.
Also confirm that your trigger is connected to that Flow rather than an older duplicate.
This is one reason meaningful flow names are important.
Problem 14: Flow is delayed
If you've intentionally added a delay, check the location of the Delay component.
A delay placed in the wrong branch won't affect the path you are testing.
The current troubleshooting material specifically recommends checking the placement and configuration of the Delay element when timing doesn't behave as expected.
Problem 15: Customer receives the template but the Flow doesn't start
Check the button action.
The template is only the first step.
The button needs to be connected to the appropriate Flow path.
Think:
Template
↓
Button
↓
Bot Flow
↓
WhatsApp Flow
A reliable troubleshooting method
Test each layer separately.
Test 1
Can you open the Flow manually?
If no:
Flow problem.
Test 2
Can a keyword/button launch it?
If no:
Trigger/mapping problem.
Test 3
Can a template button launch it?
If no:
Template mapping problem.
Test 4
Can a website webhook launch it?
If no:
Webhook/mapping/phone problem.
This avoids changing ten settings at once.
Checklist
Flow
[ ] Correct Flow
[ ] Saved
[ ] Published
[ ] Submit Button present
[ ] Correct screens/fields
Trigger
[ ] Correct keyword/button
[ ] Correct Bot Flow
[ ] Correct WhatsApp account
Template
[ ] Approved
[ ] Active
[ ] Correct template
[ ] Correct button mapping
Webhook
[ ] Correct webhook URL
[ ] Test submission received
[ ] Raw data captured
[ ] Fields mapped
[ ] Phone mapped correctly
Customer
[ ] Correct WhatsApp number
[ ] Correct international format
[ ] Messaging rules allow the initial message
The most important diagnostic rule
Don't say:
"The WhatsApp Flow isn't working."
Be more specific:
"The Flow works manually, but the template button isn't launching it."
That immediately narrows the problem to the trigger/mapping layer.
A structured diagnosis is much faster than repeatedly rebuilding the Flow.