Platform & Architecture
iDialogue connects Salesforce records and Files to selected AI and processing services through an agentic layer of configured agents, skills, tools, workflows, and governance.
The architecture exists to produce two practical outcomes: generate Documents and Experiences, or understand files through Image OCR, File Extraction, Contract Summaries, and Document Q&A.
Minimal architecture
This illustration shows a common OpenAI-enabled path. Salesforce records and Files provide selected business context. The iDialogue Agentic Layer applies configured skills, tools, workflows, and review before producing Generative AI or IDP outcomes. Other providers can participate when a Connection and workflow enable them.
Architecture layers
Salesforce Records + Files
Account, contact, opportunity, quote, product, custom-object, and ContentVersion context stays connected to the business process that owns the work.
Selected AI and processing services
Configured providers can supply reasoning, image, file-understanding, communication, research, or other capabilities appropriate to the agent and task. A service listed in the Connections catalog is not necessarily configured or used for a particular customer.
iDialogue Agentic Layer
Agents combine instructions, skills, tools, workflows, permissions, lifecycle controls, and human-review points.
Generative AI
Documents and Experiences turn Salesforce context into approved business content and customer-facing outcomes.
Intelligent Document Processing
Image OCR, File Extraction, Contract Summaries, and Document Q&A turn existing content into usable context and configured actions.
Operational model
- Real-time guided work and background file/document processing use the appropriate execution path.
- The configured Salesforce or external-service identity, input context, active skills, enabled tools, and workflow settings jointly bound what an agent can read or change.
- Templates, source context, review, and workflow rules keep outputs aligned with the intended business process.
- The architecture complements Salesforce, CPQ, Revenue Cloud, and other systems of record rather than replacing their pricing, billing, tax, ERP, order, invoicing, or revenue-recognition responsibilities.