Use cases

Messaging use cases

Start from what you want to achieve. Each use case lists the channels and products that fit.

Overview

The messages enterprises send most

Business messaging falls into a handful of patterns. Transactional messages confirm something the customer did or needs to know: a one-time passcode, a payment alert, a delivery update. Service messages help the customer through a process, such as an appointment reminder or a support conversation. Promotional messages invite action and normally require the recipient’s consent.

The right channel depends on the message. SMS reaches nearly every phone without an app, which is why it is the default for passcodes and alerts. RCS and chat apps add richer content and two-way conversation where the audience and device support them. Many teams combine them with a fallback, so a message that cannot be delivered on one channel is tried on the next.

For the technical side, see the API documentation and the SMS API overview.

At a glance

Use cases and the products behind them

Use caseTypical message typeProducts that fit
One-time passcode (OTP) verificationFast, reliable delivery of verification codes.A2P SMS, Voice API, Numbers Lookup
Appointment remindersReminders with confirm and reschedule built in.A2P SMS, 2-Way Messaging, RCS
Order and delivery notificationsConfirmations, shipping updates and delivery alerts.A2P SMS, RCS, WhatsApp Business
Transaction and security alertsFast, recognisable alerts for payments and account activity.A2P SMS, SenderID, SenderID Protection
Promotional campaignsConsent-based offers with rich content and clear results.RCS, A2P SMS, WhatsApp Business
Customer support conversationsConversations, chatbots and handover on one platform.Chatbot, Knowledge Base, 2-Way Messaging

Availability, features and requirements vary by country, operator and channel provider.

Have a different use case?

Tell us what you want to achieve and we will recommend the channels and products.