Real Messaging Engine

Roadmap

Directional, not contractual. Dates and sequencing may change.

Now — shipped

  • Email, SMS, RCS, WhatsApp, Voice, and Push channels
  • SendGrid, Amazon SES, Azure ACS, Mailgun, Postmark, SparkPost adapters
  • Intelligent routing, failover, retry, and suppression
  • Consent management with per-channel and per-category scope
  • Flow actions, Invocable Apex, REST API, Platform Events, webhooks
  • Delivery analytics and packaged reports and dashboards

Next — in development

ItemDescription
Microsoft Teams and Slack channelsInternal escalation and operational alerts as first-class channels
Conversation threadingUnified inbound/outbound thread view across channels
Template approval workflowNative approval process with diff view between versions
Predictive send time (GA)EIE-driven OPTIMAL scheduling out of pilot
Cost analyticsPer-message and per-campaign spend by provider and channel
Inbound email parsing v2Structured extraction into Case and Opportunity fields

Later — planned

  • Provider marketplace with community adapters
  • Journey primitives for multi-step operational sequences
  • Real-time deliverability advisor with corrective actions
  • BIMI onboarding assistant
  • Data Cloud activation for RME communication history
  • Multi-org routing for federated enterprises

Adjacent packages

RME is one pillar of the Real Intelligence documentation ecosystem. Planned sibling spaces follow this same structure:

Enterprise Intelligence Engine · AVA Enterprise Intelligence · Relationship Intelligence · Meeting Intelligence · Voice Intelligence · Building Intelligence · Operations Intelligence · Schema Intelligence

Requesting a feature

Open a request through your Real Intelligence account team with the business outcome, expected volume, and affected channels. Roadmap prioritization weighs enterprise impact, compliance need, and platform leverage.

Continue to Release Notes.

Was this helpful?

Last updated 1 month ago