Webivio sends WhatsApp notifications to participants and receives messages in an inbox in the panel. It works through the Meta Cloud API on your own WhatsApp Business account (WABA) - participants see your company's name.
Plan: Pro (per the current pricing page). Webivio does not provide a phone number - you connect your own WABA.
What you can send (per webinar)
- registration confirmation,
- a reminder 24h before,
- a reminder right before start,
- a follow-up after the webinar (everyone / attended / didn't attend).
When WhatsApp is enabled on a webinar, a phone number becomes required at registration.
1. Connect your WhatsApp account
- Choose WhatsApp from the menu.
- Connection tab - start the connection (Embedded Signup in the panel).
- Complete the Meta steps. Templates must have APPROVED status in Meta before production sending can go out - typically anywhere from a few minutes to a few hours.
- Optionally fill in the Business profile (description, email, address, industry, photo).
Requirements page: /auth/whatsapp/wymagania.
Important — number registration: after you add a new number, Meta often shows status “Pending”. In Webivio on the Connection tab you will see that status and the Register number (set PIN) button — set a 6-digit PIN and Webivio finishes Cloud API registration. Error (#133010) Account not registered means that registration is missing — this is not a Webivio outage.
Number already in the WhatsApp Business app (coexistence)
In some cases Meta lets you keep the same number in the WhatsApp Business phone app and use it with Cloud API (Webivio) at the same time — this is called coexistence. Only Meta decides whether a number is eligible, inside the connection window.
If you see a “Not eligible” badge (PL: Brak kwalifikacji) and the number is greyed out:
- this does not mean you are missing items from the Webivio checklist — Meta is refusing that number for now;
- most common cause: the number is already in the WhatsApp Business app, but the account fails Meta’s eligibility check (often low conversation activity; Meta messages around code ~3441045);
- other causes: the number is on consumer / personal WhatsApp (not Business), it is already linked to another API provider, or there are regional limits.
What to do:
- Keep this number and the app — use WhatsApp Business normally (real customer conversations), keep the app updated, then run the Webivio connection again later.
- Another number or API-only — in the Meta window choose “Enter a new phone number”, or first disconnect / delete that number from the phone app, wait (usually about 15–30 minutes), then add it again in the connection flow.
Personal WhatsApp (not Business) on the same number cannot coexist with Cloud API — remove it from the app first.
2. Enable notifications on the webinar
- Creator -> Notifications -> WhatsApp.
- Enable the scenarios you want (confirmation, 24h, last minute, follow-up...).
- Send a test message from the panel to your own number — this works only after the number is fully registered in Meta.
3. Inbox
- WhatsApp Inbox menu (
/auth/whatsapp/inbox) or the Messages tab. - You can reply with text within the 24h window since the participant's last message (Meta's rule outside of templates).
Common Meta errors
| Code / message | Meaning | What to do |
|---|---|---|
Not eligible / Brak kwalifikacji | Meta will not let you select the number (often WA Business app / coexistence) | Keep using the number in the app and retry or a new number / disconnect from the app — see coexistence |
(#133010) Account not registered | Number not registered for Cloud API yet | In Webivio → Connection click “Register number (set PIN)”; refresh status |
(#200) missing permissions | Token / partner / WABA without full access | Check Partners and assets in Meta, then disconnect and reconnect |
The token has expired… | Meta access token expired (~60 days with the old config) | Disconnect and reconnect (Embedded Signup). This is the last refresh — new connections get a permanent token. You’ll get an email and an in-app banner 3 days before expiry. |
| Template not APPROVED | Meta has not approved the content yet | Wait for APPROVED in the Templates tab |
Permanent token
Webivio stores the token from Embedded Signup. After switching the Meta configuration to never-expiring, new connections no longer need periodic refreshes. Existing tokens keep working until they expire — then reconnect once.
Message costs
These depend on the Meta template category and the recipient's country - set on the Meta / WABA side. We don't list rates in this documentation.
What not to confuse it with
WhatsApp does not replace email. It's an additional channel with its own separate toggles.
If sending does not work
- Check the connection, phone registration and template approval status.
- Send a test from the panel to a number with the correct country code.
- For error
#133010, return to Connection and choose Register number (set PIN). - Webivio does not confirm an automatic WhatsApp fallback to SMS or email — configure those channels separately if you need a backup.