Channels
Wappr is one platform for WhatsApp, Email, SMS and RCS. Contacts, conversations, campaigns and reporting are shared — you just connect the channels you want to send on.
Connecting a channel
- 1Open Channels from the sidebar. Each channel card shows its providers and any existing connections.
- 2Click Connect on the channel you need and pick a provider.
- 3Fill in the credentials. Secret fields are encrypted at rest and never shown again after saving.
- 4Give the connection a display name — useful when you run several senders on one channel.
- 5Use Send test to confirm the credentials work before you send anything to real contacts.
Providers and credentials
| Channel | Provider | What you need |
|---|---|---|
| Meta Cloud API | WABA ID, phone number ID and a permanent access token — or use embedded signup. | |
| Managed sending (recommended) | Nothing: the platform sends from the verified notify domain. | |
| Custom SMTP / provider | Host, username, password and the from address. | |
| SMS | Twilio | Account SID, auth token and a sending number or messaging service. |
| RCS | Twilio RCS | Account SID, auth token and your registered RCS agent ID. |
One channel, several connections
You can connect more than one sender per channel — for example separate WhatsApp numbers per country. Campaigns and automations pick the default connection unless you choose another.
Inbound messages
- WhatsApp inbound and delivery statuses arrive on your tenant Meta webhook and land in the shared inbox.
- SMS inbound arrives on the Twilio webhook, signature-verified, and threads onto the same contact.
- STOP / START keywords are handled automatically and update the contact's consent state.
- RCS replies fall back to SMS when the handset can't receive RCS, and stay in the same conversation.
- Email replies are tracked through the email events receiver — bounces and complaints add the address to suppression.
Using channels in campaigns and automations
Every campaign runs on one primary channel and may declare a fallback with a wait window, so a permanent failure on WhatsApp can be re-sent by email or SMS automatically. See Campaigns for the full flow.
- WhatsApp sends require an approved template; Email, SMS and RCS send your body text with variables substituted.
- Email campaigns skip contacts without an email address; SMS and RCS use the contact's E.164 number.
- Opted-out contacts are excluded on every channel.
Usage and cost
- Every send writes a usage event with the channel, provider and quantity — SMS is metered in segments, email in messages.
- Channel usage counts against your monthly plan allowance alongside WhatsApp conversations.
- Analytics breaks volume and estimated cost down per channel.
Disconnecting
Disabling a connection stops new sends immediately; queued jobs on that channel fail and, if a fallback is configured, retry on the fallback channel.
Still stuck? Open a support ticket.