Real Bots Architecture
Real Bots is the Salesforce-native integration and runtime layer for Real Intelligence. It is delivered as a managed package under the ribot namespace and installed directly into each customer's Salesforce org.
Layers
| Layer | Runs in | Responsibility |
|---|---|---|
| Real Bots managed package | Salesforce | Configuration objects, Apex services, permission sets, admin actions, outbound authentication |
| Public API boundary | Real Intelligence | The single customer-facing entry point for Real Intelligence services |
| Enterprise Intelligence Engine (EIE) | Real Intelligence | Tenant registry, connected systems, credential storage, capability execution |
| Data providers | Customer-owned | Google Workspace, meeting platforms, voice and chat AI platforms |
Capabilities
Real Bots supports three first-class capabilities that share the same package, configuration model, and security model:
- Meeting Automation — meetings, transcripts, Gemini notes, and follow-up activity into Salesforce.
- Relationship Intelligence — organizational relationship signals derived from authorized communication metadata.
- Bot Integration (Voice & Chat) — authorized AI agents reading and acting on Salesforce data.
Tenancy
Every Salesforce organization is registered as a connected system inside a Real Intelligence tenant. The Salesforce Organization ID is the key used to resolve the tenant on every request. Credentials, provider configuration, and signing certificates are stored per tenant, and there is no cross-tenant fallback.
Salesforce Org ID → EIE Tenant → Tenant credentials and providers
Customer-facing endpoint
All Salesforce callouts target the public API boundary:
https://eie-api.realintelligence.com
Backend execution infrastructure is never referenced directly from Salesforce configuration.
Security posture
- Outbound authentication uses asymmetric RS256 assertions signed inside Salesforce.
- No shared static API secret exists between Salesforce and Real Intelligence.
- Provider credentials (for example Google Workspace service accounts) are tenant-specific and encrypted at rest.
See Permissions & Security for the Salesforce-side controls.
Was this helpful?
Last updated 1 month ago