Frame the request
Match the source activity to the correct contact, account, and opportunity records
Sales · Specialized agent role
CRM Assistant
The CRM Assistant turns permitted sales activity into structured notes and proposed field updates while preserving ownership, source context, and change review.
Best for
- Revenue teams that need reliable activity capture after calls, emails, meetings, and handoffs
- Sales operations groups with documented field definitions, source precedence, and validation rules
Typical inputs
- CRM schema, field definitions, required stages, owners, validation rules, and duplicate policy
- Approved email, meeting, call, form, and task context linked to a known account or contact
Input quality determines output quality. Source permissions, retention, and field-level access should be settled before the workflow begins.
Core workflow
Each stage has a defined purpose, visible evidence, and a named owner for exceptions.
Gather context
Extract only supported facts and map them to configured CRM fields
Prepare the work
Compare proposed values with existing data and identify conflicts or missing evidence
Review and hand off
Submit low-risk notes or review-gated changes with a clear before-and-after record
Actions it can perform
- Prepare activity notes, normalize fields, associate records, identify missing values, and create follow-up tasks
- Detect possible duplicates, stale ownership, conflicting stages, unsupported forecasts, and ambiguous entity matches
Actions should be restricted to the systems, records, and channels required for this role. Broader access is not a substitute for a well-designed workflow.
Outputs
- CRM-ready notes, proposed field changes, relationship links, tasks, and source references
- Conflict reports, missing-field queues, duplicate candidates, and change logs for sales operations
Every output should make its status clear: prepared, awaiting approval, completed under policy, or escalated with an explanation.
Role-specific configuration details
Use these role-specific terms to make the implementation brief concrete: resolve the relevant definitions, permissions, routes, and exception conditions before the role touches live work.
- assistant-turns
- turns-permitted
- permitted-sales
- sales-activity
- structured-notes
- proposed-field
- field-updates
- preserving-ownership
- consistency-without
- without-silently
- silently-overwriting
- overwriting-authoritative
- authoritative-customer
- customer-opportunity
- opportunity-ownership
- forecast-information
- schema-field
- field-definitions
- definitions-required
- required-stages
- validation-rules
- duplicate-policy
- email-meeting
- meeting-call
- call-form
- known-account
- contact-match
- correct-contact
- contact-account
- opportunity-records
- records-extract
- extract-only
- only-supported
- supported-facts
- fields-compare
- compare-proposed
- proposed-values
- existing-data
- identify-conflicts
- missing-evidence
- evidence-submit
- risk-notes
- gated-changes
- clear-before
- after-record
- record-prepare
- prepare-activity
- activity-notes
- notes-normalize
- normalize-fields
- fields-associate
- associate-records
- records-identify
- identify-missing
- missing-values
- create-follow
Human approval and escalation
Approval boundary
People approve ownership, lifecycle stage, forecast, amount, close date, deletion, merge, and other material changes to authoritative records.
Escalation rule
Ambiguous matches, inconsistent source data, strategic accounts, restricted fields, and updates that affect reporting go to the record owner.
What remains under human control
- Revenue operations defines the CRM schema, field authority, validation, duplicate handling, and write permissions
- Record owners approve consequential changes and decide how conversation context affects qualification, forecast, and strategy
Teams should review permissions and outcomes over time, especially when policies, data sources, responsibilities, or customer expectations change.
Recommended integrations
Connections are workflow building blocks, not proof of automatic availability. Confirm authentication, permissions, supported actions, and error handling during implementation.
Example workflow
After a discovery call, the agent matches the participants, drafts a factual activity note, proposes next-step fields, and flags a conflicting close date for the seller.
The implementation should record the source, owner, decision boundary, and recovery route for each important stage. That makes the workflow easier to review and improve without hiding responsibility.
Related agents
Use related roles only when responsibility and handoff boundaries are genuinely distinct.
CRM Data Cleanup Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore CRM Data Cleanup AgentSales Call Analysis Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Sales Call Analysis AgentPipeline Monitoring Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Pipeline Monitoring AgentRelated use cases
Explore outcome-led workflows that can combine this role with approved systems and human review.
Automate CRM Updates
Understand how this role can contribute to a broader outcome-led workflow.
Explore Automate CRM UpdatesAutomate Reporting
Understand how this role can contribute to a broader outcome-led workflow.
Explore Automate Reporting
Design a responsible CRM Assistant workflow
Define the sources, controls, connected tools, exceptions, and owners before implementation.