Connecting a number to the official WhatsApp API is a short sequence of screens — yet it’s where most companies get stuck. It’s almost never the platform: it’s a number that still has active WhatsApp, a duplicate business account created, a display name rejected by Meta, or a person without admin permission trying to authorize. This guide is the right order: what to prepare beforehand, what to decide about the number, what to do in the first 48 hours, and what makes the channel grow instead of being blocked.
In this article
- What changes when the number moves to the API
- What to have before starting
- New number or the company’s number?
- Step-by-step connection process
- The first 48 hours
- Limits, quality, and warming up
- Opt-in: the part that’s not bureaucracy
- Templates: what gets approved and what doesn’t
- Cost, with no surprises
- Coexistence: when it makes sense
- The seven errors that block the connection
- When it’s worth it — and when it’s not
- Frequently asked questions
What really changes when the number moves to the API
Before any step-by-step, it’s worth understanding what you’re contracting, because almost every connection error stems from a wrong expectation here.
- The number no longer lives on a device. It moves to a Meta account in the company’s name. There’s no phone that needs to stay on, no six-digit code in daily use, and no "connected device."
- Access is by person. Each agent logs in with their own user, and removing someone means revoking access, not recovering a phone.
- Who initiates the conversation must follow rules. Outside the 24-hour window, you can only message the customer using an approved message template. Inside the window, free text is allowed.
- There is a cost per conversation. Meta charges per conversation started, with different prices depending on the category.
- The regular WhatsApp Business app stops being the place for service — or continues, if you choose coexistence, which is a separate path explained later.
The honest summary: the official API is not an improved version of the app. It’s something else. It solves team, history, automation, volume, and security issues, and in exchange charges for process discipline and cost per conversation. A company with one agent and twenty messages per day rarely needs this.
What you need to have before starting
Half of the connections that get stuck do so because something on this list is missing. Gather everything before opening the connection screen:
- A phone number you control and that can receive SMS or voice call for verification. It can be mobile or landline.
- A Facebook Business account (Business Manager) for the company. If it doesn’t exist, it’s created during the process — but having it beforehand avoids confusion.
- A personal Facebook profile with admin access to that business account. Meta requires a logged-in individual to authorize.
- The company’s data: legal name, CNPJ, address, and website. These are used in registration and later in verification.
- A decision about the number: will you use a new number or the number the company already uses on WhatsApp?
That last question is the most important of all, and it’s the next topic.
New number or the number the company already uses?
There are three scenarios, each with a different consequence:
- New number, no WhatsApp. The simplest and risk-free path. However, the number starts from zero: no one has it saved, and it will need warming up before any volume.
- The company’s current number, migrating fully. This path preserves relationships — customers already have this contact saved. But it requires deleting the WhatsApp Business account on that number before connecting, and the chat history from the app does not transfer.
- The current number, in coexistence. Mode where the number works simultaneously on the app and the API. It’s the most comfortable path for those afraid of losing mobile service, and it brings part of the history and recent contacts to the platform.
The most costly mistake at this stage: connecting a new number and blasting messages to the base the next day. A number without history, with high volume, and no opt-in is exactly what Meta’s systems block. If the decision is a new number, warming up is not optional.
Step-by-step connection process
In practice, connecting via the platform is a short flow. What usually takes time is not the click, but the documentation.
- 1. Open the connection screen and choose the path. You choose between connecting in the cloud (official API) or via QR Code, and understand the risk of each before deciding.
- 2. Log in with Facebook. A Meta pop-up opens. This is the only place where data is entered — no serious provider asks for your Facebook password outside this pop-up.
- 3. Select or create the business account. If the company already has a Business Manager, choose the existing one. Creating a second one by mistake causes half of the permission problems later.
- 4. Create or select the WhatsApp account (WABA) within that portfolio.
- 5. Enter the number and display name. The name is what the customer sees. It undergoes review and must relate to the company — generic names like "Support" are usually rejected.
- 6. Verify the number via code received by SMS or call.
- 7. Accept permissions and finish. The number appears connected on the platform.
From the click to here, with everything ready, it takes just minutes. What comes next defines whether the channel will work.
What to do in the first 48 hours
A connected number is not a ready channel. The sequence that avoids the most common problems:
- Complete the business profile: photo, description, address, website, service hours. An empty profile undermines trust and hinders verification.
- Start company verification in Business Manager. It’s not mandatory to start, but it unlocks higher limits and the badge later.
- Submit the first message templates. They take time to be reviewed, and without approved templates you can’t start conversations.
- Promote the number. Website, social media, email signature, Google My Business. Incoming conversations are the best quality signal there is.
- Set up the team and distribution rules before volume arrives, not after.
Limits, quality, and starting slow
Every new number starts with a low daily limit for conversations started, which increases as it sends quality messages and receives replies. This step can’t be bought or rushed — it’s a consequence of behavior.
What raises the number’s level: replied conversations, few complaints, few blocks, and gradually increasing volume. What lowers it: blasting to purchased lists, unexpected messages to customers, content that looks like advertising, and identical text sent to thousands at once.
The correct approach is to treat the first week as deliberate warming up: few sends, to people who have already interacted with the company, with content that invites a reply. This is worth more than any configuration.
Keep reading for free
Fill out once and unlock this and all other blog articles. We charge nothing — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
Opt-in: the part that’s not bureaucracy
The rule is simple to say and easy to ignore: the company should only start conversations with those who authorized receiving messages from that number. It’s not just Meta’s policy — it’s what separates a growing channel from a number that gets reported until it dies.
Opt-in methods that work and are recorded:
- Acceptance checkbox on the website form, with text clearly stating the company will send WhatsApp messages.
- The customer initiating the conversation themselves — button on the site, link, QR code, ad that opens WhatsApp. This is the best opt-in there is.
- Consent at purchase or registration, with date and source recorded.
- Confirmation in the first message, with opt-out option, for older bases.
And what doesn’t count: purchased lists, other channel bases without notice, numbers collected at events without WhatsApp mention, and spreadsheets inherited from a departed salesperson.
Message templates: what gets approved and what doesn’t
Outside the 24-hour window, every conversation starts with an approved template. Understanding the review logic saves weeks:
- Correct category. Utility is for something the customer expects, linked to a transaction or update. Marketing is for promotion and news. Authentication is for access codes. Sending marketing disguised as utility is the number one reason for rejection and, worse, reclassification later.
- Variables with examples. Every variable field needs a real example filled in, or it’s rejected.
- No vague text. Messages that don’t clearly state who is speaking and why are rejected.
- No promises or excessive appeals. ALL CAPS, excessive emoji, and artificial urgency count against approval.
- Buttons help. An unsubscribe button in marketing messages reduces complaints, which really protects the number.
Start with three: a confirmation, a status update, and a conversation follow-up. With these three, almost any operation gets moving.
Cost, with no surprises
Meta charges per conversation started, with different prices by category and country. Conversations opened by the customer and replied to within the window are the cheapest — often free. Those started by the company with marketing templates are the most expensive.
The practical consequence is good for those who do things right: the more the customer initiates conversations, the lower the channel cost. Investing in a button on the site, a link in ads, and printed QR codes is not just marketing — it’s direct operational cost reduction.
An example to give scale. A company that sends 3,000 follow-up messages per month, all started by it in the marketing category, pays one amount; the same company that manages to get half of those contacts to start the conversation pays significantly less and also has a higher response rate, because whoever wrote first is interested. The cheap channel and the effective channel here are the same channel.
Coexistence: when it makes sense
Coexistence allows the number to keep working on the WhatsApp Business app and simultaneously be on the platform. It’s recommended when:
- The team fears losing mobile service during the transition.
- There is a large history on the device the company doesn’t want to abandon all at once.
- The owner answers personally and wants to keep replying on the phone while the team uses the platform.
And when it doesn’t make sense: operations with multiple people, high volume, or automation needs from day one. In these cases, keeping the phone involved only maintains the mess that motivated the change.
The seven errors that block the connection
- Number still in use on WhatsApp without being deleted first, when coexistence was not chosen.
- Creating a new Business Manager when the company already had one, splitting portfolios and permissions.
- Generic or unrelated display name, which gets rejected.
- Person without admin permission trying to authorize. The pop-up opens but doesn’t complete.
- Number that doesn’t receive SMS or calls — VoIP and extensions often fail verification.
- Pop-up blocker preventing the Meta window from opening. It’s common and blocks many people.
- Financial or verification pending on the business account, which blocks sending even if connected.
When the official API is worth it — and when it’s not
It’s worth it when at least one of these exists: more than one person answering on the same number; need for history that isn’t lost when someone leaves; first response automation and qualification; sending confirmations, billing, or notices in volume; integration with CRM, system, or store; and requirement for control over what’s said on behalf of the brand.
It’s not worth it when the company has one agent, few conversations per day, and no plan to grow the channel. In that case, the app suffices, and the cost per conversation doesn’t pay off.
The practical deciding question isn’t about technology: if the person answering today leaves tomorrow, does the company lose the conversations? If yes, the number is in the wrong place — and that’s why most companies end up migrating, even those without volume problems.
Frequently asked questions
How long does it take to connect a number to the official WhatsApp API?
The connection itself takes a few minutes when everything is ready: business account in Business Manager, a person with admin access, the number that receives SMS or calls, company data, and chosen display name. What usually extends the process isn’t the click but what surrounds it. The display name undergoes review and may be rejected if generic or unrelated to the company. The first message templates need to be submitted and reviewed before you can start conversations, and that timing isn’t up to you. Company verification in Business Manager, which unlocks higher limits, involves documentation and has its own timeline. And if you choose to migrate the company’s existing number, there’s also the step of deleting the app account before connecting. In practice, count minutes to connect and a few days for the channel to be fully operational.
Can I use the same number the company already uses on WhatsApp Business?
Yes, and there are two paths with different consequences. The first is full migration: you delete the WhatsApp Business app account on that number and connect the number to the API. This preserves relationships since customers have that contact saved, but the chat history on the device does not transfer to the platform. The second path is coexistence, where the number continues working on the app and simultaneously exists on the platform, bringing part of the contacts and recent conversations. Coexistence is comfortable for those afraid of losing mobile service during transition, or when the owner wants to keep replying on the device while the team uses the system. It makes less sense in operations with multiple people, high volume, or automation needs from day one, because keeping the phone involved maintains the very mess that motivated the change.
Why does the number connection fail or get stuck?
Seven causes account for the vast majority of cases. The number still has active WhatsApp and wasn’t deleted first, when coexistence wasn’t chosen. A new Business Manager was created instead of using the company’s existing one, splitting permissions between two portfolios. The display name is generic, like Support or Sales, and gets rejected for not relating to the company. The person trying to authorize lacks admin access to the business account, so the pop-up opens but doesn’t complete. The number doesn’t receive SMS or voice calls, common with VoIP and phone system extensions. The browser’s pop-up blocker prevents the Meta window from opening, a common and trivial cause. Finally, there’s financial or verification pending on the business account, where the number connects but sending remains blocked.
Connection is just the start. The channel is what comes next.
VeyloCRM connects your number to the official WhatsApp API with the account in your company’s name, organizes team and history, manages message templates, and monitors number quality and limits so you don’t discover problems through blocks.