RCS Messaging
RCS campaigns with WhatsApp fallback are under investigation — not available today.
Rich Communication Services (RCS) would let a business send rich, interactive messages — carousels, suggested replies, action buttons, and branded sender identity — through supported carrier messaging apps. A WhatsApp fallback path would route messages to contacts whose devices or carriers do not support RCS. Wavy's backend handles WhatsApp text and template messaging through the Meta Cloud API, but there is no RCS messaging adapter, no Google Business Messages or carrier RCS client, and no automated RCS-to-WhatsApp fallback logic. This page is not indexed because the capability is not live.
What does not exist
Removed from this page because it is not built.
The following capabilities are part of the RCS concept but are not part of any live Wavy offering.
- RCS messaging adapter — There is no adapter, client, or connector that sends or receives RCS messages. No RCS API credentials are stored, no RCS provider is configured, and no outbound RCS send path exists in the backend.
- Carrier and device capability lookup — There is no logic to check whether a contact's carrier supports RCS, whether their device renders rich messages, or whether a fallback to WhatsApp or SMS is needed. No capability-check API call is made.
- Automated WhatsApp fallback — There is no fallback trigger that detects an RCS delivery failure, carrier non-support, or unsupported device and automatically re-sends the message through WhatsApp. No fallback rule exists in the rules engine.
- Rich message templates — There are no RCS rich cards, carousels, suggested replies, action chips, or branded sender templates. The template model covers WhatsApp message templates only.
- RCS campaign delivery state — There is no RCS delivery receipt, read receipt, or carrier status event. The campaign job states apply to WhatsApp sends; no RCS provider event is parsed or stored.
What does exist
The WhatsApp infrastructure that RCS would extend — and why it is not RCS.
Wavy has a messaging architecture built for WhatsApp. RCS would require a separate provider integration that has not been started.
- WhatsApp messaging client — The backend contains a client that sends text and template messages through the Meta Cloud API. This is WhatsApp-specific; RCS uses a different provider surface (for example, Google Business Messages or a carrier-based RCS gateway) that is not integrated.
- WhatsApp template model — Templates are WhatsApp Cloud API templates with language, category, and Meta approval status. There are no RCS rich-card templates or branded message templates. The model does not store RCS-formatted content.
- WhatsApp delivery receipts — Inbound webhook events are parsed for WhatsApp sent, delivered, read, and failed states. No RCS carrier event is handled. The receipt model has no RCS status type.
- Channel model with type field — The channel data model has a type field (default:
whatsapp) that could accommodate non-WhatsApp channels in principle. No RCS channel type has been registered or implemented. - RCS listed as planned on integrations page — The integrations page lists Instagram and RCS messaging as planned additional channels. This is a roadmap item, not a current capability.
The intended path
What RCS with WhatsApp fallback would require if built.
If and when RCS messaging is built, the intended path would add an RCS messaging adapter alongside the existing WhatsApp client, register an RCS channel type in the channel model, create rich-card templates in the template system, and add carrier-capability lookup to determine whether a contact can receive RCS. A fallback rule would detect RCS non-support or delivery failure and re-send through WhatsApp — using the same template and consent state already stored for that contact.
This depends on several external factors that have not been verified: an RCS provider or Google Business Messages API that Wavy can integrate, carrier support for RCS in target markets (particularly India), device-level RCS rendering, and reliable delivery-state reporting from the RCS provider. Because carrier and device coverage is uneven, the WhatsApp fallback path is not a guaranteed parity layer — a contact who cannot receive RCS and has no WhatsApp account on file cannot be reached through either channel. Consent state, template approval, and human review gates that apply to WhatsApp campaigns would apply equally to RCS sends. No RCS send would bypass the workspace consent, suppression, or approval rules already in place.
None of that integration work has been started, and no RCS provider has been selected or tested. This page will be updated and the noindex directive removed only if an RCS messaging path reaches a configuration-dependent state — meaning an RCS adapter exists, the source is workspace-scoped, and it can be enabled with provider setup. Until then, no RCS capability should be assumed.
Dependencies and uncertainty
What must be true before RCS is more than a concept.
RCS is not a single API to integrate. It depends on carrier, device, and provider factors that are outside Wavy's control.
- Provider dependency — An RCS business messaging provider or Google Business Messages API must be available, accept Wavy as a client, and expose send, receive, and status endpoints. No provider has been selected or contracted.
- Carrier and device coverage — RCS support varies by carrier and device. A contact whose carrier or device does not support RCS cannot receive rich messages. The fallback to WhatsApp only helps if the contact has a WhatsApp account on file.
- Delivery-state uncertainty — RCS delivery and read receipts depend on carrier and device support. Some carriers report only a subset of states. The campaign UI would need to surface this uncertainty honestly rather than implying guaranteed delivery.
- Consent and approval parity — RCS campaigns would be subject to the same workspace consent, suppression, template-approval, and human-review rules as WhatsApp campaigns. No RCS send would bypass these gates.
- Human approval gate — As with WhatsApp campaigns, an RCS campaign send would require human approval before dispatch when approval rules are enabled. No RCS campaign would auto-send without review.
- No parity claim — RCS and WhatsApp are different protocols with different capabilities, coverage, and delivery semantics. Wavy does not claim feature parity between the two channels. Rich-card content that renders on one may not render identically on the other.
Questions
RCS messaging — straight answers.
Can I send RCS messages through Wavy today?
No. There is no RCS adapter, RCS messaging client, or RCS-to-WhatsApp fallback path in the backend. The messaging client sends WhatsApp text and template messages only.
What is the WhatsApp fallback?
The concept is that when a contact's carrier or device does not support RCS, the message is automatically re-sent through WhatsApp. This fallback logic has not been built. It would also require the contact to have a WhatsApp account on file — a contact without WhatsApp cannot be reached through either channel.
Does Wavy's Meta integration cover RCS?
No. The WhatsApp client calls the WhatsApp Cloud API. RCS uses a different provider surface — such as Google Business Messages or a carrier-based RCS gateway — which is not integrated. No RCS provider has been selected or tested.
Can I at least create RCS rich-card templates?
No. The template model covers WhatsApp Cloud API templates with language, category, and Meta approval status. There are no RCS rich-card, carousel, or suggested-reply templates in the system.
Is RCS supported in India?
RCS carrier and device support varies and is outside Wavy's control. We have not verified carrier coverage in any target market. The fallback to WhatsApp only helps if the contact has a WhatsApp account on file. This uncertainty is part of why the capability is labelled Investigate, not Planned.
Will RCS campaigns need human approval?
Yes. When built, RCS campaigns would be subject to the same workspace consent, suppression, template-approval, and human-review rules as WhatsApp campaigns. No RCS send would bypass these gates or auto-send without review when approval is enabled.
Will RCS messaging be added in the future?
It is under investigation. It depends on an RCS provider being available and integrated, carrier and device coverage in target markets, and reliable delivery-state reporting. This page will be updated and the noindex directive removed only if an RCS path reaches a configuration-dependent state — an adapter exists, is workspace-scoped, and can be enabled with provider setup.
RCS messaging is under investigation, not shipped.
Explore Wavy's available WhatsApp messaging, automation, and campaign capabilities today. When an RCS path is built, this page will say so plainly.