Messaging Channels
The Qlara Partner Gateway supports three channels, each with different capabilities and reach. Understand the strengths of each to choose the right channel for your use case.
SMS
The most reliable, universal channel.
Send text messages to any mobile phone worldwide. SMS requires no approval or templates—just send.
When to Use SMS
- Maximum reach (works on every phone)
- Simple, text-only messages
- Transactional alerts and confirmations
- Backup channel for other platforms
Characteristics
- Plain text only (no rich media)
- No template approval needed
- Instant delivery (typically within seconds)
- Two-way capable (receive replies)
- Works on every phone globally
- Lowest cost per message
Endpoint: POST /message-server/sms/send
RCS (Rich Communication Services)
Rich media on Android devices.
RCS delivers enhanced messages with images, buttons, and interactive elements on Android. Requires template approval. Falls back to SMS on unsupported devices.
When to Use RCS
- Reach Android users with rich content
- Interactive buttons and quick replies
- Images and media in messages
- Higher engagement than SMS
Characteristics
- Rich media (images, videos, buttons)
- Template approval required
- Delivery only on Android devices (SMS fallback on others)
- Two-way capable
- Moderate cost (between SMS and WhatsApp)
- Higher engagement than SMS
Endpoint: POST /message-server/rcs/send
Template Requirements
RCS messages must use pre-approved templates. Templates include:
- Message body with variable placeholders
- Optional media (images, videos)
- Optional action buttons
- Quick reply options
Contact support to submit templates for approval.
WhatsApp
Premium reach with highest engagement.
Send messages via WhatsApp using Meta-approved templates. Free-form messages are allowed within 24 hours of customer interaction. Highest engagement and two-way conversation capabilities.
When to Use WhatsApp
- Premium customer communications
- Require high engagement rates
- Support and customer service
- Two-way conversations
- Media-rich messages to users who actively engage
Characteristics
- Rich media (images, videos, documents)
- Template approval required (by Meta)
- Free-form messages within 24-hour window after customer contact
- Highest engagement rates
- Two-way messaging with customer
- Highest cost per message
- Requires customer opt-in
Endpoint: POST /message-server/whatsapp/send
24-Hour Window
After a customer sends you a message on WhatsApp, you have 24 hours to reply with free-form (non-template) messages. After 24 hours, you must use an approved template.
Feature Comparison
| Feature | SMS | RCS | |
|---|---|---|---|
| Rich Media | No | Yes | Yes |
| Templates | Not required | Required | Required |
| Approval Process | None | Carrier review | Meta review |
| Device Support | All phones | Android only | All platforms |
| Two-way | Yes | Yes | Yes |
| Reach | ~100% | ~70% (Android) | ~60% (opt-in) |
| Cost | Low | Medium | High |
| Engagement Rate | Low | Medium | High |
| 24h Free-form Window | N/A | No | Yes |
Choosing the Right Channel
Send to Everyone?
Use SMS. It reaches every phone with no approvals.
Rich Content for Android?
Use RCS. It falls back to SMS automatically on unsupported devices.
Premium Engagement?
Use WhatsApp. Highest engagement, two-way conversations, rich media.
Maximize Reach?
Use the Fallback Chain: WhatsApp → RCS → SMS. Try WhatsApp first; if it fails, automatically try RCS; if that fails, use SMS. See fallback setup below.
Automatic Fallback Chain
The Qlara API can automatically fall back between channels if delivery fails:
- Try WhatsApp (if approved)
- If WhatsApp delivery fails → Try RCS
- If RCS delivery fails → Use SMS
To enable fallback, include fallback: true in your request (where supported). The system will attempt each channel in order until one succeeds.
Example request with fallback:
{
"phoneNumber": "+393901234567",
"message": "Important update",
"fallback": true,
"templateId": "template_123"
}
This single request will try WhatsApp, then RCS, then SMS automatically.
Delivery Tracking
Each channel supports real-time delivery tracking.
Webhook Method (Recommended) Receive instant notifications when status changes. See Webhooks Guide.
Polling Method Manually check status at any time. See Webhooks Guide for polling endpoint.
Next Steps
- Quick Start — Send your first message
- Webhooks — Set up delivery tracking
- Campaigns — Send to multiple recipients
Have questions about channel selection? Contact support@agiletelecom.com.