Configure RCS notifications
RCS (Rich Communication Services) delivers media-rich messages to Android devices on supporting carriers. RCS messages can include images, action buttons, and rich formatting that standard Text messages cannot. RCS is the carrier-supported successor to plain SMS for Android.
Closed beta: RCS is currently in closed beta and available to a limited number of users. RCS campaigns are created and published from Marketing > Campaigns > Email/text/whatsapp/rcs — not as a standalone notification-template channel. Contact your Zenoti account manager to request access.
Before you begin
- RCS provisioning must be enabled for your organization. If you cannot find the RCS channel in the notification template editor, RCS is not enabled.
- RCS only delivers to Android devices on RCS-supporting carriers. iOS devices and unsupported Android carriers fall back to standard Text — confirm the fallback behavior with your Zenoti account manager.
- You need administrator access at the organization level to configure RCS templates.
Permission: Edit under Organizations in the Administrator section of the security role (Configuration > Security > Security roles) is required to edit notification templates at the organization level.
Configure an RCS template
- Navigate to Configuration > Notifications.
- Open the template editor.
- Locate the notification type you want to configure for RCS.
- Enable the RCS channel toggle for the template.
- Author the message body. RCS supports formatted text plus optional rich elements:
- Image (header) — a single image displayed at the top of the message.
- Action buttons — quick-reply or URL buttons that the guest can tap.
Important — carrier-driven limits. RCS body length, button counts, and media size are constrained by carrier-specific limits that vary by region and by the RCS aggregator provisioned for your tenant. The exact thresholds for your organization are provisioned at onboarding; to confirm the current values, contact your Customer Success Manager.
- Save the template.
The template follows the standard template-tier hierarchy — base → organization → center.
Fallback to Text
When a recipient device cannot receive RCS (for example, an iOS device or an Android device on a non-RCS carrier), the system falls back to standard Text (SMS) delivery using the same template's Text channel content. Rich elements such as images and action buttons are stripped during fallback; only the plain body text is sent.
Important. Configure the Text channel for every RCS template you create. If the Text channel is not configured for a template, recipients on non-RCS-capable devices will not receive the notification.
Use cases
RCS notifications are commonly used for:
- Promotional campaigns where a hero image and call-to-action button drive engagement.
- Appointment confirmations with a one-tap reschedule action button.
- Loyalty program updates with branded imagery.
Tips
- Always configure the Text channel for the same template as a fallback. Without it, recipients on non-RCS devices receive nothing.
- Test on a real RCS-capable Android device before launching a campaign — emulators do not reliably reflect carrier RCS behavior.
- Keep call-to-action buttons short and action-oriented (Reschedule, Confirm, Cancel) — long button labels are truncated.
- Track RCS-specific delivery rates separately from Text in your campaign analytics; the engagement profile differs.