Test WhatsApp step by step

Start with Meta’s supplied test number to check that a message can reach your phone. Then test a connected staging business number to check the full Brixit experience.

1. Send a message from Meta’s test number

1. Open your app in Meta for Developers.
2. Open the WhatsApp API Setup or Getting Started screen. Labels may differ by app.
3. In From, choose the supplied test number.
4. In To, add your own WhatsApp phone number with its country code. Complete the recipient verification prompts and select it as the recipient.
5. Use the sample hello_world message and select Send message.
6. Open WhatsApp on your phone and confirm that the message arrived. Reply with Brixit test reply to generate an incoming message for webhook testing.

Use only recipients allowed by your app’s test-number setup. Postman’s step-by-step test message walkthrough describes the From/To verification flow. Meta also publishes an official Send Test Message example.

Expected result: the sample message arrives on your phone. This alone does not confirm that Brixit received your reply or can send messages from its inbox.

2. Understand the current test-number limitation

Brixit’s connection dialog currently uses Continue with Meta for business onboarding. It has no manual Connect Meta test number option. Sending a message in Meta’s dashboard does not automatically create a company connection in Brixit.

For a message to reach the CRM, the same WhatsApp account and phone number must have an active connection assigned to the staging company, with working webhook delivery and background workers. A webhook test in Meta alone does not establish that connection.

For an end-to-end test today: connect a dedicated staging business number through the client connection steps. To test specifically with Meta’s supplied number inside Brixit, a dedicated test-number connection path still needs to be implemented and validated. Do not paste test credentials into the client connection dialog or manually replace a client’s working connection.

3. Prepare Brixit staging

Have the platform administrator confirm these items before the phone test:

• WhatsApp is enabled for the staging installation, and its current updates are deployed.
• Meta onboarding is configured for the staging CRM domain and the intended connection type.
• The connected account’s messages reach the WhatsApp webhook, then the correct CRM company.
• The CRM message workers and integration delivery workers are running.
• The test agent can view and send WhatsApp messages and can access the test contact.
• The test contact has one unambiguous international phone number belonging to a consenting tester.

Use a separate staging company and number. A new number cannot simply replace an existing company connection; that requires a reviewed migration.

4. Check an incoming message and a CRM reply

1. From the tester’s phone, send Brixit staging test to the connected business number.
2. Open WhatsApp → Client conversations in Brixit.
3. Confirm that the message appears once under the right contact.
4. Send Received in Brixit from the CRM and check the tester’s phone.
5. Follow the message’s delivery status. An accepted or queued message is not yet proof that it arrived. A read receipt is only shown when Meta provides one.
6. Open the contact’s timeline and confirm that the conversation is visible there too.

For an existing Business app connection, also reply from the phone app. Check that its message appears once in Brixit. If history import was selected, check its status in Integrations → Apps → WhatsApp. Old history must not make an expired reply window open.

5. Check templates and a small campaign

1. Open Templates. Create a simple static text template and wait for Meta approval. Only use templates Brixit can select; the developer sample is not a substitute for this check.
2. Record the tester’s consent for the intended campaign purpose.
3. Create a campaign with just that test contact and the approved template.
4. Save it as a draft and confirm that nothing is sent.
5. Review and explicitly approve the test send, then check the phone and campaign report.
6. For a scheduled test, check the displayed UTC time before approving.

Brixit currently sends free-form replies only within 24 hours of the latest incoming customer message. Outside that window, use an approved supported template. A WhatsApp communication preference alone is not campaign consent.

If a test fails

Before inviting clients

Confirm both directions of messaging, delivery updates and agent access in staging. For Business app clients, also check app-message sync and the chosen history setting. The platform operator must complete Meta’s required business onboarding and app access approval for customer accounts; a successful developer test is not evidence of that approval. See Meta’s official platform overview for its Embedded Signup resources.

The screenshots in the connection guide use the real Brixit interface with synthetic data. They demonstrate the controls, not a successful live Meta pilot.