Overview

The Deflector API enables you to send messages across multiple communication channels (WhatsApp, RCS, and SMS) using a single API request. It supports template-based messaging with dynamic attributes and allows you to define a delivery flow. With this flow, you can control the order in which messages are attempted to be sent across channels.

For example, you can set a fallback flow like SMS → RCS → WhatsApp. If a message is not delivered on one channel, it is automatically sent through the next channel, ensuring the message still reaches the user.

This makes the Deflector API suitable for transactional alerts, critical notifications, and large-scale messaging campaigns where reach, reliability, and efficiency are essential.

Workflow

With Deflector API, you can configure a channel fallback sequence to ensure maximum reach. If a message fails to deliver on one channel, the API automatically retries delivery on the next configured channel, without requiring additional logic from your side.

Use Cases

• Fallback Messaging for Maximum Deliverability
  Ensure near-complete message delivery by configuring a fallback flow such as SMS → RCS → WhatsApp or any preferred sequence. This approach achieves the maximum delivery rate.

• Cost Optimization
  Prioritise cost-effective channels first and fall back to richer channels only when needed. This helps you optimise messaging spend while maintaining reach.

• Experience Optimization
  Start with rich channels like RCS or WhatsApp to deliver a better user experience, and fall back to SMS when advanced channels are unavailable.

• High-Volume Notifications
  Ideal for sending bulk or critical messages like transactions, OTP, authentication, etc, where guaranteed delivery is important than engagement