| name | rep-context |
| description | Give compact CRM context; not a full deal brief. |
| metadata | {"short-description":"Give sellers fast, relevant CRM context"} |
Rep Context
Outcome
A compact context snapshot that lets the seller orient quickly and choose the right next move.
CRM-neutral operating contract
- Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
- Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
- Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
- Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
- Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.
Workflow
- Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
- Retrieve the minimum authorized evidence needed from the following inputs: Requested entity, current CRM fields, recent interactions, open opportunities, stakeholders, commitments, tasks, service issues, and relevant internal material.
- Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
- Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
- Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.
Analysis rules
- Resolve the exact target and the user's immediate purpose before selecting context.
- Prefer recent, decision-relevant facts over exhaustive record dumps.
- Surface last meaningful interaction, current commercial state, open commitments, relationship owners, risks, and immediate next step.
- Mark stale data, conflicting records, and facts the user may not be authorized to access.
Required output
- Who or what this is
- Why it matters now
- Recent history
- Commercial and relationship state
- Open commitments
- Suggested next move
Actions and boundaries
Read-only by default; route mutations to the relevant update or logging workflow.
