Sales · Call preparation
Meeting preparation and follow-up
Turn calendar, CRM, and conversation context into a meeting brief and follow-up, while the account executive controls every external message and CRM change.
Illustrative product view
run_meeting_prep_01
A calendar meeting enters its configured preparation window.
Trigger captured
Context is assembled
Evidence attached
Brief and follow-up are drafted
Evidence attached
Human decision required
Terminal approval step
The operating problem
Where the process breaks.
Critical account context is spread across calendars, email threads, CRM records, and prior calls. Reps lose preparation time before the meeting and momentum afterward when notes and follow-up sit unfinished.
Governed execution
How the work runs.
Order remains explicit from trigger to decision. Every step runs inside the tools, data scope, and policy assigned to this workflow.
- 01Trigger
Meeting window opens
The calendar event supplies the account, attendees, owner, and preparation deadline.
- 02Agent
Context is assembled
The agent retrieves permitted CRM history, recent email, open tasks, and relevant knowledge.
- 03Agent
Brief and follow-up are drafted
The agent produces a source-linked brief before the call and proposed follow-up and CRM changes afterward.
- 04Human
Rep reviews the actions
The account executive edits or approves the external message and every proposed CRM field change as the terminal workflow step.
Decision boundary
Human approval is the boundary.
The approval node is terminal today. A post-approval send or write happens only through a separate manual or newly triggered continuation.
Required decision
The account executive approves the follow-up and each proposed CRM field change; a configured send or write requires a separate manual or newly triggered continuation.
Approval recorded
Actor, decision, edits, and timestamp join the receipt.
Separate continuation
External write
Nothing resumes silently after the human decision.
Proof of execution
Execution receipt.
The output is not just a result. It carries the trigger, evidence, proposed actions, decision, and final workflow state.
Illustrative receipt
sample · run_meeting_prep_01
- Calendar trigger and meeting identifier
- captured · evidence_01
- Sources retrieved and access scope
- captured · evidence_02
- Draft versions and model configuration
- captured · evidence_03
- Rep approval, edits, and timestamp
- captured · evidence_04
- Rep decision and continuation status
- approved · continuation_not_started
Output · A meeting brief, proposed follow-up and CRM changes, and the rep’s decision receipt.
Connected work
Example systems in this workflow
These are illustrative system choices, not a claim that every one is a native connector. Configure supported native tools, MCP servers, OpenAPI imports, or approved HTTP tools for your environment.
Deployment boundary
Run the workflow in Zilionix Cloud, inside your VPC, or through the self-hosted deployment path while keeping organization-scoped data and credentials inside the selected boundary.
Zilionix Cloud
Your VPC
Self-hosted
Policy before autonomy
Guardrails for this run.
Read and write permissions are scoped independently by tool and workspace role.
External messages and CRM writes require explicit rep approval and a separate continuation.
Retrieved context and tool results are attached to the execution trace.
Sensitive fields can be excluded before model context is assembled.
External evidence
Benchmark the opportunity.
This source illustrates the surrounding business problem. It is not a Zilionix deployment, customer result, or performance guarantee.
Bring this workflow into view.
Map the trigger, tools, approval boundary, and execution receipt against the way your team already works.