Sales · Agent family

AI Sales Agent Roles

Explore a coordinated family of AI sales roles for the work between finding an account and handing a well-documented opportunity to a seller.

Get StartedReview the workflow

Best for

  • Revenue teams dividing prospecting, pipeline, and seller-support work into accountable stages
  • Operations leaders who need explicit review points before outreach or customer-record changes

Typical inputs

  • Ideal customer profiles, territories, qualification rules, account lists, and campaign boundaries
  • CRM records, approved message guidance, conversation notes, meeting context, and ownership rules

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.

1

Frame the request

Map the revenue stage and define which sales role owns each handoff

2

Gather context

Collect permitted account, contact, activity, and conversation context

3

Prepare the work

Prepare research, scoring, drafts, alerts, or record updates for the named stage

4

Review and hand off

Route the output to its owner and hold sensitive external actions for review

Actions it can perform

  • Coordinate account research, lead scoring, follow-up preparation, proposal assembly, and pipeline checks
  • Structure CRM notes, surface missing fields, flag stalled deals, and prepare next-step recommendations

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

  • Qualified lead packets, account briefs, follow-up drafts, proposal outlines, and meeting-ready context
  • CRM-ready notes, pipeline exceptions, prioritized work queues, and traceable handoff summaries

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.

  • coordinated-family
  • sales-roles
  • between-finding
  • well-documented
  • documented-opportunity
  • seller-create
  • more-consistent
  • consistent-revenue
  • research-qualification
  • qualification-follow
  • records-arrive
  • scattered-notes
  • notes-ideal
  • ideal-customer
  • customer-profiles
  • profiles-territories
  • territories-qualification
  • qualification-rules
  • rules-account
  • account-lists
  • campaign-boundaries
  • message-guidance
  • guidance-conversation
  • conversation-notes
  • notes-meeting
  • ownership-rules
  • revenue-stage
  • handoff-collect
  • collect-permitted
  • permitted-account
  • account-contact
  • contact-activity
  • prepare-research
  • research-scoring
  • scoring-drafts
  • drafts-alerts
  • record-updates
  • named-stage
  • stage-route
  • hold-sensitive
  • sensitive-external
  • external-actions
  • coordinate-account
  • account-research
  • research-lead
  • lead-scoring
  • scoring-follow
  • preparation-proposal
  • proposal-assembly
  • pipeline-checks
  • checks-structure
  • notes-surface
  • surface-missing
  • missing-fields
  • fields-flag
  • flag-stalled

Human approval and escalation

Approval boundary

People approve outbound messages, commercial terms, ownership changes, and any update that could materially alter a customer or opportunity record.

Escalation rule

Conflicting account data, unclear consent, sensitive conversations, and exceptions to qualification policy go to the responsible seller or sales operations owner.

What remains under human control

  • Sales leadership owns targeting, qualification thresholds, territories, messaging policy, and commercial judgment
  • Account owners decide whether to contact a prospect, change a deal stage, promise terms, or close an opportunity

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.

HubSpotReview integration scopeSalesforceReview integration scopeApolloReview integration scopeGoogle WorkspaceReview integration scope

Example workflow

A revenue operations lead maps research, qualification, and follow-up roles around a target-account campaign; each role contributes a specific artifact before a seller reviews outreach.

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.

SDR Agent

See the responsibilities, controls, and handoffs for this related specialist role.

Explore SDR Agent

Related use cases

Explore outcome-led workflows that can combine this role with approved systems and human review.

Design a responsible AI Sales Agent Roles workflow

Define the sources, controls, connected tools, exceptions, and owners before implementation.

Get Started