Give the most useful conclusion first.
Resources / Service guidance
Turn RCS ideas into operable message journeys
These frameworks support enterprise RCS aggregation and messaging operations, from rich-message orchestration and SMS fallback to API/webhook integration across brand, product, legal and engineering teams.
Resource library
Practical guidance organized around the delivery workflow
Move from content and journeys to governance, engineering, measurement and shared terminology in one resource library.
Content guide
RCS card framework
Build a scan-friendly hierarchy with title, detail, media and actions.
Read framework →Journey guideSMS fallback design
Choose the conclusion, link, conditions and opt-out that must remain.
Read guide →GovernanceConsent & frequency
Review consent source, purpose, frequency, privacy and opt-out.
View checklist →EngineeringIntegration & webhook
Cover idempotency, signatures, retries, ordering and observability.
View checklist →MeasurementMessage and business metrics
Connect message status, user action, attribution and continuous improvement.
Understand boundaries →GlossaryRCS messaging terms
Align the team on cards, actions, fallback and webhooks.
View terms →01 / Card content
Lead with the conclusion, then add context and action
A phone message is not a smaller landing page. Help the recipient understand what happened, whether it matters now, and what they can do.
- Use one sentence for the object and status
- Add only the timing, location, value or conditions needed
- Never make media the sole carrier of essential information
- Write action labels as verbs, not “click here”
Add the context needed for a decision.
Match the most likely intent.
Keep a necessary alternative available.
A
Extract the conclusion
Decide what must remain if only one sentence survives.
B
Keep a trusted entry point
Use a confirmed link and brand-domain strategy.
C
Include necessary conditions
Retain deadlines, costs, risk or opt-out language.
D
Test SMS independently
Validate length, character set, segmentation and market rules.
02 / SMS fallback
Fallback is not an auto-truncated rich card
Write and approve RCS and SMS separately so the message remains useful without media and buttons.
SMS fallback carries essential conclusions, trusted entry points, sender setup, consent and local rules through purpose-written content.
03 / Consent & governance
Earn appropriate consent before asking for attention
Sending teams coordinate consent, frequency, data and opt-out requirements with legal, privacy and operations stakeholders.
Record consent source
Store when, how and for what purpose a recipient gave consent.
Match the message purpose
Service and marketing messages may require different consent.
Control frequency
Set business caps, quiet hours and priority rules.
Honor opt-out
Make opt-out clear and synchronize it promptly.
Minimize data
Send only what is required to complete the current task.
Confirm by market
Coordinate sender, carrier and applicable rules for each target market.
04 / Integration checklist
Handle duplicates, ordering and temporary failure
Production integration uses authentication, idempotency, signatures, retries, alerts and data-retention controls as operational foundations.
Explore API & webhook workflows →Use a stable business reference or idempotency key and retain enough server-side state for safe deduplication. Define the exact deduplication semantics in the integration configuration.
Validate signatures and timestamps, restrict sources, acknowledge quickly and process asynchronously. Keep secrets and sensitive payloads out of logs.
Use event IDs, occurrence time and valid state transitions to process the business timeline.
05 / Measurement
Separate what happened from why it happened
Message status and actions describe journey activity. Business attribution still needs first-party systems and an appropriate measurement method.
1
Message status
Operational view of requests, routing and events.
2
User action
Context around replies and action events.
3
Business outcome
Evaluated in first-party systems with suitable attribution.
06 / Glossary
Common team language
Business messaging that organizes rich cards, suggested actions and conversation features around market, carrier, device, sender and recipient conditions.
A single card, or a browseable set of cards, combining media, title, detail and actions.
A clear control for opening a link, navigation, calendar or a predefined reply.
Purpose-written SMS content that continues the essential message and action when the rich path is unavailable or unsuitable.
Move from guide to journey
Bring the checklist into the next message review.
Start with one real notification and review content, path, consent and acceptance with brand, product, legal and engineering.