WhatsApp Business API requirements: what to have ready first
What you need, as a list
The requirements for connecting the WhatsApp Business API split in two: the ones Meta sets and the ones your operation sets.
| On Meta's side | On your business's side |
|---|---|
| A number that meets its conditions | The documents you will answer from |
| A Meta business account | A decision on what answers itself and what does not |
| The number verified | The team with access to the panel |
None of them is hard. What delays a rollout is finding out about one of them late.
What Meta asks of the phone number
It is written in its documentation and worth checking before choosing the number.
Meta requires the number to be yours, to have a country and area code (short codes do not work) and to be able to receive calls or SMS, because that is how it gets verified.
That last point rules out more numbers than people expect: the office landline nobody picks up, or the virtual number that does not receive messages, will not be able to complete verification.
Can I use the number I already use?
It depends which app it is on today, and the difference matters.
- If the number is on the WhatsApp Business app, Meta documents how to migrate an existing number to a business account.
- If the number is on regular WhatsApp, that account has to be deleted first before it can be registered.
- If the number was blocked by WhatsApp, that has to be resolved through the appeal process before registering it.
The practical decision: using your usual number keeps your contacts and your identity, and comes with an awkward moment during migration. A new number avoids that moment and leaves you starting from zero.
What you need on your business's side
Almost nobody arrives prepared here, and it is what changes the result most.
- The documents you will answer from. Price list, policies, timelines, requirements. The more specific, the better it answers.
- A decision on what is off limits. The topics that go straight to a person.
- Who on the team gets into the panel. And who takes care of the handed-off conversations.
The documents are the one requirement you can start today without depending on anybody. And the one that gets postponed most.
The order that keeps you from stalling
Number verification runs in parallel with everything else. Use that.
- Get into the panel and do the onboarding. That starts the trial period.
- Configure the service: instructions, tone, what it does and what it does not.
- Load its context: your documents, your catalogue if you have one.
- Test it in the sandbox, with real contacts from your address book.
- Connect the channel and switch it on, once the number is verified.
If you start verification on the same day you start configuring, by the time the number is enabled you already have a tested service.
Another option: the inbox first
Some businesses prefer to flip the order, and it works.
You connect the channel and work in the inbox with automated replies switched off. The team gets used to handling everything in one place, with conversations distributed, and automation gets switched on later.
It is slower on paper and faster in practice, because the team does not have to learn two things at once.
How long it takes
It depends on a single question: whether what you need already exists.
If it is functionality already on the platform, the trial stage starts immediately. If it needs custom development, the typical timeline is around two weeks.
What is almost never the bottleneck is the technical part. It is usually gathering the documents.
What you do not need
Worth saying, because it stops a lot of people for no reason.
You do not need to change your management system, migrate your contacts anywhere, or have somebody technical on the team. You also do not need everything defined: you can start by answering five questions and expand later.
Key takeaways
- Meta requires a number that is yours, with country and area code, and able to receive calls or SMS.
- A number you already use on the WhatsApp Business app can be migrated; one on regular WhatsApp has to be deleted first.
- On your business's side, what weighs most are the documents you will answer from.
- The order that works: onboarding, configure, load context, test in the sandbox, and only then connect.
- Number verification runs in parallel, so it does not have to block you.
- There is a variant that works well: connect the channel and use the inbox with automation off.
Frequently asked questions
- Can I use my current WhatsApp Business number?
- Yes. Meta documents the process for migrating an existing number to a business account. If the number is on regular WhatsApp instead of the Business app, that account has to be deleted first.
- Does a landline work?
- It can work if it meets Meta's requirements: being yours, having a country and area code, and being able to receive a call or an SMS for verification. A landline nobody answers will not be able to verify.
- Which documents are worth having ready?
- Your current price list, shipping policies and timelines, requirements and terms, and the notes for the questions you get asked most. The first two alone take care of a good share of the day's queries.
- Do I need somebody technical on my team?
- Not for the standard configuration. It does help if you are going to connect your own management system over an API, even though the configuration is done from the panel.
- Can I start without switching automated replies on?
- Yes, and it is a common way to start. The channel gets connected, the team works in the inbox, and automation gets switched on when they are ready.
Related posts
Get twice the output from your team without asking more of them
It answers WhatsApp, Instagram and web. It learns your business, takes the orders, and hands off to a person when it matters. You see every action noted in the chat.
Free Pro trial. No credit card required.