RCS Order and Delivery Notifications with Com.Bot

The complete guide

RCS Order and Delivery Notifications with Com.Bot: everything you need to know

What are RCS order and delivery notifications

Short answer: RCS order and delivery notifications are rich, branded messages sent through Google RCS Business Messaging to update customers about a purchase they already made. They arrive in the default messaging app on supported Android phones like Google Messages, with no new app to install, and can include your logo, images, carousels, suggested reply buttons, and read receipts.

RCS order and delivery notifications are rich, branded messages sent through Google RCS Business Messaging (RBM) to update customers about a purchase they already made. Unlike SMS, RCS messages can include your logo, images, carousels, suggested reply buttons, and read receipts. They arrive in the default messaging app on supported Android phones, such as Google Messages, and on other devices where the carrier and device support RCS.

Customers do not need to install a new app. The message looks like a chat from your brand, and they can tap buttons to track a package, confirm a delivery slot, or contact support. so the update still reaches the customer.

For a small business or D2C brand, this means order confirmations, shipping updates, out-for-delivery alerts, and delivery confirmations can look professional and be easier to act on than a plain text message.

• Branded sender with logo and verified badge
• Images, carousels, and rich cards
• Suggested reply and action buttons
• Read receipts to see when a message was opened
• Reach customers on supported Android phones and carriers

Why send order and delivery notifications on Google RCS

Short answer: Sending order and delivery notifications on Google RCS gets updates seen faster because they land in the customer's messaging app, and the verified branded sender reduces fraud concerns around delivery messages. Interactive buttons like Track order or Reschedule delivery turn a one-way alert into a quick action, and Com.Bot manages RCS, WhatsApp, Instagram, and Messenger in one shared inbox.

Customers check messaging apps constantly. An order update that arrives in the same place as their personal chats gets seen faster than an email. RCS adds trust because the sender is verified and branded, so the customer knows the message is from you and not a scam. That matters for delivery updates, which are a common target for fraud.

RCS also gives customers a way to respond. A suggested reply button like "Track order" or "Reschedule delivery" turns a one-way notification into a quick action. If the customer replies, a conversation starts, and your team can help inside the same thread. This reduces support calls and failed delivery attempts.

Com.Bot connects RCS to the rest of your communication stack. The same platform handles WhatsApp, Instagram, Messenger, and a website chat widget, so you can manage all customer conversations in one shared inbox.

• Higher open and response rates than email
• Verified sender reduces phishing concerns
• Interactive buttons cut support back-and-forth
• One platform for RCS, WhatsApp, Instagram, and Messenger
• Check RCS reach before you send

How to set up RCS order and delivery notifications in Com.Bot

Short answer: To set up RCS order and delivery notifications in Com.Bot, create an account, connect your Google RCS channel, and complete agent verification with Com.Bot's help. Then build triggers in the visual drag-and-drop bot builder for order, shipping, out-for-delivery, and delivered events, pulling store or CRM data through the automation builder, and test on a real device before publishing.

Start by creating a Com.Bot account and connecting your Google RCS channel. RCS requires agent verification before launch, and Com.Bot helps you submit the details Google needs, such as your business name, logo, and use case. Once verified, your brand appears as a verified sender in Google Messages.

Next, build the notification flow in the visual drag-and-drop bot builder. You can trigger a message when an order is placed, when a tracking number is generated, when the package is out for delivery, and when it is delivered. Each trigger can pull data from your store or CRM through the automation builder, which supports 1,000+ integrations, webhooks, and API calls.

Then write your message templates. RCS supports rich elements, so you can include an order image, a track button, and a delivery window. Com.Bot lets you test the flow, check how it looks on a device, and publish it. You can also plan how to reach customers whose devices or carriers do not support RCS, for example with a WhatsApp campaign or, in India, a separate SMS campaign.

• Connect and verify your RCS agent
• Build triggers for order, shipping, and delivery events
• Add rich elements like images and buttons
• Test on a real device before publishing
• Check RCS reach for your customer list

RCS order and delivery notifications rules and compliance

Short answer: RCS order and delivery notifications require agent verification before launch and must follow Google's policies. Send utility updates only to customers with an existing transaction, keep promotional content in marketing messages, and use approved templates for business-initiated messages outside the 24-hour window. Com.Bot helps you manage templates and keep utility and marketing messages separate.

RCS Business Messaging has its own rules. Brands need agent verification before launch, and messages must follow Google's policies. You should only send order and delivery updates to customers who have an existing transaction with you. Promotional content belongs in marketing messages, not utility updates.

The 24-hour messaging window applies to RCS conversations in a similar way to other messaging channels. When a customer replies, you can continue the conversation with free-form messages for a period. Outside that window, you need to use approved templates for business-initiated messages. Com.Bot helps you manage templates and stay within the rules.

Never mix promotional offers into a utility notification. If you want to send a discount or a re-engagement message, use a marketing template and make sure the customer opted in. Keeping utility and marketing separate protects your sender reputation and keeps your messages compliant.

• Complete agent verification before launch
• Send utility updates only for existing transactions
• Use approved templates outside the 24-hour window
• Keep marketing and utility messages separate
• Respect opt-in and opt-out requests

Mistakes to avoid with RCS order and delivery notifications

Short answer: Common mistakes with RCS order and delivery notifications include sending an update at every warehouse scan, which causes opt-outs, and labeling marketing content like cart reminders as utility templates, which risks rejection and lowers sender quality. Another mistake is ignoring reach: some customers lack RCS, so plan another way to reach them, such as a WhatsApp campaign or, in India, a separate SMS campaign.

A common mistake is sending too many messages. Customers want to know when an order is confirmed, when it ships, and when it will arrive. They do not need an update at every warehouse scan. Set clear triggers and avoid duplicate notifications, which can feel like spam and lead to opt-outs.

Another mistake is using the wrong template category. Order confirmations and delivery updates are utility messages. Abandoned cart reminders, offers, and back-in-stock alerts are marketing. If you label a cart reminder as utility, you risk rejection and damage your sender quality rating.

Finally, do not ignore reach. Some customers will not have RCS available. If you do not plan another way to reach them, they may miss the update entirely. Com.Bot lets you check which customers RCS can reach and plan how to reach the rest, for example with a WhatsApp campaign or, in India, a separate SMS campaign, so every customer gets the information they need, regardless of device.

• Sending too many updates and causing opt-outs
• Using marketing content in utility templates
• Forgetting to check RCS reach for your customers
• Not testing the message on a real phone
• Ignoring customer replies and leaving them unanswered

Measuring results and costs for RCS order and delivery notifications

Short answer: Measuring RCS order and delivery notification results means tracking delivery, read, and response rates for each notification type, then testing send times, shorter messages, or clearer button labels when rates are low. RCS messaging charges vary by country and carrier, so ask the Com.Bot team for current rates. Com.Bot plans start at $149 per quarter for Silver, with no monthly conversation cap.

Track delivery rate, read rate, and response rate for each notification type. RCS read receipts show when a customer opened the message, which helps you see if the update was seen. If a delivery notification has a low read rate, test a different send time or a shorter message. If a track button gets few taps, check that the link works and the button label is clear.

On cost, Com. RCS messaging charges vary by country and carrier, so ask the Com.Bot team for current rates in your market. You pay for your Com.Bot plan, which starts at $149 per quarter for Silver. That plan includes 1 WhatsApp API channel, 1M contacts, 5 team members, and 20 messages per second. Gold is $349 per quarter and adds more team members, higher limits, and faster support.

There is no monthly conversation cap on Com.Bot. You can send as many notifications as your customers need, and you only pay the platform plan plus the pass-through message costs. For businesses sending high volumes of order and delivery updates, this keeps costs predictable.

• Monitor delivery, read, and response rates
• Test send times and button labels
• Official Meta Business Partner
• Plans start at $149 per quarter
• No monthly conversation cap

Frequently asked questions