Rich RCS Messages: Images, Buttons, and Carousels

The great promise of RCS is leaving plain text behind and opening a range of interactive formats. Rich RCS messages let you combine images, buttons, and carousels inside the native messaging app, turning every notification into a mini experience. This guide walks through each format and when to use it.

From notification to a message that acts

An SMS can only say "your order has shipped." A rich RCS message can show a photo of the package, a button to track it, and another to contact support, all in the same bubble. The difference is not aesthetic, it is functional. The customer acts without leaving the chat.

The building blocks of RCS

1. Formatted text and media

Beyond the 160 characters of SMS, RCS supports long messages with embedded images, GIFs, and video. Use media when the visual context adds value: a product, a map, a receipt.

2. Suggested replies

These are buttons that offer predefined responses. When tapped, the customer sends that reply without typing. Ideal for:

• Confirming or canceling ("Yes, confirm" / "Reschedule").
• Choosing between options ("See offers" / "Talk to an agent").
• Rating ("Excellent" / "Okay" / "Poor").

They reduce friction and guide the conversation.

3. Suggested actions

Unlike replies, these trigger an action on the device:

• Open a URL: send to a product or checkout page.
• Dial a phone number: start a call with one tap.
• View a map or share location.
• Add to calendar.

They are the bridge between the message and the real world.

4. Carousels (rich cards)

A carousel is a swipeable row of rich cards, each with an image, title, description, and its own buttons. Perfect for:

• Showing multiple products with price and buy button.
• Presenting plans or packages side by side.
• Offering help articles or categories.

It is essentially a mini storefront inside the chat, and because each card acts independently, the customer can browse and act on exactly the item that interests them without you sending five separate messages.

How to design rich messages that work

Having powerful formats does not guarantee good results. A few practical rules:

1. One goal per message: do not cram five competing buttons.
2. Quality images sized to load fast.
3. Short copy: rich format is no excuse for long text.
4. Clear, actionable buttons: verbs, not vagueness ("Track order," not "Info").
5. Brand consistency: colors, tone, and logo aligned with your verified identity.
6. Think about fallback: if the message drops to SMS, the text should stand on its own.

Concrete examples by use case

• Ecommerce: a carousel of recommendations with a "Buy" button on each card.
• Services: an appointment reminder with suggested replies "Confirm" / "Change."
• Support: a message with actions "View status" and "Talk to agent."
• Reservations: a card with a venue photo, "Book" and "Get directions" buttons.

Accessibility and good taste in rich messages

A common mistake is assuming "richer" always means "better." It does not. A message that overwhelms with heavy images, five buttons, and endless text ends up worse than a clear SMS. A few taste guidelines:

• Visual hierarchy: let the most important element (the offer, the action) stand out first.
• Alt text and clarity: do not pack all the information into the image; the text should carry the message on its own.
• Contrast and legibility in buttons, especially in dark mode.
• Consistency across cards in a carousel: same style, same button logic.

The best rich messages do not look like ads: they look like timely help. That is the standard to aim for.

Where to orchestrate all of this

Designing and sending rich messages is only half the work; the other half is managing the replies. When someone taps "Talk to agent," that thread must reach your team with full context. With Omnifox you can build rich RCS templates and, when the customer interacts, that conversation lands in the unified inbox alongside WhatsApp, Instagram, SMS, and webchat, ready for a human or AI agent to continue without losing the thread.

Common mistakes that ruin a rich message

• Overloading the card with too much text or too many buttons.
• Using heavy images that load slowly.
• Forgetting opt-in and firing rich messages without permission.
• Not testing on real devices before scaling.
• Ignoring fallback and losing those without RCS.

Conclusion

Rich RCS messages turn a simple notification into an interactive experience: images that hook, buttons that act, and carousels that showcase. The key is purposeful design and smart handling of every reply.

If you want to create rich RCS messages and manage every interaction from one place, try Omnifox and take your messaging beyond plain text.