1. Select a completed call
Choose a fictional scenario. The transcript, proposed CRM changes, risks and coaching output will update together.
2. Review transcript
Inspect the completed meeting transcript before starting the simulated analysis.
3. Simulated analysis
Predefined results demonstrate a consistent governed workflow without using a live AI service.
Governance and production design
The workflow is designed around controlled access, evidence, human approval and auditability.
How this workflow is governed
User consent and transcript access controls
Only approved users and meetings would enter the workflow.
Only approved users and meetings would enter the workflow.
Restricted Google Workspace permissions
Use the minimum scope required to retrieve completed transcripts.
Use the minimum scope required to retrieve completed transcripts.
Human approval before Salesforce changes
No automatic write action would occur without an explicit review decision.
No automatic write action would occur without an explicit review decision.
Evidence attached to every proposal
Field changes remain traceable to specific transcript entries.
Field changes remain traceable to specific transcript entries.
Confidence thresholds
Low confidence suggestions stay outside bulk approval.
Low confidence suggestions stay outside bulk approval.
Field level write permissions
The integration could update only approved objects and fields.
The integration could update only approved objects and fields.
Audit history
Reviews, edits, rejections and applied changes would be recorded.
Reviews, edits, rejections and applied changes would be recorded.
Data retention rules
Transcript and extracted data retention would follow company policy.
Transcript and extracted data retention would follow company policy.
Model output monitoring
Accuracy, overrides and failure patterns would be reviewed over time.
Accuracy, overrides and failure patterns would be reviewed over time.
Clear operating ownership
Sales owns conversation quality, Revenue Operations owns field governance, and IT owns secure access.
Sales owns conversation quality, Revenue Operations owns field governance, and IT owns secure access.
Production architecture
This prototype uses simulated data and predefined results. A production version could use the Google Meet REST API, Google Workspace event subscriptions, a secure server function, a structured large language model response, the Salesforce REST API, and Salesforce OAuth through an External Client App. None of these integrations are active in this demonstration.