Build and Test a WhatsApp Workflow for Automated Campaign Replies · WABPO
WABPO / Workflows / Build and Test a WhatsApp Workflow for Automated Campaign Replies Workflows 6 min read
Build and Test a WhatsApp Workflow for Automated Campaign Replies This SOP explains how to create, configure, test, and publish a workflow that automatically responds to customer messages and button clicks. It also covers how to reduce messaging costs by using the correct message type and timing, and how to troubleshoot workflow issues.
By Saifullah Alam Last reviewed Jun 21, 2026 Published Jun 21, 2026 Key Steps 1. Confirm prerequisites before building the workflow 0:00
Not finding what you are looking for? Chat with us or send us an email.
© 2026 WABPO Help Center
Crafted with love by Spadasoft
Verify that the account is connected.
Confirm the template has already been approved.
Make sure the campaign has been run or is ready to run.
Decide whether the message should be treated as a marketing or utility message, since pricing differs. 2. Understand message cost rules before sending 0:21
Use utility messages when the content is transactional or service-related, because they cost less than marketing messages. Remember that inbound replies from customers are free when you respond within the 24-hour window . If you send a message after 24 hours: Marketing templates are charged at marketing rates. Utility templates are charged at utility rates. Keep the message content simple if you want it to qualify as utility rather than marketing. 3. Create a trigger for a customer keyword or action 1:36
Build a workflow trigger based on a customer message such as "tell me more" . Use the trigger to start the automation only when the exact keyword or matching condition is received. Keep the first response short and clear, then continue the conversation through buttons or follow-up steps. 4. Send the first automated response with a call to action 1:52
After the trigger fires, send a message with the offer or key information. Example: notify the customer that a credit offer expires by the end of the day. Add a button such as "How to claim" so the customer can continue the flow without manual support. 5. Connect button clicks to the correct workflow branch 2:24
Link the "How to claim" button to the appropriate branch or node in the workflow. Ensure the button action routes the user to the next step automatically. Use clear node names so the workflow is easy to maintain later. 6. Provide setup help through a separate button flow 2:46
Add another button such as "How to connect Meta account" for setup-related questions. When the user clicks it, send a helpful resource instead of a long text explanation. Use a YouTube tutorial button or link to guide the user visually. End the flow after the tutorial is delivered if no further action is needed. 7. Keep messages short and use buttons to reduce cost and complexity 3:24
Avoid putting all instructions into one long message. Use a simple message plus buttons to guide the user to the right next step. This approach helps reduce unnecessary marketing-style messaging and keeps the workflow easier to manage. 8. Use workflows for repeated support questions 4:05
Build complete flows for common questions such as: How to connect Need a new number I got an error Speak to customer support This prevents the team from typing the same replies manually every time. Use the workflow to automatically send the correct response based on the selected option. 9. Generate or edit workflow prompts with AI when needed 5:28
If you are not technical, write the workflow idea in your own language. Use an AI assistant to generate the full prompt or workflow structure. Enter the business use case clearly, such as a restaurant workflow or customer support flow. Review the generated output before publishing. 10. Build and validate the workflow structure 6:00
Confirm the workflow contains the required nodes, such as: Trigger Category list Product or item options Validate the workflow to make sure the logic is correct. If needed, add new nodes or properties manually by dragging and dropping them into place. 11. Refine the workflow by testing specific inputs 6:34
Test the workflow by entering a sample command such as "add salad" . Check whether the system adds the item correctly without removing existing nodes. If the result is wrong, update the prompt or workflow instructions and test again. Repeat until the workflow behaves as expected. 12. Save, publish, and enable the workflow 7:17
Once the workflow is correct, save it and publish it. Enable the workflow so it can respond to live messages. Turn it on from the dashboard before sending test messages or launching a campaign. 13. Test the live trigger with the exact message format 7:32
Send a test message from your own number. Use the exact trigger phrase if the workflow is set to exact match . If the workflow should respond to variations, choose contains or wildcard instead. Confirm the trigger works for the intended message type, such as text, image, video, location, or contact. 14. Troubleshoot incorrect workflow behavior 8:19
If the workflow sends the wrong response, return to the editor and adjust the prompt or node logic. Reword the instructions clearly, such as telling the system what it should send instead. Continue testing until the output matches the intended response. 15. Review run history and failure reasons 9:07
Check the workflow run history to see how many times it has executed. If a run fails, review the failure reason shown in the system. Use the failure details to correct the workflow logic or prompt. 16. Escalate issues to support when needed 9:26
If you cannot resolve the issue yourself, use the help option. Open the WhatsApp support channel and describe the error clearly. Share what you expected the workflow to do and what actually happened. 17. Use workflows before running large campaigns 10:01
Build the workflow before sending a campaign to many users. This is especially useful when you expect many quick replies or button clicks. The workflow can automatically handle incoming responses after the campaign is sent. 18. Understand platform fees and subscription limits 10:37
Inbound workflow replies are free from Meta within the allowed window. Platform service fees may still apply depending on your subscription status. Review your plan limits for campaign messages, inbox messages, and workflow conversations. If no plan is active, service charges may apply per message. 19. Manage wallet balance and plan upgrades 11:21
Use the free credit if available before adding more balance. When the credit is used up, add funds to the wallet or upgrade the plan. Watch for discounts or promotional offers to reduce costs. Keep the account active so workflows and campaigns continue running smoothly.
Cautionary Notes Do not assume every message qualifies as a utility message; review the content carefully before sending. Make sure the trigger condition is set correctly, especially for exact , contains , or wildcard matching. Test workflows before launching a campaign to avoid sending the wrong automated response. If a workflow fails, check the failure reason before making changes. Be aware that Meta charges and platform service fees are separate. Keep an eye on wallet balance and subscription status to avoid interruptions.
Tips for Efficiency Use short messages with buttons instead of long manual explanations. Reuse workflow templates for common support questions. Let AI generate the first draft of the workflow prompt, then refine it. Validate and test each branch before publishing. Use workflows to reduce manual typing and speed up customer support. Keep tutorial links, help resources, and support options ready inside the workflow.
Link to Loom Continue exploring
Related docs
Feedback
Was this helpful? Yes No
Loading feedback…
