Test your first WhatsApp conversation
Confirm inbound delivery and a human reply on your connected Waaru number, then choose the next task for workflows, campaigns, or a server integration.
Reviewed
Prove that a customer message reaches the right workspace and that your team can reply before building a larger workflow. Use a separate WhatsApp account you control or have permission to test with.
The customer-service window lasts 24 hours after the customer’s latest message to your business number. A free-form reply is a message you type yourself. It does not need a template while the window is open, but the other sending checks still apply. Outside that window, use an eligible approved template.
Before you test
- Create the workspace and connect the exact number.
- Confirm that the number is connected in Numbers.
- Give the testing teammate the required workspace role and access to that number. See team access.
- For a first manual test, use a number without an active Logic Flow so the message can reach the human Inbox. If a flow already handles it, follow its configured handoff instead.
You do not need a broadcast, imported audience, or approved template to test an eligible reply to a new inbound message.
Receive and answer one message
- Send a short message from your test WhatsApp account to the connected business number.
- In Waaru, open Inbox and choose the correct WhatsApp number.
- Find the test conversation and confirm its message and contact details.
- Select Assign to me when the conversation is unassigned.
- Confirm that the customer-service window is open. Type a reply and select Send.
- Check the message state in Waaru and confirm receipt on the test account. A queued or submitted message is not proof of delivery.
If another teammate owns the conversation, coordinate the assignment before replying. See work in Inbox for notes, saved replies, resolution, and recovery.
If the test stops
| What you see | What to check |
|---|---|
| Number missing from Inbox | Workspace role, access to that exact number, and its connection state. |
| No inbound message | The destination number, Meta connection, and whether a published flow handled the message. |
| Reply unavailable | Assignment, conversation state, opt-out or number restriction, and the 24-hour service window. |
| Queued, failed, or no delivery | The message status and error, connected sender, and current provider state. Avoid sending duplicate replies while the outcome is uncertain. |
If the service window has closed, use an eligible approved template. A stored phone number alone is not permission to message someone. Review consent and restrictions before adding a campaign.
Choose your next task
- Answer repeatable enquiries: create a Logic Flow. Test its trigger, invalid input, and human handoff before activating a wider journey.
- Run a campaign: create a message template, prepare contacts and segments, then create a broadcast.
- Share daily work: invite teammates and configure business hours.
- Use your own server: follow the Developer API quickstart. Each number chooses either Logic Flow or Developer API for inbound handling. Test that change deliberately.
The first working setup is complete when you have confirmed the connected number, inbound message, authorized reply, and actual receipt. A saved draft or successful signup alone does not prove messaging works.
Connect a WhatsApp number
Connect a new, existing Cloud API, or WhatsApp Business app number to Waaru and confirm the correct Meta account and phone number.
Understand the Waaru dashboard
Learn how the Waaru dashboard separates daily operations, WhatsApp setup, settings, and team access. Find simple definitions of common WhatsApp and workflow terms.