Channels overview
An Arino One instance runs 18+ channels through one inbox and one contact record. Each channel has its own identity, opt-in rule and message-window behaviour — the console normalises the rest.
The core set
| Channel | Best for | Business-initiated rule |
|---|---|---|
| Support, transactional, marketing | Approved template required outside the 24-hour window | |
| Social support and commerce | Reply window applies | |
| Messenger | Social support | Reply window applies |
| SMS | OTP, alerts, fallback | Sender registration by country |
| RCS | Branded rich messaging | Verified agent required |
| Long-form, receipts, documents | Authenticated domain | |
| Live chat widget | On-site conversations | None |
| PingMe | One-press live voice | None |
Choosing a channel
Pick by the recipient's expectation, not by cost. Time-critical and identity-critical traffic goes to SMS; conversational and rich traffic goes to WhatsApp or RCS; documents go to email.
Next step
Bring this to your enterprise stack
See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.