RCS offers far more than just text. From simple messages to interactive carousels with product catalogues - discover the full range of RCS messaging possibilities.
The simplest form of an RCS message. Like a classic SMS, but with the advantage of a verified sender and read receipts.
Ideal for: Short notifications, OTP codes, reminders
The enhanced text message with more characters and the ability to display suggestion chips (reply suggestions) below the message.
Ideal for: Customer communication, surveys, support enquiries
Send this exact message with POST https://api.sendrcs.eu/api/rcs/send (header X-API-Key). Full reference: docs.sendrcs.eu Each button and chip can carry its own postbackData and webhookUrl - you can get a separate callback per button or use the same postback URL on every button. It is entirely up to you whether you use postback data and URLs at all.
{
"phoneNumber": "+4512345678",
"messageType": "text",
"sendernameId": "<rcs_sender_id>",
"content": {
"text": "Good morning! Your coffee subscription expires in 3 days. Renew now and keep your free delivery and 10% member discount - your next box of freshly roasted beans ships on Monday. Would you like to renew?",
"suggestions": [
{
"reply": {
"text": "Yes, renew",
"postbackData": "yes_renew",
"webhookUrl": "https://yourapp.com/webhooks/rcs/yes-renew"
}
},
{
"reply": {
"text": "No, thanks",
"postbackData": "no_thanks",
"webhookUrl": "https://yourapp.com/webhooks/rcs/no-thanks"
}
},
{
"action": {
"text": "Manage subscription",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "manage_subscription",
"webhookUrl": "https://yourapp.com/webhooks/rcs/manage-subscription"
}
}
]
}
}The visual powerhouse message. Combine an image or video with a title (max. 200 characters), description (max. 2,000 characters) and up to 4 action buttons in an elegant card.
Button types: URL, Dial, Add-to-Calendar, Show-Location, Share-Location, Webhook
Ideal for: Product announcements, offers, event invitations
Send this exact message with POST https://api.sendrcs.eu/api/rcs/send (header X-API-Key). Full reference: docs.sendrcs.eu Each button and chip can carry its own postbackData and webhookUrl - you can get a separate callback per button or use the same postback URL on every button. It is entirely up to you whether you use postback data and URLs at all.
{
"phoneNumber": "+4512345678",
"messageType": "richCard",
"sendernameId": "<rcs_sender_id>",
"content": {
"title": "New collection just arrived!",
"description": "Discover our spring collection - now with 20% introductory discount.",
"cardOrientation": "VERTICAL",
"media": {
"height": "MEDIUM",
"contentInfo": {
"fileUrl": "https://sendrcs.eu/images/rcsexamples/shoes-1.jpg"
}
},
"cardActions": [
{
"text": "Shop now",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "shop_now",
"webhookUrl": "https://yourapp.com/webhooks/rcs/shop-now"
},
{
"text": "Call us",
"type": "dial",
"dialAction": {
"phoneNumber": "+4512345678"
},
"postbackData": "call_us",
"webhookUrl": "https://yourapp.com/webhooks/rcs/call-us"
}
],
"suggestions": [
{
"reply": {
"text": "More info",
"postbackData": "more_info",
"webhookUrl": "https://yourapp.com/webhooks/rcs/more-info"
}
},
{
"reply": {
"text": "Not interested",
"postbackData": "not_interested",
"webhookUrl": "https://yourapp.com/webhooks/rcs/not-interested"
}
}
]
},
"smsFallback": {
"message": "New collection just arrived! Discover our spring collection - now with 20% introductory discount. https://example.com",
"sendernameId": "<sms_sender_id>"
}
}Present multiple products or options in a horizontally scrollable carousel. Each card can have its own images, title (max. 200 characters), description (max. 2,000 characters) and buttons.
Button types: URL, Dial, Add-to-Calendar, Show-Location, Share-Location, Webhook
Ideal for: E-commerce, product catalogues, menus, travel offers
Send this exact message with POST https://api.sendrcs.eu/api/rcs/send (header X-API-Key). Full reference: docs.sendrcs.eu Each button and chip can carry its own postbackData and webhookUrl - you can get a separate callback per button or use the same postback URL on every button. It is entirely up to you whether you use postback data and URLs at all.
{
"phoneNumber": "+4512345678",
"messageType": "carousel",
"sendernameId": "<rcs_sender_id>",
"content": {
"cardContents": [
{
"title": "Barcelona",
"description": "From €299",
"media": {
"height": "MEDIUM",
"contentInfo": {
"fileUrl": "https://sendrcs.eu/images/rcsexamples/travel-1.jpg"
}
},
"cardActions": [
{
"text": "Book",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "book_barcelona",
"webhookUrl": "https://yourapp.com/webhooks/rcs/book-barcelona"
}
]
},
{
"title": "Rome",
"description": "From €249",
"media": {
"height": "MEDIUM",
"contentInfo": {
"fileUrl": "https://sendrcs.eu/images/rcsexamples/travel-2.jpg"
}
},
"cardActions": [
{
"text": "Book",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "book_rome",
"webhookUrl": "https://yourapp.com/webhooks/rcs/book-rome"
}
]
},
{
"title": "Paris",
"description": "From €319",
"media": {
"height": "MEDIUM",
"contentInfo": {
"fileUrl": "https://sendrcs.eu/images/rcsexamples/travel-3.jpg"
}
},
"cardActions": [
{
"text": "Book",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "book_paris",
"webhookUrl": "https://yourapp.com/webhooks/rcs/book-paris"
}
]
}
],
"suggestions": [
{
"reply": {
"text": "More destinations",
"postbackData": "more_destinations",
"webhookUrl": "https://yourapp.com/webhooks/rcs/more-destinations"
}
},
{
"action": {
"text": "All deals",
"type": "openUrl",
"openUrlAction": {
"url": "https://example.com"
},
"postbackData": "all_deals",
"webhookUrl": "https://yourapp.com/webhooks/rcs/all-deals"
}
}
]
}
}Send files directly via RCS - from images and videos to PDFs and documents. Everything directly in the messaging app, without external downloads.
Ideal for: Invoices, tickets, guides, product videos
Send this exact message with POST https://api.sendrcs.eu/api/rcs/send (header X-API-Key). Full reference: docs.sendrcs.eu Each button and chip can carry its own postbackData and webhookUrl - you can get a separate callback per button or use the same postback URL on every button. It is entirely up to you whether you use postback data and URLs at all.
{
"phoneNumber": "+4512345678",
"messageType": "media",
"sendernameId": "<rcs_sender_id>",
"content": {
"url": "https://sendrcs.eu/images/rcsexamples/shoes-1.jpg",
"caption": "Here are your edited photos from the last shoot."
}
}Find the right message type for your use case
| Type | Text | Media | Card Buttons | Suggestion Chips | Layout | Use case |
|---|---|---|---|---|---|---|
| Basic Text | Max. 160 characters | - | - | - | - | OTP, short messages |
| Rich Text | Max. 3,072 characters | - | - | Max. 11 total Reply & Action mix |
- | Support, surveys |
| Rich Card | Title: 200 Description: 2,000 |
1 image/video JPG, PNG, GIF, MP4, WebM |
Max. 4 per card | Max. 11 total Reply & Action mix |
Vertical / Horizontal Image: Left / Right |
Offers, events |
| Rich Carousel | Title: 200 Description: 2,000 per card |
2-10 cards Image/video per card |
Max. 4 per card | Max. 11 total Reply & Action mix |
Vertical only | Product catalogues |
| Files & Media | Caption: 3,072 URL max. 2,000 characters |
Max. 100 MB JPG, PNG, GIF, MP4, MPEG, WebM, H.263 |
- | - | - | Documents, videos |
Max. 25 characters per button and suggestion chip
Max. 250 KB JSON payload per message
URL, URL-in-Webview, Dial, Calendar, Show location, Share location, Webhook/Postback
Allowed, but flagged with a warning - iPhones reject such messages, Android delivers them. To reach every phone, put links on chips and buttons or use a rich card.
SendRCS supports five RCS message types: Basic Text (plain text up to 160 characters), Rich Text (up to 3,072 characters with suggestion chips and buttons), Rich Card (image or video with title, description and buttons), Rich Carousel (2-10 scrollable cards) and Files & Media (images, videos, PDFs, documents and audio). SMS fallback is available for every type.
A Basic Text message holds up to 160 characters, like a single SMS. Rich Text messages hold up to 3,072 characters. In Rich Cards and Carousels, each card has a title of up to 200 characters and a description of up to 2,000 characters. Buttons and suggestion chips are limited to 25 characters each.
Each Rich Card or carousel card can have up to 4 action buttons, and every message can show up to 11 suggestion chips below it. Seven button types are available: URL, URL-in-webview, dial, add-to-calendar, show-location, share-location and webhook/postback.
A Rich Card is a single card with one image or video, a title, a description and up to 4 buttons - ideal for one product, offer or event. A Rich Carousel combines 2 to 10 such cards in a horizontally scrollable row, so recipients can browse several products or options in one message.
Images (JPEG, PNG, GIF), videos (MP4, MPEG, WebM, H.263), audio files and PDFs or documents, each up to 100 MB. Files open directly in the recipient's messaging app without external downloads - ideal for invoices, tickets, guides and product videos.
They are Google's billing categories for RCS Business Messaging (RBM). A Basic Message is text only, up to 160 characters, without suggestion chips or rich elements. A Single Message is any richer message: text over 160 characters, messages with suggestion chips, Rich Cards, Carousels and media. SendRCS shows the category next to each message type so you know how it is billed.
You can, but validation returns a warning: iPhones reject a text or textBasic message whose text contains an email address or web address (URL, www. host or bare domain), while Android delivers it. The message is still accepted and sent. To reach every phone, put links on suggestion chips and buttons, or use a rich card: card titles, descriptions and chip labels may contain an address.
Get started today and discover which RCS message type best suits your business.