Put WhatsApp in your product, under your own name
Your customers connect their own WhatsApp Business number through a hosted page that carries your brand. You get one partner API for messaging, templates, and webhooks — and they stay the owner of their account, billed by Meta directly.
- 1 API call
- to start a customer’s onboarding
- Their WABA
- owned and billed by your customer
- 0% markup
- added to Meta’s conversation rates
- Unlimited
- customer numbers on one workspace
Three calls, and your customer is live on their own number.
Adding WhatsApp usually costs a quarter — or your margin
Meta’s onboarding is the hard part
Embedded Signup, phone registration, two-step PINs, re-verification, webhook subscriptions. Weeks of work before your first message sends — and every edge case lands in your support queue.
Reselling makes you the biller
Most providers put their line of credit in the middle, so you inherit invoicing, margin management, and the awkward conversation when a customer disputes a conversation charge.
Your brand disappears
Send customers to a third-party dashboard to connect a number and you have handed the relationship — and the branding — to someone else at the worst possible moment.
Three steps from signup to first message
Create a link
Call the partner API with your own reference for the customer and a URL to send them back to. You get a one-time hosted link.
They connect
Your customer opens a neutral page showing your name, signs in with Facebook, picks their number, and enters their PIN. Guided the whole way.
You get a channel
They land back on your URL with your reference and a channel id. Send, receive, and automate through the same API you already use.
Everything the white-label model runs on
Hosted onboarding
A neutral, mobile-ready page that carries your name — not ours. Resumes safely if a customer closes the tab, and recovers from forgotten PINs.
One API, every customer
Each connected number is just another channel id. The same messaging endpoints serve one customer or a thousand.
Template management
Create and edit WhatsApp templates programmatically, upload header media from a URL, and track Meta approval without anyone opening a dashboard.
Webhooks for everything
Signed, retried delivery for inbound messages, delivery receipts, template approvals, and channel connections — so your product stays in sync.
Built for AI agents
The same capabilities are exposed as MCP tools, so assistants can create links, draft templates, and check status inside your workflows.
Clean economics
Your customer pays Meta directly at Meta’s rates. You charge for your product, not for someone else’s messaging margin.
A page that looks like it belongs to you
What they do
- Open a link from inside your product
- Sign in with Facebook and share their WhatsApp account
- Pick the phone number they want to connect
- Enter their six-digit two-step PIN
- Land back in your product, connected
What they never do
- Create a Lodgestory login
- Learn a second dashboard
- Read Meta’s developer documentation
- Wire up webhooks or register a phone number
- Pay anyone but Meta for their conversations
What changes for your team
- Launch WhatsApp as a feature in days rather than a quarter
- Keep your brand in front of the customer during onboarding
- Stay out of the middle on conversation billing and disputes
- Onboard customers without a human touching a dashboard
- Match every connected number back to your own tenant record
- Support the flow from your own product with live link status
Questions, answered
Who owns the WhatsApp Business Account?
Your customer does. During signup they create or connect their own Meta Business account and WhatsApp Business Account, and they keep full access to it in WhatsApp Manager. Nothing is held in escrow by you or by Lodgestory, so there is no hostage problem if they ever leave.
Who pays Meta for the messages?
Your customer, directly. They add their own payment method during onboarding and Meta charges them per conversation at Meta’s published rates for their country and category. Lodgestory never rebills or marks up Meta’s conversation charges, so you are not forced to become a payments intermediary.
Does my customer ever see Lodgestory?
Not during onboarding. The hosted page is neutral and displays the partner name you pass when you create the link. The one name they do see is Meta’s, because Facebook sign-in is a required part of the official WhatsApp signup and cannot be white-labelled by anyone.
What do I have to build?
One API call to create an onboarding link, a redirect handler, and whatever you want your product to do with the messages. Everything underneath — the Meta signup flow, phone registration, two-step PIN entry, verification recovery, and webhook wiring — is handled for you.
How fast can I onboard customers?
Onboarding is instant for each customer, but Meta caps how many new businesses can complete signup per rolling week, and that cap rises once your app clears Meta’s business verification and access review. Talk to us before a bulk migration so the rollout is sized correctly.
What happens when a customer gets stuck?
The hosted flow handles the cases that normally derail WhatsApp onboarding: a forgotten two-step PIN, a number that needs re-verification by SMS or voice call, a closed browser tab mid-flow. Each link also reports its live status through the API, so your support team can see exactly where a customer stopped.
Start building
The partner API reference has the full onboarding, messaging, and template surface — with copy-paste examples for every call.