Channel & platform1 min read
RCS Business Messaging is live on every DLVRD account
Verified sender profiles, rich cards, carousels and read receipts now work on RCS the same way they do on WhatsApp: same inbox, same campaign builder, same API.
What's changing
- Verified sender profile with your logo, brand colour and a blue tick
- Rich cards, carousels and suggested replies in campaigns
- Automatic SMS fallback when a handset has no RCS
- No new API the existing send endpoint takes an rcs channel
RCS Business Messaging has left beta and is enabled on every DLVRD account. It is the upgrade path for anyone still leaning on SMS: the same reach on Android, with branding, rich media and delivery and read receipts that SMS never had.
What you get
- A verified sender profile: your logo, brand colour, description and a verification tick in the conversation header.
- Rich cards and carousels, so a product, a booking or an order renders as a card with images and buttons instead of a wall of text.
- Suggested replies and suggested actions, which turn a notification into something the recipient can act on without typing.
- Delivery and read receipts, and typing indicators on inbound replies.
In our own beta, the same campaign sent over RCS rather than SMS returned roughly three times the click-through, across handsets covering about 98% of Android users in supported markets. Sending it takes no code changes.
Fallback is automatic
Not every handset supports RCS, and iOS coverage still varies by carrier. DLVRD checks capability at send time and falls back to SMS for anyone who cannot receive the rich version, so a campaign reaches its whole list without you maintaining two of everything. Both legs appear as one thread in the unified inbox.
Sending is the existing endpoint with the channel set to rcs. Campaigns pick it up in the channel selector, and the inbox treats RCS threads exactly like WhatsApp ones: same routing rules, same agent assignment, same analytics.