Send a WhatsApp test message before your first order: what the Connect and Test buttons check

What Beacon Messenger verifies when you connect a WhatsApp Business account, why the test message uses hello_world, what the warnings mean, and how to read the result.

The worst time to learn that your WhatsApp connection is half-working is when a real customer places a real order and nothing arrives. The second worst is when something arrives, but it is the wrong template, or it reaches the wrong phone, or Meta accepts it and then quietly marks it failed and you never see the status because the webhook is pointed somewhere else.

Beacon Messenger front-loads those discoveries into two buttons on its WhatsApp account page: Connect, and Send a test message. This post goes through what each one actually does against Meta's API, in order, so that when one of them complains you know which of the four things you pasted is wrong, and so that a successful test means what you think it means.

What Connect checks, step by step

The connect form asks for four values from your Meta developer app: the WhatsApp Business Account ID, the phone number ID, a permanent access token and the app secret. Before any network call, the two IDs are checked to be purely numeric, because the most common paste error is grabbing a display name or a phone number instead of the ID, and the token is checked to be at least twenty characters long. Those two checks fail instantly, with a message that says which field is wrong.

Then the app talks to Meta, in this order:

  1. It asks the Graph API for the phone number record behind the phone number ID, using your token. This is the one call that has to succeed. If the token is invalid, expired, or does not have access to that number, the connect stops here and the error from Meta is shown as-is. If it succeeds, the app now knows the display phone number, the verified business name and the number's quality rating, and shows all three on the page.
  2. It lists the message templates on the WhatsApp Business Account. If this fails, the connection is still saved, but a warning says templates could not be loaded. The usual cause is a token whose permissions cover the phone number but not template management on the WABA.
  3. It subscribes your Meta app to the WABA's webhooks, which is what tells Meta to send delivery statuses and inbound replies for this account to your app's callback URL. If this fails you get a second warning, and the connection is still saved; statuses will stay stuck at sent until you subscribe the app by hand in the Meta dashboard.
  4. It stores the credentials encrypted, along with the number details, and saves whatever templates it managed to load.

The distinction matters: a hard failure in step one means nothing is saved; a warning in step two or three means you are connected and can send, but one of the two supporting pieces, templates or statuses, needs attention. The page shows the warnings next to the success message rather than hiding them, which is deliberate. A green connected badge with no templates would be a lie.

Why the test message uses hello_world

WhatsApp Cloud API does not let a business start a conversation with free text; the first message to a customer has to be an approved template. So the test cannot just send "testing 123". It has to pick a template, and it has to pick one it can fill in without knowing anything about an order.

The rule is simple. The test looks through your approved templates for one named hello_world, which is the sample template Meta creates on every new WhatsApp Business Account. If that has been deleted, it falls back to any approved template with no placeholders at all. If neither exists, it refuses with a message saying so and suggesting you create one and refresh templates. It will not guess values for a template that expects an order number, because a test that sends "Your order {{1}} has shipped" with made-up data proves less than it seems to.

The number you type is normalised before sending: spaces, dashes and brackets are stripped, a leading 00 or + is removed, and leading zeros go. What is left has to be between seven and fifteen digits, which is the E.164 range. Type the number with its country code; a national number without the code will either be rejected or, worse, land in another country.

What a sent test proves, and what it does not

A successful test writes a row in the Messages page with the trigger test, the recipient, the template name and the status sent, together with the WhatsApp message ID Meta returned. It also counts against your monthly message allowance, which is why the test is blocked with a clear message if the allowance is already used up; a test never sneaks past the cap.

What a status of sent tells you:

  • The token works for sending from this phone number ID.
  • The template is approved in the language the app picked.
  • Meta accepted the recipient number as well-formed.

What it does not yet tell you is whether the message arrived. That is what the next two statuses are for. If the webhook subscription from the connect step worked, the row moves to delivered within seconds and to read when you open it on your phone. If the row stays at sent for a minute after the message has visibly arrived, the webhook is the problem, not the sending: Meta is delivering the message but not telling the app. The Webhook section on the same page shows the callback URL and verify token to paste into the Meta dashboard, and the message status post covers what each status means in detail.

Reading the first test
What you seeWhat it meansWhat to do
Error before sending, names a fieldAn ID is not numeric or the token is too shortRe-copy the value from the Meta app dashboard
Error from Meta on connectToken invalid or lacks access to the numberGenerate a new permanent token with the WhatsApp permissions
Connected, warning about templatesToken cannot read templates on the WABAFix token permissions, then Refresh templates
Connected, warning about webhooksSubscription call failedSubscribe the app to the WABA in Meta's dashboard; check the callback URL
Test refused: no templateNo approved template without variablesCreate one or restore hello_world, then Refresh
Test sent, stays at sentStatuses are not reaching the appCheck the webhook callback URL and verify token in Meta
Test sent, then failedMeta rejected it after acceptingRead the error on the row: recipient not on WhatsApp, template paused, number quality
Test delivered and readEverything in the chain worksSwitch on your first automation

Templates, refreshed on demand

The Templates field on the connected number shows how many templates are loaded and when they were last synced, with a Refresh button beside it. Templates live in Meta, not in the app; the app keeps a copy so it can show you the body text and count the placeholders when you map a trigger to a template. Whenever you create, edit or get approval for a template in WhatsApp Manager, press Refresh so the copy catches up. The test message reads from that copy, so a brand new hello_world replacement will not be found until you refresh.

A ten-minute pre-flight

  1. Connect with the four values. Read any warnings and clear them before continuing; they do not go away on their own.
  2. Confirm the display name and phone number shown match the number you meant to connect. Businesses with several numbers get this wrong more often than they expect.
  3. Send a test to your own phone. Wait for delivered. If it does not arrive at all, the problem is sending; if it arrives but the row stays at sent, the problem is the webhook.
  4. Open the Messages page and find the test row. This is the same place you will look when a customer says they got nothing.
  5. Refresh templates, map your first trigger to an approved template, and place a test order in your store to see the real thing go out.

None of this takes long, and all of it is cheaper than finding out on a Friday evening. Beacon Messenger puts the checks on one page because the four values, the templates and the webhook are three different things that can each be wrong on their own, and a single test message exercises all of them in order. Start at the homepage if you have not installed it yet.

Frequently asked questions

Why does my WhatsApp test message use the hello_world template?

Cloud API requires the first message to a number to be an approved template, and the test cannot invent order data for a template with variables. hello_world is the sample template Meta creates on every WhatsApp Business Account and has no placeholders, so it is the safe default. If you have deleted it, any approved template with zero variables is used instead.

Does a test message count toward my monthly message limit?

Yes. It goes through the same send path as a real notification, is logged in the Messages page with the trigger test, and increments the month's counter. If the allowance is already used up, the test is refused with a message saying so rather than sent.

My test says sent but never changes to delivered. Is the message lost?

Probably not. If it arrived on your phone, the message is fine and the delivery statuses are not reaching the app, which means the webhook subscription did not take. Check the callback URL and verify token shown on the WhatsApp account page against your Meta app's webhook configuration, and subscribe the app to the WhatsApp Business Account.

What does the warning about templates not loading mean after connecting?

The token worked for the phone number but could not list templates on the WhatsApp Business Account, usually a permissions gap on the token. You are connected, but no templates are available to map until you fix the token's permissions and press Refresh templates.

More guides