Your Meta Business Portfolio is already verified and you are using your own existing phone number — so you can skip straight to the WhatsApp setup. This guide walks you through creating your WhatsApp Business Account and connecting Enchat as your messaging partner. Total time: around 20 minutes.
You already have a verified Meta Business Portfolio, which is the hardest part. The remaining work is: creating a WhatsApp Business Account inside your portfolio, attaching a phone number to it, and granting Enchat permission to send and receive messages on that number.
A 60-second sanity check before we move on.
In Meta Business Suite, go to Settings → Security Centre. You should see Business Verification: Verified with a green tick. If you see Verification Pending or Not Verified, switch to Guide A.
↗ Meta Security CentreRoughly 20 minutes. Follow these steps in order using your own phone number.
Inside Meta Business Suite, open Settings → Business assets. In the left sidebar, find WhatsApp accounts. If you do not yet have a WhatsApp Business Account (WABA), click Add to create one.
↗ Meta Business Suite SettingsClick Create a WhatsApp account. Give the account the legal name of your business. This is the name that will appear to your customers when they message you on WhatsApp — get it right first time, it is painful to change later.
Every WhatsApp Business Account needs one phone number to route messages through. This becomes the number your customers message on WhatsApp. Enter your number in the WhatsApp account settings. It must not already be active on a personal WhatsApp or another WhatsApp Business account — if it is, deactivate it there first or use a different number. A landline or mobile both work.
Meta will send a 6-digit code to your number, either by SMS or voice call. Enter the code in the Meta verification prompt.
In the WhatsApp account settings, open the Partners or People & partners tab. Click Add partner → Add partner using Business ID and enter our Business ID: 957477320190058.
Once Enchat's Business ID has been added as a partner, a confirmation message will appear in Meta Business Suite. You will also receive an email confirmation from Meta. Forward this email to your Enchat onboarding manager — we use it to verify that the partner link is live on our side.
That's it from your side. Our onboarding team will now:
From the moment Enchat is added as a partner on your WABA, the onboarding clock starts. Here's the standard timeline — we'll communicate clearly at each stage.
You complete the steps in this guide and we receive the partner confirmation from Meta.
We set up your tenant in the Enchat platform, configure your WhatsApp number, and link your voice agent. You receive a login for your unified inbox.
We draft your first WhatsApp message templates (appointment confirmations, reminders, etc.) and submit them to Meta for approval. We train the AI on your FAQs, SOPs, tone of voice, and escalation preferences.
30-minute call to walk you through your unified inbox, test the AI live, and flip the switch. Your WhatsApp and voice are live from this call.
If any step above doesn't behave as described, check here first. If you're still stuck, email onboarding@enchat.co.uk and we'll jump on a call within the hour during UK business hours.
Meta's SMS delivery can be patchy, particularly for UK landlines. Try the voice call option instead. If that also fails, the number may already be flagged — contact us and we'll investigate.
Double-check that you've entered our Business ID exactly — it's a 15-digit number, no spaces, no dashes: 957477320190058. If it still doesn't work, make sure you're adding it under WhatsApp accounts → Partners, not under Apps or System users (those are for different integrations).
Meta's template rules are strict — no promotional language in utility templates, no ALL CAPS, no vague variables without context. Don't worry about this: our team handles template submissions on your behalf. If you have specific wording you need approved, send it to us and we'll reformat it to Meta's guidelines.
The most common cause is a name mismatch — the name on your Meta portfolio does not match the name on your uploaded document. Check both exactly. Otherwise Meta will state the reason by email; forward it to us and we'll tell you the fix.