MoraselWhatsApp API onboarding, step by step
Between signing up and the first delivered message sit five gates that belong to Meta, not to you. This page lists them in order, what each one needs, and what Morasel does at each.
Why teams stall between sign-up and first message
Most WhatsApp API projects do not fail; they stall. The number is still tied to the WhatsApp app on someone's phone, Meta Business verification is waiting on a document nobody was told to upload, the first template was rejected for a wording rule, or the wallet is empty on launch day. None of these are hard. All of them are invisible until they block you.
- A number that is still registered to the WhatsApp Business app cannot be used on the API until it is released.
- Meta Business verification asks for company documents that match the business name exactly.
- The first outbound message needs an approved template; approval is Meta's, not ours.
- Sending costs are prepaid; a live number with an empty wallet delivers nothing.
What Morasel records for your channel
One WhatsApp connection record per number, with every gate and its state, so the person running onboarding sees where the channel is without asking.
- Phone number
- The number being connected, its display name, and whether it is new or being moved from the WhatsApp app.
- Meta Business verification
- Not started, submitted, verified, or action required — with the reason Meta returned.
- Display-name review
- Meta's decision on the name customers will see.
- Templates
- Each template with its category, language, Meta status and the time the status was last synced.
- Wallet
- Prepaid balance, currency, and the last top-up.
- Channel status
- Connected and sending, connected but blocked (and by which gate), or disconnected.
The five gates, in order
Each gate is a real state in your workspace. You cannot skip one, and you do not have to guess which one you are on.
Sign up and choose the number
Create your workspace (14-day trial, no card). Decide whether to connect a new number or keep the one your customers already save; if it is on the WhatsApp Business app, release it first — the keep-your-number guide covers this.
Meta Embedded Signup
From the workspace, open Meta's sign-in flow. Morasel's team joins the thread and stays on it. You confirm the business, the number, and grant Morasel the permissions Meta asks for.
Business verification and display name
Upload the company document Meta asks for; the name on it must match your Meta Business name. Display-name review runs alongside. Both show their state on the connection record.
First template approved
Submit your first template from the workspace — a reminder, an order update, a reply — in the customer's language. Meta approves or rejects; the status syncs to Morasel every 15 minutes and the rejection reason is shown.
Fund the wallet and go live
Top up the prepaid wallet by card or bank transfer. When verification, one approved template and a positive balance are all in place, the channel flips to sending and the first message goes out.
What the customer sees on day one
Your business name, verified, on the number they already have — and a message that came from an approved template.
What your team sees while it happens
Onboarding is a checklist on the connection record, not a support ticket.
- Each gate with its state and who is waiting on whom — you, Meta, or Morasel.
- The Meta rejection reason, verbatim, next to the template or document it applies to.
- A shared thread with Morasel's team on the same record, so nothing is repeated over email.
- Wallet balance and the rate card for your country before the first message is sent.
- The moment the channel goes live, with the timestamp, in the audit log.
Permissions and review points
Two people usually run onboarding: an owner who signs with Meta and a manager who writes templates. Morasel keeps those apart.
- Only an owner can start Meta Embedded Signup or disconnect a number.
- Template submission can be delegated to a manager; approval remains Meta's.
- Wallet top-ups are recorded with who paid, how, and when.
- Every state change on the connection record is in the audit log.
What Morasel does not do
Morasel does not verify your business, approve your templates, or set the message rates — Meta does all three. Morasel makes each gate visible, keeps its team on the thread, and turns the channel on the moment Meta's decisions allow it. We do not issue instant API keys, and we do not call ourselves a Business Solution Provider unless that is formally the case.
Start the connection today
Create your workspace, pick the number, and let Morasel's team sit on the thread for every Meta gate.
Onboarding questions
How long does WhatsApp API onboarding take?
Sign-up and Embedded Signup take minutes. Meta Business verification usually takes a few business days and depends on your documents matching your business name. Template approval is often same-day. Most teams are sending inside the trial.
Can I keep the number my customers already have?
Yes. Release it from the WhatsApp Business app first, then connect it in Morasel. Chat history on the phone is not migrated; the number and its customers are.
Do I get an API key immediately after sign-up?
No. Sending needs Meta's verification and an approved template first. What you get immediately is a workspace with the connection record that shows exactly which gate is open.
Is Morasel an official WhatsApp Business Solution Provider?
Morasel connects your number through Meta's Embedded Signup for the WhatsApp Business Platform. We do not claim a partner title we do not formally hold; the Meta relationship is stated plainly on our WhatsApp Business page.
What if Meta rejects my first template?
The rejection reason appears on the template within 15 minutes of Meta's decision. Edit and resubmit from the same screen; there is no limit on resubmissions.
Do I need a card to start?
No. The 14-day trial has no card requirement. You fund the wallet by card or bank transfer when you are ready to send.