Frame the request
Confirm the latest interaction, participants, stated commitments, and current opportunity state
Sales · Specialized agent role
Sales Follow-up Agent
The Sales Follow-up Agent converts recent conversations and agreed next steps into relevant drafts, reminders, and CRM notes for an opportunity owner to review.
Best for
- Account executives managing many active conversations, demos, evaluations, and stakeholder threads
- Sales teams with a defined follow-up cadence and disciplined opportunity-note expectations
Typical inputs
- Meeting transcript or notes, email thread, opportunity stage, contacts, owners, and recorded next steps
- Approved tone, follow-up timing, content resources, escalation rules, and CRM field requirements
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 decisions, questions, owners, deadlines, and evidence-backed personalization
Prepare the work
Prepare the appropriate follow-up draft and proposed CRM updates
Review and hand off
Request owner approval, then record the approved handoff and monitor due next steps
Actions it can perform
- Summarize conversations, draft recap messages, propose resources, and create next-step reminders
- Prepare CRM notes, surface overdue commitments, detect conflicting dates, and pause closed or sensitive threads
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
- A concise follow-up draft with agreed actions, owners, dates, and relevant approved resources
- CRM-ready activity notes, open-question lists, overdue reminders, and an exception queue
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.
- sales-follow
- converts-recent
- recent-conversations
- agreed-next
- next-steps
- relevant-drafts
- drafts-reminders
- keep-legitimate
- legitimate-sales
- sales-commitments
- commitments-visible
- timely-without
- without-sending
- sending-generic
- generic-nudges
- inventing-promises
- were-never
- never-discussed
- discussed-meeting
- meeting-transcript
- notes-email
- email-thread
- thread-opportunity
- opportunity-stage
- stage-contacts
- recorded-next
- tone-follow
- timing-content
- content-resources
- resources-escalation
- escalation-rules
- field-requirements
- requirements-confirm
- latest-interaction
- interaction-participants
- participants-stated
- stated-commitments
- current-opportunity
- opportunity-state
- state-extract
- extract-decisions
- decisions-questions
- evidence-backed
- backed-personalization
- personalization-prepare
- appropriate-follow
- updates-request
- steps-summarize
- summarize-conversations
- conversations-draft
- draft-recap
- recap-messages
- messages-propose
- propose-resources
- create-next
- next-step
Human approval and escalation
Approval boundary
The opportunity owner approves every external message, changed commitment, commercial statement, stage update, and new deadline before it becomes authoritative.
Escalation rule
Pricing objections, legal or security questions, negative replies, conflicting promises, and executive relationships go directly to the account owner.
What remains under human control
- Sellers choose the follow-up strategy, tone, recipients, timing, resources, and what constitutes a real commitment
- Account owners resolve objections, negotiate terms, change opportunity stages, and decide when a thread should stop
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 product demonstration, the agent extracts the buyer’s questions and agreed evaluation date, drafts a precise recap, and waits for the account executive to approve it.
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.
Sales Call Analysis Agent
See the responsibilities, controls, and handoffs for this related specialist role.
Explore Sales Call Analysis AgentCRM Assistant
See the responsibilities, controls, and handoffs for this related specialist role.
Explore CRM AssistantPipeline 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 Sales Outreach
Understand how this role can contribute to a broader outcome-led workflow.
Explore Automate Sales OutreachAutomate CRM Updates
Understand how this role can contribute to a broader outcome-led workflow.
Explore Automate CRM Updates
Design a responsible Sales Follow-up Agent workflow
Define the sources, controls, connected tools, exceptions, and owners before implementation.