Skip to content
OmniChannels.ai
Menu

Free tool

RCS rich card builder and preview

Design a rich card or a carousel of up to 10 cards with media, buttons and suggested replies. See it the way customers will, check it against Google's RBM limits and write the SMS fallback in the same place.

Free · no sign-up · runs in your browser

Start from an example

Cards

3 cards: sent as a carousel (2–10 cards).

Media

Illustrative placeholders. In production you host the image, GIF or video (up to 100 MB) at a public URL.

18/200
67/2000

Card suggestions

2/4

Up to 4 replies or actions per card, 25 characters each.

  • 7/25
  • 11/25
Layout

Suggested replies and actions

3/11

Up to 11 chips shown under the message. They disappear after the user taps one or replies.

  • 16/25
  • 13/25
  • 13/25

Sent instead when the phone or network doesn't support RCS. Keep it short and include the link.

Encoding
GSM-7
Characters
134
SMS parts
1
Left in this part
26

Within Google's RBM limits. Ready to send.

Spec checklist

  • Note: Media: host files at a public HTTPS URL, up to 100 MB; thumbnails up to 100 kB. Images here are placeholders.
  • Note: Carousel cards are shown at a uniform height, so keep titles and descriptions of similar length.
  • Pass: Carousel of 3 cards (allowed: 2–10).
  • Pass: Card 1: title 18/200, description 67/2000, 2/4 suggestions.
  • Pass: Card 2: title 16/200, description 44/2000, 2/4 suggestions.
  • Pass: Card 3: title 19/200, description 49/2000, 2/4 suggestions.
  • Pass: 3/11 suggested replies and actions.
  • Pass: SMS fallback: 134 characters, GSM-7, 1 part.

Limits checked against Google's RCS Business Messaging documentation (phones.agentMessages reference and send-messages guide), verified October 2026. phones.agentMessages · Send messages

Message JSON (illustrative)

An RBM-style AgentMessage with placeholder media URLs, for orientation only. Our RCS API accepts the same card, carousel and suggestions with automatic SMS fallback.

{
  "contentMessage": {
    "richCard": {
      "carouselCard": {
        "cardWidth": "MEDIUM",
        "cardContents": [
          {
            "title": "Ultra running shoe",
            "description": "Lightweight cushioning for long runs. AED 349, free 2-day delivery.",
            "media": {
              "height": "MEDIUM",
              "contentInfo": {
                "fileUrl": "https://example.com/rcs/card-1-product.jpg",
                "forceRefresh": false
              }
            },
            "suggestions": [
              {
                "action": {
                  "text": "Buy now",
                  "postbackData": "card1_buy_now",
                  "openUrlAction": {
                    "url": "https://shop.example.com/p/ultra"
                  }
                }
              },
              {
                "reply": {
                  "text": "Check sizes",
                  "postbackData": "card1_check_sizes"
                }
              }
            ]
          },
          {
            "title": "Pro sports watch",
            "description": "GPS, heart rate and 10-day battery. AED 899.",
            "media": {
              "height": "MEDIUM",
              "contentInfo": {
                "fileUrl": "https://example.com/rcs/card-2-event.jpg",
                "forceRefresh": false
              }
            },
            "suggestions": [
              {
                "action": {
                  "text": "Buy now",
                  "postbackData": "card2_buy_now",
                  "openUrlAction": {
                    "url": "https://shop.example.com/p/pro-watch"
                  }
                }
              },
              {
                "reply": {
                  "text": "Compare models",
                  "postbackData": "card2_compare_models"
                }
              }
            ]
          },
          {
            "title": "Carry-on travel bag",
            "description": "Water-resistant and cabin-size approved. AED 279.",
            "media": {
              "height": "MEDIUM",
              "contentInfo": {
                "fileUrl": "https://example.com/rcs/card-3-travel.jpg",
                "forceRefresh": false
              }
            },
            "suggestions": [
              {
                "action": {
                  "text": "Buy now",
                  "postbackData": "card3_buy_now",
                  "openUrlAction": {
                    "url": "https://shop.example.com/p/carry-on"
                  }
                }
              },
              {
                "reply": {
                  "text": "See colours",
                  "postbackData": "card3_see_colours"
                }
              }
            ]
          }
        ]
      }
    },
    "suggestions": [
      {
        "reply": {
          "text": "Talk to an agent",
          "postbackData": "chip_talk_to_an_agent"
        }
      },
      {
        "action": {
          "text": "Nearest store",
          "postbackData": "chip_nearest_store",
          "viewLocationAction": {
            "query": "Horizon Store Dubai"
          }
        }
      },
      {
        "reply": {
          "text": "Stop messages",
          "postbackData": "chip_stop_messages"
        }
      }
    ]
  }
}
RCS API docsRCS for business

Need a verified RCS sender and carrier launch in your markets? We register the agent, handle approval and fall back to SMS automatically. Talk to an RCS expert

Nothing you type here is sent to our servers.

Short answer

An RCS rich card is a message bubble that combines media, a title of up to 200 characters, a description of up to 2,000 characters and up to 4 suggested replies or actions. Cards can be sent alone or as a carousel of 2 to 10 cards, and a message can add up to 11 suggestion chips. Each suggestion's text is limited to 25 characters. Phones without RCS receive an SMS fallback instead.

Trusted infrastructureOfficial Meta Business Solution ProviderGoogle RBM partnerGSMA memberISO/IEC 27001:2022ISO/IEC 27018ISO 9001:2015ISO 22301SOC 2 Type IIGDPR compliant

How to build an RCS rich card

  1. 1

    Start from an example

    Load a product carousel, flight check-in or delivery update, then type your brand name to see the verified sender header.

  2. 2

    Edit each card

    Choose a media style, write the title and description, and add up to 4 replies or actions: open a link, call, view a location.

  3. 3

    Set layout and chips

    Pick vertical or horizontal, media height or carousel card width, then add up to 11 suggested replies under the message.

  4. 4

    Check fallback and export

    Review the SMS fallback text and its part count, fix the checklist, then copy the illustrative JSON.

RCS rich card limits

Google's RCS Business Messaging (RBM) API reference sets the limits a rich card must respect. Messages that break them are rejected by the API, so this builder checks them as you type.

Source: Google, RBM reference for phones.agentMessages, https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages, and the send messages guide, https://developers.google.com/business-communications/rcs-business-messaging/guides/build/messages/send (checked October 2026).

  • Card title: up to 200 characters. Description: up to 2,000 characters.
  • Suggestions on a card: up to 4 replies or actions, each up to 25 characters.
  • Suggestion chips under the message: up to 11.
  • Carousel: 2 to 10 cards, with card width SMALL (120 DP) or MEDIUM (232 DP).
  • Media height: SHORT (112 DP), MEDIUM (168 DP) or TALL (264 DP). Media files up to 100 MB; thumbnails up to 100 kB.
  • Postback data and fallback URLs: up to 2,048 characters. Plain text messages: up to 3,072 characters.

Standalone card or carousel?

Use a standalone card when there is one thing to act on: a booking to confirm, a parcel to track, a payment to complete. A vertical card puts media on top and works best with a strong image. A horizontal card places a thumbnail beside the text, which suits receipts and status updates; it needs a title, description or suggestion alongside its media.

Use a carousel when the customer is choosing: products, flights, plans, appointment slots. Keep cards consistent, all with media or all without, and give titles and descriptions a similar length, since carousel cards are shown at a uniform height. Put the most likely choice first.

Suggested replies and actions

Suggested replies send a fixed text back to your agent along with postback data, so your bot knows exactly which option was tapped. Suggested actions open the phone's own apps: the dialer, the browser or a webview, maps, the calendar, or the location picker to share a position.

Card suggestions stay attached to the card. Chips appear in a scrolling row under the latest message and disappear once the customer taps one or replies, so use them for next steps such as "Talk to an agent" or "Stop messages". Since November 2025, open URL actions must use http:// or https:// links.

Verified sender and SMS fallback

Every RCS business agent is verified before launch: Google and the carriers check the brand, logo and use case, and the conversation shows the brand name with a verified badge. That trust signal is a large part of why RCS messages get higher engagement than plain SMS.

Not every phone or network supports RCS, so production traffic needs a fallback. The SMS version should carry the essentials and a link. One SMS holds 160 GSM-7 characters or 70 UCS-2 characters; longer texts are split into parts of 153 or 67 characters, each billed as one message. Arabic text, emoji and even curly quotes force UCS-2, so the builder counts parts and can swap typographic characters for plain ones.

About the exported JSON

The export follows the shape of an RBM AgentMessage contentMessage, with a standaloneCard or carouselCard, card suggestions and message-level suggestions. Media URLs are placeholders and postback data is generated from the button text. It is illustrative: use it to brief developers or compare with your provider's API.

With OmniChannels.ai you send the same card, carousel and suggestions through one REST API or a campaign, with automatic SMS fallback and delivery reports for both channels.

RCS rich card questions

What is an RCS rich card?

A rich card is an RCS message that combines an image, GIF or video with a title, description and up to 4 tappable suggestions in a single bubble. It is sent by a verified business agent and appears in the phone's default messaging app, such as Google Messages.

How many cards can an RCS carousel have?

A carousel holds between 2 and 10 cards. Each card follows the same limits as a standalone card: a 200-character title, a 2,000-character description and up to 4 suggestions.

How many suggested replies can an RCS message have?

Up to 11 suggestion chips per message, plus up to 4 suggestions on each card. Every suggestion's text is limited to 25 characters.

What happens if the recipient's phone does not support RCS?

The RCS message cannot be delivered, so your platform sends a fallback, usually an SMS with the key information and a link. OmniChannels.ai can fall back to SMS automatically.

What is the RCS verified sender badge?

It shows that the brand behind the agent has been verified before launch. Customers see the brand name, logo and a verified badge in the conversation, which helps them trust links and buttons.

What image size should I use for an RCS card?

Media files can be up to 100 MB and thumbnails up to 100 kB. The displayed height is SHORT (112 DP), MEDIUM (168 DP) or TALL (264 DP); keep the important part of the image centred, because it is cropped to the chosen height.

Is RCS available in the Middle East?

RCS business messaging depends on carrier launch in each country and on the handset. Coverage is growing; contact us to check availability for your target markets and set up SMS fallback where RCS is not live.

More free tools