Short answer
RCS campaigns work best when the rich format helps the customer do something: browse a carousel, tap a card to track an order, or confirm an appointment with one tap. Below are 10 campaign ideas for Indian businesses. Each one shows the RCS features it uses and a plain SMS fallback. They are illustrative examples for planning - not real campaigns, real customers or measured results.
Before you use these examples
- Availability varies. A customer receives RCS only if their phone, messaging app and mobile network support it, and your RCS agent has been launched on that network.
- The use case is set when the agent is created. Google groups agents as OTP, transactional, promotional or multi-use, and a campaign should match the declared use case.
- Opt-out is required. Google's launch review asks for a working STOP (opt-out) flow. Promotional messages should go only to customers who have agreed to hear from you.
- The branded sender appears after verification and launch. The mockups below use placeholder names and deliberately show no verification mark.
- SMS fallback has to be set up. It is not automatic. For Indian SMS, the fallback text also needs a DLT-approved header and template.
1. Festive sale carousel (retail and e-commerce)
A swipeable carousel shows gift categories, and each card opens the matching page on your website. A chip lets customers ask a question instead.
RCS features: carousel of rich cards, open-URL actions, suggested reply.
SMS fallback idea: one line about the sale with a short, whitelisted link.
Festive picks are here. Swipe to explore:
Gift hampers
Diya sets
2. Order shipped update (e-commerce)
When an order ships, a card confirms it and offers a tracking button. A "Talk to support" reply routes the customer to your team.
RCS features: rich card, open-URL action, suggested reply.
SMS fallback idea: "Your order has shipped. Track: [link]" as a DLT-registered service template.
Your order has shipped
Order #12345 is on its way.
3. Appointment reminder (clinics, salons, service centres)
A reminder with quick replies to confirm or reschedule, plus actions that open the calendar, map or dialler. Keep the content free of sensitive details - see our appointment reminder examples for clinics.
RCS features: suggested replies, calendar, map and dial actions.
SMS fallback idea: date, time and a number to call.
Reminder: your appointment is on Saturday at 10:30 AM.
4. Bill or payment due reminder (utilities, subscriptions, lending)
A card shows the due date with a button to your payment page and a reply for customers who have already paid. Link only to your own official payment page, and never ask for card details or OTPs in a message.
RCS features: rich card, open-URL action, suggested reply.
SMS fallback idea: amount due, due date and a whitelisted link.
Your bill is due on 5 October
Amount due: Rs 1,499. Pay before the due date to avoid a late fee.
5. Event or webinar invitation (B2B, education, community)
An invitation card with a registration link and an "Add to calendar" action that fills in the event title and time.
RCS features: rich card, open-URL action, create-calendar-event action.
SMS fallback idea: event name, date and a registration link.
Live webinar: GST basics for small businesses
Thursday, 4 PM. Free to attend.
6. Property site-visit booking (real estate)
A carousel of projects, each with a "Book a site visit" reply and a button to call the sales team.
RCS features: carousel, suggested replies, dial action.
SMS fallback idea: project name and a number to call. Promotional SMS needs a promotional template and header.
Two projects near you are open for site visits this weekend:
2 BHK homes
Villa plots
7. Admission enquiry follow-up (education)
After an enquiry, send the course brochure as a PDF and offer a callback. Whether a PDF opens in the chat depends on the customer's messaging app, so keep a web link as a backup.
RCS features: PDF file, suggested replies.
SMS fallback idea: brochure link and counsellor number.
Thanks for your enquiry. Here is the course brochure.
Brochure-2026.pdf
8. Post-order feedback (restaurants, food delivery, retail)
Ask for a one-tap rating with suggested replies. Your system receives the reply the customer taps, so you can follow up on poor ratings.
RCS features: suggested replies.
SMS fallback idea: a short link to a feedback form.
How was your order today?
Great
Thank you! We're glad you enjoyed it.
9. Booking confirmation (travel and hospitality)
A confirmation card with booking details, a button to view the ticket or voucher, and directions to the pickup point or hotel.
RCS features: rich card, open-URL action, view-location action.
SMS fallback idea: booking reference, date and a link to the booking.
Booking confirmed
Hyderabad to Vijayawada, Friday 9:00 PM. Ref: AB1234.
10. Renewal reminder (insurance, subscriptions, AMC)
Remind customers before a policy or plan expires, with a renewal button, a "remind me later" reply and an option to speak to an advisor.
RCS features: rich card, open-URL action, suggested reply, dial action.
SMS fallback idea: expiry date and a renewal link.
Your plan expires in 7 days
Renew now to stay covered without a break.
Design limits to plan around
Google's RCS for Business documentation sets these limits, among others:
- A carousel holds between 2 and 10 rich cards.
- A rich card can carry up to 4 suggested replies or actions.
- A message can show up to 11 suggestion chips, and each suggestion label can be up to 25 characters.
- Time-sensitive messages can be given an expiry of up to 15 days, which is also a natural trigger for your fallback.
What happens when a customer taps a button
Different buttons do different things, and none of them creates a follow-up on its own:
- Suggested replies send a reply back to the business. Your system receives it, together with data you attached when you sent the message, and then decides what happens next.
- Open-URL actions open a web page. What the customer does on that page is tracked by your website, not by the RCS message.
- Dial, map and calendar actions open the phone's dialler, map or calendar.
Turning replies into leads, tickets or bookings needs an integration with your own systems. Read how RCS Business Messaging works with SMSTAKE for what we set up during onboarding.
See how your campaign could look in RCS
Tell us your use case and we will walk you through an RCS demo. Supported networks, pricing and SMS fallback setup are confirmed with you during onboarding.
Request an RCS DemoSources
Checked on 30 September 2026. Rules and prices change, so confirm current requirements with the official source before acting.
- Google for Developers - RCS for Business: send messages (rich cards, carousels, suggestions, limits)
- Google for Developers - RCS for Business: receive messages (suggested reply postback data)
- Google for Developers - RCS for Business: build your first agent (use cases)
- Google for Developers - RCS for Business: launch approval (opt-out flow requirement)