Skip to main content
RoutMe
All posts
WhatsApp5 min read

WhatsApp without Twilio: how the Cloud API connection works

You can run WhatsApp support without your own Twilio account. Learn how Embedded Signup connects the Cloud API directly, and what a BSP adds that you may not need.

SM

Sushma Madan

WhatsApp platform

You can run WhatsApp customer support without your own Twilio account. RoutMe connects your number straight to Meta's WhatsApp Cloud API using Embedded Signup, a login flow run by Meta. You pick the number from your own WhatsApp Business Account, RoutMe registers it, and messages arrive in RoutMe without passing through a provider account that you manage.

A note on wording, because it matters for accuracy. RoutMe itself uses Twilio for some telephony and number features on our side. The claim here is narrower and more useful: you do not need a Twilio account of your own, or a business solution provider, to run WhatsApp and website chat with RoutMe.

What the Cloud API is

The WhatsApp Business Platform is Meta's offering for businesses that want automation, several agents and integration with their own systems. Its Cloud API is the hosted interface to it, so a business or a platform acting on its behalf can send and receive messages over HTTP. Meta publishes the documentation at developers.facebook.com. Anything that talks to your WhatsApp number at scale is, one way or another, using it.

The question is therefore not whether you use the Cloud API. It is who stands between you and it. See the glossary entries for Cloud API and BSP if the terms are new.

How the direct connection works in RoutMe

  1. 1You create an app in RoutMe, which owns your numbers, templates, keys and webhooks.
  2. 2You log in with the Facebook account that administers the business that owns the WhatsApp Business Account.
  3. 3Meta shows its own Embedded Signup pop-up. You choose the number.
  4. 4RoutMe exchanges Meta's authorisation code for an access token, subscribes the app to your WhatsApp Business Account so delivery events reach it, registers the number for the Cloud API with a two-step verification PIN, and reads the number's details back from Meta.
  5. 5The number shows as connected, with its quality rating and messaging tier read from Meta.

If the person with the Facebook login is not the person setting up RoutMe, the dashboard can create an onboarding link that takes them straight to the same pop-up. The link works for seven days. If you already have the account ID, the phone number ID and an access token, there is a connect existing option that asks Meta to confirm them before saving.

What a BSP adds

A business solution provider is a company that has been approved by Meta to help businesses use the platform. Providers in this role typically offer some mix of the following.

  • Onboarding help and account verification support.
  • A console for templates, numbers and message logs.
  • An API that wraps Meta's own, sometimes with provider-specific behaviour and limits.
  • Billing that bundles Meta's charges with their own fees.
  • Support if something goes wrong with the account.

Those are real services, and some teams genuinely want them. Twilio, for example, is a communications API provider that offers WhatsApp messaging through its APIs and describes a WhatsApp sender as a phone number associated with a WhatsApp Business Account. If your engineers already build on it, staying is a legitimate choice. What changes with RoutMe is that the console, the API and the agent are one product, so there is no second layer to learn.

What you give up and what you keep

Going direct does not remove Meta's rules. The 24-hour customer service window, template approval, opt-in and quality ratings all apply whoever carries the messages. RoutMe enforces them as guardrails: a free-form message outside the window fails visibly and tells you a template is needed, and templates carry the same pending, approved, rejected and paused states that Meta reports.

What to check before you switch

  • Whether the number is currently registered with another provider, and what that provider needs from you to release it.
  • Which templates exist and which are approved, so you can import rather than recreate them.
  • Whether anyone depends on provider-specific webhooks or message logs for reporting.
  • Who in your company can log in as an admin of the business that owns the account.
  • How your current setup handles opt-outs, so the same rule holds after the move.

For the wider comparison of options, read Twilio WhatsApp alternatives. For the practical rebuild of the logic around the number, see moving a support workflow from n8n, and for compliance see WhatsApp compliance and security.

To see the connection in a live account, book a demo. For the full list of migration routes, go to Move to RoutMe.

A short word on cost and ownership

Whichever route you take, Meta bills the message charges, and they depend on the category of message and the destination market, not on the provider you chose. What a provider adds on top varies, and we do not quote anyone's prices. When you compare, separate the two lines: what Meta charges for delivery, and what a vendor charges for everything around it. Then ask what you would stop paying for if the vendor layer were gone, and what you would need to build or buy instead.

On ownership, the question to settle early is who administers the business that owns the WhatsApp Business Account. If it was created by a contractor or by a provider on your behalf, make sure a person at your company is listed as an admin before you plan any move. That one check prevents most delays.

Common questions from teams moving over

People often ask whether switching will interrupt service. It does not have to, if the old number keeps serving customers while you connect and test a different one, and you move the live number only when the new setup is ready. They also ask about message history. Conversations that took place in a provider's console stay there, so export what you need for records before you leave.

What you will see after connecting

The number appears in the dashboard with a status of connected, pending, unverified or disconnected. Pending means RoutMe saved it but one registration step did not finish, and the response lists which, so you can reconnect or run a sync. Each number also reports Meta's quality rating, its messaging tier, which sets how many new customers you may start conversations with in a rolling day, and the state of its display name review. These come from Meta, so they match what you would see in WhatsApp Manager. A sync reads every number on your account, refreshes those fields, adds new numbers and flags any that have gone.

  • Migration
  • Twilio
  • WhatsApp Cloud API
  • BSP
SM

Sushma Madan

WhatsApp platform

Writes about templates, pricing, and getting things approved on the WhatsApp Business Platform.

Frequently asked questions

Does RoutMe use Twilio at all?

RoutMe itself uses Twilio for some number features on our side. What that means for you is that you do not need your own Twilio account, or any other provider account, to run WhatsApp and website chat.

Who owns the WhatsApp Business Account when I connect directly?

You do. It belongs to the business that logs in through Embedded Signup, which is a Meta pop-up. RoutMe never sees your Facebook password.

Can I move a number I already use?

Yes, there is a guided path for migrating a number that is live elsewhere, and you can import templates that are already approved on your WhatsApp Business Account.

Do I still pay Meta?

Yes. Meta's per-message charges apply to any WhatsApp setup. See how WhatsApp pricing works and the pricing page.

See it on your own data

Connect a system, drop an agent node into a flow, and watch it answer from what is actually true in your systems right now.