Prepare for client calls using email and CRM context
An agent gathers context before a meeting from calendars, correspondence, CRM records, and public sources. Designed for salespeople and leaders, including B2B sales teams.
How this works
An agent gathers context before a meeting from calendars, correspondence, CRM records, and public sources. Designed for salespeople and leaders, including B2B sales teams.
Prepare a short meeting brief from the current relationship context, not a broad personal dossier. Prioritize the last interaction, open promises and the purpose of this meeting, with public facts included only when they improve preparation.
Before you start
Defined operating scope
Client calls require recent correspondence and CRM context shortly before the meeting.
Required source material
Obtain Upcoming meetings; Emails and messages about attendees; CRM records. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
An attendee cannot be matched confidently. Label their context unavailable instead of merging another person’s history.
Prepare the inputs
- meeting_id
- Required
Calendar event and start time
Resolve timezone, attendees and cancellation status.
- attendee_matches
- Required
Email-to-contact/account mapping
Do not match people by name alone.
- internal_context
- Required
Permitted CRM and correspondence
Include dates and current open commitments.
- public_context
- Required
Relevant public facts with dates
Keep uncertain matches separate.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check meeting_id, attendee_matches, internal_context, public_context before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected meeting_id and any missing required fields.
Find meetings starting in the next few minutes
- Select upcoming events within the requested window and avoid preparing the same event revision twice.
- Verify event time, attendee identity and account match immediately before delivery.
Checkpoint: A saved intermediate result for: Find meetings starting in the next few minutes.
Gather internal context and public information about attendees
- Retrieve the latest relevant correspondence and CRM context, separating attendee facts from assumed organizational roles.
- Check that open commitments remain current and are not already resolved in later correspondence.
Checkpoint: A saved intermediate result for: Gather internal context and public information about attendees.
Prepare a brief and send it to team chat when there is useful information to share
- Summarize meeting purpose, prior agreements, open questions and useful public developments; omit unrelated personal information.
- Verify event time, attendee identity and account match immediately before delivery.
Checkpoint: A saved intermediate result for: Prepare a brief and send it to team chat when there is useful information to share.
Reconcile the proposed result
- Verify event time, attendee identity and account match immediately before delivery.
- Check that open commitments remain current and are not already resolved in later correspondence.
Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.
Package the result and unresolved work
- Verify company and person matches, current commitments, and the relevance of the information.
- Do not enrich with irrelevant private personal information.
Checkpoint: A pre-call brief with context about the client and attendees. Unresolved items remain visible in the review record.
Decisions along the way
An attendee cannot be matched confidently.
Label their context unavailable instead of merging another person’s history.
The event was cancelled or rescheduled.
Update or suppress the prepared brief using the current event version.
The team destination has broader access than the source messages.
Redact restricted context or keep the brief in the permitted workspace.
What you will produce
meeting-preparation-brief-result.json
JSONA pre-call brief with context about the client and attendees. Label proposed and completed states separately.
Include: meeting_id · purpose · attendee_context · open_commitments · questions · source_dates · status · evidence_reference · review_note
meeting-preparation-brief-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving public_context.
Include: source_reference · question · owner · next_action
Check the result
- Verify event time, attendee identity and account match immediately before delivery.
- Check that open commitments remain current and are not already resolved in later correspondence.
- Inspect meeting_id and attendee_matches in both the original and output; confirm that record identity and interpretation survived the transformation.
- Verify company and person matches, current commitments, and the relevance of the information.
When something goes wrong
An attendee cannot be matched confidently.
Label their context unavailable instead of merging another person’s history. Retain the affected evidence and recovery status.
The event was cancelled or rescheduled.
Update or suppress the prepared brief using the current event version. Retain the affected evidence and recovery status.
The team destination has broader access than the source messages.
Redact restricted context or keep the brief in the permitted workspace. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Prepare for client calls using email and CRM context for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Meeting M-8 is with A-3 tomorrow. Last email promised an implementation timeline; CRM lists pricing discussion from an earlier month.
Expected result
Synthetic expected result: Brief leads with the promised implementation timeline and open dependencies. Pricing is historical context, not assumed to be the current meeting objective.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure preparation minutes per call; missing or outdated facts corrected by the owner.
Stop or revise
The team destination has broader access than the source messages. Pause affected records and apply this recovery: Redact restricted context or keep the brief in the permitted workspace.
Keep the scope clear
- Do not enrich with irrelevant private personal information.
- Creating a brief is authorized preparation; posting it follows the user’s selected destination and sharing scope.
Check before using
Verify company and person matches, current commitments, and the relevance of the information.
Business activities
- Run sales conversations and proposals
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Upcoming meetings · Emails and messages about attendees · CRM records
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow