Navigators
Navigators allow you to send a message via the best of multiple channels.
Last updated
Was this helpful?
Navigators allow you to send a message via the best of multiple channels.
Last updated
Was this helpful?
Navigator behaviour may vary according to the country you are sending to and the message type. You can see the preferred kind of SMS channels for each scenario here and check any existing navigator in your workspace via the Navigator TAB in the developer dashboard
Navigators only support SMS channels. Other platform channels (WhatsApp, RCS, etc.) will not be included in any message sent via Navigators.
By default, each workspace will have 4 navigators.
Please contact our support team if you need a customized navigator added to your workspace. One of our support support agents will coordinate its provisioning
Marketing: The primary objective of marketing navigators is to send bulk traffic. They will only attempt delivery via PROMOTIONAL
channels, adhering to strict compliance checks, including quiet hours and Opt-Out regulations.
Conversation: Conversational navigators consider only two-way CONVERSATIONAL
channels, ignoring any one-way channels (such as those using Alphanumeric senders).
Transactional: The transactional navigator prioritizes high-quality routes when applying only the minimum required compline check. Transactional navigators will only send traffic from TRANSACTIONAL
channels to ensure the best possible Quality of Service.
OTP: The 2FA navigator prioritizes deliverability above all. It attempts to send messages via 2FA
channels first but will use TRANSACTIONAL
channels if none are available, and as a last resort, it will utilize PROMOTIONAL
channels.
When sending OTPs, ensure you have either 2FA or transactional channels in your workspace. OTP messages delivered through promotional channels during quiet hours may be delayed until the following day.
Navigators can access as many countries as there are channels available to them. Coverage may vary over time based on channel availability and health.
You can check a navigator coverage and the channel it will use for each country by clicking on it in the navigator set up page
A-Sync : this will start a background process that may require some time to complete. A Get call may be required to to retrieve the final result .
The Navigators POST request follows the same schema and requires the same body as the channels POST request
The navigator message will contain navigator metadata, including.
providing UUID relevant to both the navigator objection and the navigator message objects
Navigator may attempt to send messages via more than one channel. attempts will list and providing information about all channels a navigator used when handling a given message
You can get messages sent to a navigator by making a request to the channel endpoint that accepted the message based on the response above
We recommend subscribing at least to navigator.outbound. Navigator event will provide you information about any fallback as well the status of your navigator messages.
Note: Navigator message status reflects the final outcome of all delivery attempts made by the Navigator. For example, if a WhatsApp delivery fails but the fallback via SMS succeeds, the navigator message status will be marked as "Delivered."
Optional: channel Webhooks
If you are interested in diving deep on specific attempts status you can also subscribe to sms.outbound
and one for whatsapp.outbound
. When doing so you will be able to retrieve the navigator ID and navigator message id in the meta field.
If you've only sent SMS messages before—especially if you haven’t operated in the U.S.—you’ve likely only used a one-way channel. WhatsApp, however, is a two-way channel by design, so users may try to contact you there. When using a Navigator to send both SMS and r WhatsApp traffic, it’s essential to monitor incoming messages to avoid missing user inquiries. Ignoring users can lead to frustration and could result in them reporting your channel to Meta, potentially causing suspension.
You can subscribe to sms.inbound
and whatsapp.inbound
event to capture all incoming messages in your workspace
NOTE incoming messages will not be linked to a navigator and will nto have the navigator information in the meta field
If you navigate to the customer service section of our side panel you can find all incoming conversations in the entry corresponding to yours SMS or WhatsApp channels.
If you want to limit the selection of channels a navigator can access, you can create a customized one.
You can add or remove channels from a navigator
You can check SMS and Log insight separately via the relevant SMS and WhatsApp tabs in our developer view, you can also use the dedicated Navigator logs, which does allow the tracking of attempts and fallbacks
Get list of the navigators configured for a workspace. Navigators are used to select a channel for a message based on its content, type, recipient, etc. The type of the navigator defines how the channel will be selected.
The ID of the workspace
Limits the number of results to return
Pagination token that keeps of track of the current position in the list
Order in which to retrieve the results
The type of navigator defines how the navigator selects a channel for a message. * messaging - navigator configured with a pool of channels and performs channel selection based on channel availability and best originator type for a recipient country. The best originator type for a recipient country is determined by the strategy - prioritized list of originator types for each country. At this moment, the default pre-configured strategy (set of country policies) is used see https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/choosing-the-right-sender-availability-and-restrictions-by-country
messaging
, use-case-messaging
, otp
otp
, transactional
, marketing
, conversation
Get a channel message
The ID of the workspace
The ID for a message
The ID for a channel
Send a message to a channel using the navigator. Channel webhooks will provide status updates, so each channel the navigator uses should have webhooks configured. Data returned via webhooks will have navigator metadata, including navigator ID and navigator message ID.
The ID of the workspace
The ID for a navigator
Create a new navigator for the workspace.
The ID of the workspace
The name of the navigator.
The type of navigator defines how the navigator selects a channel for a message. * messaging - navigator configured with a pool of channels and performs channel selection based on channel availability and best originator type for a recipient country. The best originator type for a recipient country is determined by the strategy - prioritized list of originator types for each country. At this moment, the default pre-configured strategy (set of country policies) is used see https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/choosing-the-right-sender-availability-and-restrictions-by-country
messaging
Update a navigator by ID
The ID of the workspace
The ID for a navigator
The name of the navigator.
The type of navigator defines how the navigator selects a channel for a message. * messaging - navigator configured with a pool of channels and performs channel selection based on channel availability and best originator type for a recipient country. The best originator type for a recipient country is determined by the strategy - prioritized list of originator types for each country. At this moment, the default pre-configured strategy (set of country policies) is used see https://docs.bird.com/applications/channels/channels/supported-channels/sms/concepts/choosing-the-right-sender-availability-and-restrictions-by-country
messaging
, use-case-messaging
, otp
No body