Skip to content
TXTPro

RCS Business Messaging

RCS Business Messaging for verified, branded conversations

RCS Business Messaging (RBM) lets a business send rich, interactive messages — with its verified name and logo, images, cards, carousels and tappable buttons — directly into the default messaging app on supported Android phones, using the RCS (Rich Communication Services) standard.

TXTPro helps businesses launch RCS agents, design rich message journeys and send them at scale through an API — from brand verification and agent onboarding to analytics and delivery reports.

Capabilities

What you can do with RCS Business Messaging

  • Verified sender identity

    Messages show your verified business name, logo and brand colour, helping customers recognise genuine communication.

  • Rich cards

    Combine an image or video, title, description and action buttons in a single message.

  • Carousels

    Show several rich cards side by side — ideal for products, plans, properties or courses.

  • Suggested replies & actions

    Tappable chips that let customers reply, open a URL, dial a number, view a location or add a calendar event.

  • Rich media

    Send images, GIFs, video and PDFs where supported, without links to external pages.

  • Read & interaction analytics

    Delivery and read receipts plus button-click events, where supported by the device and network.

YB

YourBrand

Verified business

Hi Priya, your favourites are back in stock. Take a look:
Running Shoes product photo

Running Shoes

₹2,499

View product
Buy now
Training Tee product photo

Training Tee

₹799

View product
Buy now
Show moreStore near meTalk to us
Illustrative example. Appearance varies by device and messaging app.

Use cases

Common RCS Business Messaging use cases

  • Product discovery

    Carousels of products or plans with “View” and “Buy” actions.

  • Booking confirmations

    Confirmations with “Add to calendar”, “Get directions” and “Reschedule” buttons.

  • OTP with brand trust

    Codes delivered from a verified sender to reduce spoofing concerns.

  • Payment reminders

    Due-date reminders with a “Pay now” action linking to your payment page.

  • Feedback collection

    Collect ratings with suggested-reply chips instead of external survey links.

  • Lead qualification

    Let prospects choose options through quick replies before a sales call.

How does RCS Business Messaging work?

RCS is the GSMA standard that upgrades SMS with modern chat features. RCS Business Messaging, operated by Google together with participating mobile networks, allows verified businesses to send messages through an “agent” — the branded identity that appears in the customer’s messaging app.

When you send a message, the platform checks whether the recipient’s device and network support RCS. Supported recipients receive the rich message in Google Messages or the device’s default RCS-capable app. Device and network support varies, so reachability should be checked for your audience.

RCS agent verification and onboarding

Every business needs an approved RCS agent before it can message customers. The onboarding process typically involves:

  1. Company details — legal business name, business address, contact person, contact phone, corporate email and website URL.
  2. Business verification documents — a GST certificate, Certificate of Incorporation or applicable business registration document that supports your legal business name and business address.
  3. Brand assets — brand name, a description of up to 100 characters, a 224 × 224 pixel logo, a 1440 × 448 pixel banner, and support phone and email.
  4. Legal links and use case — public privacy policy and terms URLs, consent / opt-in information and your messaging use cases.
  5. Brand verification and launch approval — TXTPro submits the agent for business and brand verification; an authorised representative may need to confirm the details, and launch follows the relevant approval process.
  6. Testing — messages are tested on test devices before launch.

Verification and launch approvals are decided through the relevant platform and network approval process, so TXTPro cannot guarantee approval or timelines. We prepare your agent assets and use-case information to meet the published guidelines. See the full RCS registration and onboarding guide.

RCS vs SMS: when should you use RCS?

SMSRCS Business Messaging
Sender identityHeader (sender ID) textVerified brand name, logo and colour
ContentPlain textText, images, video, cards, carousels
InteractivityLinks in textSuggested replies, action buttons
ReachVirtually every mobile phoneRCS-capable devices on supported networks
AnalyticsDelivery statusDelivery, read and click events (where supported)
India onboardingDLT registration: Principal Entity (PE ID), headers and SMS templatesBusiness verification and agent launch approval — no DLT registration or PE ID
Timing in IndiaPromotional SMS: 10:00 AM–9:00 PM ISTBusiness-initiated conversations: 7:00 AM–10:00 PM IST

RCS works best for engagement-heavy journeys: product discovery, booking confirmations with actions, and re-engagement. SMS remains the universal fallback. See RCS vs SMS vs WhatsApp for a full comparison.

RCS Messaging Hours in India

Google’s published business rules for RCS Business Messaging in India allow businesses to initiate conversations between 7:00 AM–10:00 PM IST, seven days a week. Promotional RCS campaigns should be scheduled to start and finish inside this window.

RCS and SMS timing in India compared
RCS Business MessagingPromotional SMS
Window7:00 AM–10:00 PM IST, seven days a week10:00 AM–9:00 PM IST
Set byGoogle’s RCS Business Messaging business rules for IndiaTRAI’s TCCCPR regulations and operator Codes of Practice
Applies toBusiness-initiated conversationsDelivery of promotional SMS, subject to recipient preferences
Other limitsReputation-based reach limits for promotional agentsDND preferences, approved DLT templates and operator scrubbing

Submission, conversation initiation, delivery and read receipts

  • Submission — your system sends the message to the RCS platform through the API. An accepted request means the platform has taken the message, not that it has been delivered.
  • Conversation initiation — a message your agent sends when the user has not messaged first starts a business-initiated conversation. This is what the 7:00 AM–10:00 PM IST window covers.
  • Delivery — a delivered event is reported when the message reaches the recipient’s device.
  • Read — a separate read event is reported when the recipient opens the message, where supported. A delivered message has not necessarily been read.

Offline recipients and message expiry

If the recipient’s phone is offline, the RCS platform still accepts the message and keeps trying to deliver it, so the message can arrive later than it was sent. Google’s documentation says undelivered messages are deleted 30 days after submission. For time-sensitive content — OTPs, limited-time offers, appointment reminders — set a message expiry (between six seconds and 15 days) or revoke the message, and use SMS fallback where the information must arrive on time.

Promotional reach limits

Google limits promotional RCS agents in India by agent reputation over a rolling 28-day period: the initial messages an agent can send to each user (2 at low, 4 at medium and 8 at high reputation), the unique users it can reach (1 million, 25 million and 300 million), and the daily promotional messages a user can receive from low-reputation agents combined. New agents start with a low reputation. Replies to messages the user sent first are exempt from these limits.

OTP and transactional RCS

Google’s India rules state the 7:00 AM–10:00 PM IST window for business-initiated conversations and do not publish separate hours for OTP or transactional agents. Do not assume OTP or transactional RCS can initiate conversations 24×7 — confirm the rules for your agent’s use case with TXTPro before launch.

RCS timing and SMS DLT rules are separate

RCS hours come from Google’s RCS business rules, not from TRAI’s DLT framework. RCS bot registration is separate from SMS DLT registration. A DLT registration or PE ID is not required for TXTPro's RCS bot onboarding. RCS onboarding follows its own business verification and agent launch process. SMS fallback — sending an SMS when a recipient cannot receive RCS — is a separate SMS service subject to its own DLT requirements: a registered Principal Entity, header and SMS template. Fallback SMS also follows the SMS sending timings for its category: promotional SMS is delivered from 10:00 AM to 9:00 PM IST.

Sources: Google’s RCS agent use cases and business rules and sending messages, including offline recipients and expiry. Google can update these rules, so confirm the current rules before launching a campaign.

RCS API integration

RCS messages are sent through an API: your system submits the recipient, agent and message content (text, rich card or carousel JSON with suggestions) and can receive events such as delivered, read, user replies and suggestion taps on a webhook, depending on what the RCS platform supports. This makes it possible to build conversational flows, for example confirming an appointment with a single tap. TXTPro shares API documentation during onboarding. The RCS webhook integration guide explains these events and how to process them.

Onboarding

How RCS Business Messaging onboarding works

  1. 01

    Use-case review

    We map your journeys and decide what to send over RCS and where SMS fallback is needed.

  2. 02

    Agent assets

    Prepare your agent name, logo, banner, description and policy links to platform guidelines.

  3. 03

    Verification & approval

    Business and brand verification, then agent launch approval — no DLT registration or PE ID needed.

  4. 04

    Template & flow design

    Design rich cards, carousels and suggestion flows for each use case.

  5. 05

    Integration & launch

    Connect your systems via API, test on devices and go live.

FAQs

RCS Business Messaging FAQs

Can’t find your answer? Contact our team.

What is the difference between RCS and SMS?

SMS sends plain text from a header. RCS Business Messaging sends rich content — images, cards, carousels and buttons — from a verified brand profile, and can report read receipts and button taps. RCS requires an RCS-capable device and network; SMS works on virtually every phone.

Do customers need to install an app to receive RCS messages?

No. RCS messages arrive in the phone’s default RCS-capable messaging app, such as Google Messages on Android, when RCS is enabled on the device and supported by the network.

Is DLT registration required for RCS Business Messaging?

No. RCS bot registration is separate from SMS DLT registration. A DLT registration or PE ID is not required for TXTPro's RCS bot onboarding. RCS onboarding follows its own business verification and agent launch process. If you also use SMS fallback, that fallback SMS is a separate service with its own DLT requirements.

Is a PE ID required to register an RCS bot?

No. A Principal Entity ID (PE ID) is part of SMS DLT registration. It is not required for TXTPro’s RCS bot onboarding, which uses its own business verification and agent launch process.

What documents are needed for RCS business verification?

An accepted business verification document — a GST certificate, Certificate of Incorporation or applicable business registration document — that supports your legal business name and business address. If one document does not show both, an additional accepted document is requested for the missing detail. Personal PAN and DLT registration are not required for TXTPro’s RCS onboarding.

Is SMS fallback covered by RCS registration?

No. SMS fallback — sending an SMS when a recipient cannot receive RCS — is a separate SMS service subject to its own DLT requirements: a registered Principal Entity, header and SMS template. RCS bot onboarding does not register you for SMS.

Does RCS work on iPhones?

Apple added RCS support in iOS 18, but availability of RCS Business Messaging on iPhone depends on the market and carrier rollout. Check reachability for your audience before relying on RCS alone.

Who approves RCS agent launch?

RCS agent launch is approved through the relevant RCS platform and network approval process after business and brand verification. TXTPro submits the agent and supports you through verification, but does not approve launches itself and cannot guarantee approval or timelines.

What are the RCS messaging hours in India?

Google’s published business rules for RCS Business Messaging in India allow businesses to initiate conversations between 7:00 AM–10:00 PM IST, seven days a week. Promotional RCS campaigns should follow this window. Promotional agents are also subject to reputation-based limits on messages per user and unique users reached over a rolling 28-day period.

Can RCS OTP or transactional messages be sent 24×7?

Do not assume so. Google’s India rules state the 7:00 AM–10:00 PM IST window for business-initiated conversations and do not publish separate hours for OTP or transactional agents. Confirm the rules for your agent’s use case with your provider before launch.

What happens if an RCS recipient is offline?

The RCS platform accepts the message and keeps trying to deliver it, so it can arrive later. Google deletes undelivered messages 30 days after submission. Set a message expiry or revoke time-sensitive messages, and use SMS fallback where the information must arrive on time.

Are RCS messaging hours the same as SMS sending timings?

No. Businesses can initiate RCS conversations in India between 7:00 AM–10:00 PM IST, seven days a week, under Google’s RCS business rules. Promotional SMS is delivered from 10:00 AM to 9:00 PM IST under TRAI’s regulations and operator Codes of Practice. Fallback SMS follows the SMS rules, including DLT registration; RCS onboarding does not require a DLT PE ID.

How long does RCS agent approval take?

Approval timelines are controlled by the RCS platform and participating networks and can vary. TXTPro helps you prepare complete agent information to avoid avoidable delays.

Talk to us about RCS Business Messaging

Share your use case and expected volume. We will explain onboarding requirements, timelines that depend on third parties, and pricing for your needs.

Prefer to call? +91 90304 02858 · Email info@txtpro.in

Request a demo

Tell us about your messaging requirements. Our team will walk you through the relevant channels, onboarding steps and integration options.