Embedded signup, Coexistence, migrations and limits.
8 answers
Two ways to connect: Cloud API or Coexistence
One replaces the WhatsApp Business app, the other runs alongside it.
Embedded signup registers your number on the WhatsApp Cloud API. The number leaves the WhatsApp Business app and lives entirely in VedLink, best for a new or dedicated business number.
Coexistence keeps the number in the WhatsApp Business app on the phone your staff already use, while VedLink handles campaigns, automation and the shared inbox. Recent chat history syncs across on connect.
Both routes go through Meta's own signup window. VedLink never asks for your WhatsApp password or OTP.
Which number should you use?
Use the number your customers already message, if you can free it.
Recognition beats novelty: a number already printed on your invoices and shopfront will out-perform a fresh one. Coexistence exists precisely so you do not have to give it up.
A brand new number works too, but expect a lower starting messaging limit and a slower warm-up.
Meta's own window handles the number, the OTP and the permissions.
The whole flow happens in a Meta popup launched from the app.
1Go to Settings → WhatsApp and start the connection.
2Sign in to the Meta account that owns (or will own) your business portfolio.
3Select or create the WhatsApp Business Account and add your number.
4Verify the OTP sent by SMS or voice call.
5Accept the permissions and return to VedLink, the number appears as connected.
If the popup closes early, nothing is lost. Start again and Meta resumes where you stopped.
Keep using the WhatsApp Business app (Coexistence)
Staff carry on replying from the phone; VedLink sees the same conversations.
After connecting, messages sent from the phone appear in the VedLink inbox and vice versa, so nobody has to change how they work overnight.
One caveat worth knowing: Meta sends no signal for "the business read this chat on the phone". A reply from the phone clears the unread badge in VedLink; opening the chat without replying does not.
Why customers see only my number, not my business name
Meta does not review display names for Coexistence numbers.
On a Coexistence connection, Meta leaves the display name unapproved, so recipients who have not saved you see the raw number. This is not a VedLink setting and no template or profile change fixes it.
The unlock is Meta Verified for your business. Once verified, submit the display name and it starts showing in chats.
Check the current state of your display name any time from the WhatsApp section of Account settings.
The post-connect checklist
Connecting is not the same as being ready to send.
Four things decide whether your first campaign actually goes out. VedLink verifies each one and shows you what is still missing.
1A payment method added to your WhatsApp Business Account on Meta, without it, Meta stops conversations after the free allowance.
2A display name submitted and approved.
3Your current messaging limit, so you know how many people you can reach in 24 hours.
4Business verification started, if you want limits above the entry tier.
A number already on the API can be migrated without losing it.
Ask your current provider to release the number, then run embedded signup in VedLink against the same WhatsApp Business Account. Your templates can be pulled in from Meta afterwards so you do not rewrite them.
Plan a quiet window for the switch: for a few minutes during migration, neither system is receiving.
Meta caps how many unique people you can start conversations with in 24 hours.
New numbers start low. The limit rises as you send consistently with good quality and complete business verification, moving through 1,000, 10,000, 100,000 and unlimited.
Quality is the lever, not volume. Blocks and "report" taps pull your rating down and can drop your limit back a tier.