Sales · Specialized agent role

SDR Agent

The SDR Agent prepares a controlled outbound workflow around researched accounts, message guidance, follow-up timing, reply handling, and qualified seller handoffs.

Get StartedReview the workflow

Best for

  • Sales development teams with approved segments, sequences, value propositions, and suppression rules
  • Founders or sellers who need research-backed drafts and organized follow-through rather than autonomous blasting

Typical inputs

  • Approved account and contact queue, research notes, persona, campaign purpose, and suppression list
  • Message framework, evidence-approved claims, cadence, channel rules, reply taxonomy, and handoff criteria

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

Confirm the prospect, campaign eligibility, source context, and current CRM ownership

2

Gather context

Research role-relevant triggers and select only supportable personalization facts

3

Prepare the work

Prepare outreach and follow-up drafts within the approved sequence and tone

4

Review and hand off

Classify replies and route interest, objections, opt-outs, or sensitive responses appropriately

Actions it can perform

  • Assemble account context, draft personalized messages, schedule review queues, and prepare follow-up variants
  • Identify positive replies, objections, referrals, out-of-office messages, opt-outs, and ambiguous intent

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

  • Research briefs, review-ready outreach drafts, follow-up queues, and a record of personalization sources
  • Reply classifications, opt-out records, objection summaries, and qualified meeting handoff packets

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.

  • controlled-outbound
  • around-researched
  • researched-accounts
  • accounts-message
  • message-guidance
  • guidance-follow
  • timing-reply
  • reply-handling
  • qualified-seller
  • seller-handoffs
  • handoffs-reduce
  • reduce-repetitive
  • repetitive-sales
  • sales-development
  • development-preparation
  • keeping-targeting
  • targeting-sending
  • sending-relationship
  • relationship-judgment
  • meeting-commitments
  • contact-queue
  • queue-research
  • research-notes
  • notes-persona
  • persona-campaign
  • campaign-purpose
  • suppression-list
  • list-message
  • message-framework
  • framework-evidence
  • claims-cadence
  • cadence-channel
  • channel-rules
  • rules-reply
  • reply-taxonomy
  • handoff-criteria
  • criteria-confirm
  • prospect-campaign
  • campaign-eligibility
  • ownership-research
  • relevant-triggers
  • select-only
  • only-supportable
  • supportable-personalization
  • personalization-facts
  • facts-prepare
  • prepare-outreach
  • drafts-within
  • tone-classify
  • classify-replies
  • route-interest
  • interest-objections
  • sensitive-responses
  • responses-appropriately
  • appropriately-assemble
  • assemble-account

Human approval and escalation

Approval boundary

People approve target lists, first-touch messages, sensitive follow-ups, sequence changes, and any external send unless a clearly authorized policy says otherwise.

Escalation rule

Opt-outs, complaints, legal questions, existing relationships, strategic accounts, and unclear replies go to the campaign owner without further contact.

What remains under human control

  • Sales leaders own audience, claims, channel policy, cadence, suppression, and acceptable personalization
  • Sellers approve relationship-sensitive outreach, handle nuanced objections, and make every commercial commitment

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.

ApolloReview integration scopeGmailReview integration scopeHubSpotReview integration scopeSalesforceReview integration scope

Example workflow

Before an event, the agent prepares source-backed messages for approved accounts, places them in a review queue, then routes interested replies with context to the assigned 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.

Related use cases

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

Questions about this role

Can this role send outreach without review?

Only if a customer explicitly configures and authorizes a bounded sending policy; sensitive or uncertain messages should remain approval-gated.

Design a responsible SDR Agent workflow

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

Get Started