| name | inbox-sweep |
| description | Triage authorized sales email; never act without approval. |
| metadata | {"short-description":"Triage customer email and open commitments"} |
Inbox Sweep
Outcome
A prioritized inbox view linking customer messages to CRM context and concrete next actions.
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: Authorized messages in the requested scope, sender and recipient identities, timestamps, threads, CRM people and organizations, opportunities, tasks, and service records.
- 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
- Respect the requested mailbox, folder, label, and time window and avoid unrelated personal messages.
- Resolve senders conservatively and show ambiguous CRM matches.
- Prioritize explicit commitments, deadlines, customer blockers, commercial or legal issues, renewal risk, and unanswered requests.
- Deduplicate threads, preserve the latest state, and distinguish informational mail from action required.
Required output
- Inbox headline
- Priority message queue
- CRM context and reason
- Required action and deadline
- Draft replies when useful
- Unmatched or ambiguous items
Actions and boundaries
Do not send, archive, label, delete, or log messages until the user approves the exact actions.