Sender specifications (RBM)

When registering senders, it is mandatory to define message type, use case, and business information. Below you can find specification and restrictions for different fields.

Billing category

Based on the message content itself, Billing category can have different billing type events.

Basic message

Contains text only, and can have up to 160 UTF-8 characters. Does not support any suggested reply or CTA button. A charge is for each delivered A2P message. Supported billing events for this category: basic message, single message.

Single message

Message can have more than 160 characters. Rich content available for this type of message. Supports suggested reply or CTA button. A charge is for each delivered A2P message. Supported billing events for this category: basic message, single message.

Conversational (A2P)

Two-way communication between the brand and the user within 24 hour time frame. Use it for complex user interactions where messages are exchanged in both directions. A charge for a conversation that consists of multiple A2P and P2A messages within a given time period. In case conditions for creation of conversation are not met, standard basic/single message charging is applied. Supported billing events for this category: basic message, single message, A2P conversation.

Conversational (A2P and P2A)

Two-way communication between the brand and the user within 24 hour time frame. Use it for complex user interactions where messages are exchanged in both directions. A charge for a conversation that consists of multiple A2P and P2A messages within a given time period. In case conditions for creation of conversation are not met, standard basic/single message charging is applied. Supported billing events for this category: basic message, single message, A2P conversation, P2A conversation.

Use case

OTP

Use one-time password (OTP) message when second level of authentication is needed.

Transactional

Use this message type for delivering notifications, updates, or alerts. Tailor your message to provide information regarding a customer's services or products.

Promotional

Use this type for for marketing, sales content, and promotional messages.

Multi-use

Multi-use type is a combination of transactional and promotional messages, giving you flexibility to tailor the message to your business needs.

Webhook URL

If defined, all P2A messages sent by the end-user to the sender are forwarded to this webhook. If empy, forwarding of P2A messages is not applied.

Traffic origin

Traffic origin reflect special rules for communication defined by carrier. In general, international traffic is considered special type of traffic (e.g. OTP codes) or if the brand is sending the traffic to different country than is officially registered in. If you are not sure which traffic you should select, choose international.

Sender ID

SenderID represents unique ID for the specific sender and is used in API request for sending a message. Once created, SenderID cannot be modified.