What this follow-up agent handles
Reps miss fast follow-up windows after meetings, stage changes, or inbound form fills. The next action often depends on speed and context, but templates are not enough. The team needs contextual follow-up tied to the CRM record, recent activity, and account state.
This setup is especially useful in three follow-up situations:
- Post-meeting follow-up. After a meeting completes, the agent drafts a follow-up email or creates next-step tasks based on call notes, opportunity stage, and latest tasks.
- Stage-change follow-up. When a lead status or deal stage changes, the agent suggests the next-touch sequence or owner reminder.
- Stale-deal nudge. For opportunities with no recent activity, the agent proposes an internal follow-up task and stakeholder nudges.
How the agent works
The table below shows how CRM events turn into proposed actions and where approval sits in the loop.
| Trigger | Inputs used | Proposed output | Approval |
|---|---|---|---|
| Meeting completed | Call notes, contact record, opportunity stage, latest tasks | Draft follow-up email and next-step task | Approval before send or write |
| Lead status changed | Lead source, owner, segment, prior outreach history | Suggested next-touch sequence or owner reminder | Approval before sequence trigger |
| Deal went stale | Opportunity age, last activity, owner notes | Suggested internal follow-up task and nudges | Approval before write |
How to set up this agent
Clarify which CRM events trigger follow-up proposals and which actions stay read-only.
Describe the message sources the agent can use, such as meeting summaries, notes, stage history, and prior outreach.
Explain the approval model for tasks, email drafts, and CRM updates separately.
Show how operators can reject or adjust a proposed action before it reaches Salesforce or an outbound channel.
Permissions and approval checks
- Read scope should include activity history, notes, stage changes, and the contact or opportunity objects involved.
- Write scope should stay limited to approved task creation, approved field updates, and approved outbound actions.
- If the agent touches email tools, the page should note the additional connection and approval requirements clearly.
- Audit history should record both the proposed follow-up and the final approved action.
Frequently asked questions
Does the agent send messages automatically?
No. By default, the agent drafts follow-up messages and proposes them for review. You approve before the message sends or the task is created.
What CRM events trigger follow-up proposals?
Common triggers include meeting completion, deal stage changes, inbound form fills, email replies, and stale opportunity alerts. You define which events matter and what the next action should be.
Can the agent personalize follow-up based on CRM context?
Yes. The agent reads the contact record, opportunity stage, recent activity, and notes to generate context-aware follow-up. The message includes relevant details from the CRM, not generic templates.
How does this work with Salesforce tasks and sequences?
The agent can propose task creation for internal follow-up or sequence enrollment for outbound campaigns. Both actions go through approval before they execute in Salesforce.