Multi-Channel Messaging
One orchestration engine. Every communication channel. All data in Salesforce.
Channels
| Channel | Status | Typical use |
|---|---|---|
| GA | Transactional, service, operational, statements | |
| SMS | GA | Alerts, OTP, appointment reminders |
| RCS | GA | Branded rich messaging with verified sender |
| GA | International customer conversations | |
| Voice | GA | AI voice calls, outbound IVR, voicemail drop |
| Push | GA | Mobile and Salesforce mobile app notifications |
| Microsoft Teams / Slack | Preview | Internal escalation and operational alerts |
| Future channels | Roadmap | Pluggable channel adapters |
One request, many channels
The same message request can target any channel. Channel selection can be explicit, or delegated to Intelligent Routing.
RME_Message.builder()
.channels(new List<String>{ 'SMS', 'EMAIL' }) // ordered preference
.strategy('FIRST_REACHABLE') // or ALL, LEAST_COST
.templateName('Appointment_Reminder')
.toContact(contactId)
.send();
Unified communication history
Regardless of channel, every message produces the same record shape: a Message__c parent with channel-specific detail, Delivery_Status__c children, and normalized events. Reporting, AI, and audit never need channel-specific logic.
Consent per channel
Consent is stored per channel and per purpose. An SMS opt-out never silently suppresses transactional email, and a marketing email opt-out never blocks a security alert. See Consent Management.
Continue to Enterprise Email.
Was this helpful?
Last updated 1 month ago