Sales · Use case
Draft a Follow-Up With Deal Context
Your agent reads the last thread, pulls the opportunity stage and recent activity from the CRM, and drafts a follow-up that sounds like you.
The grind
A good follow-up needs the latest from the deal - and pulling that together by hand is why follow-ups slip.
- Someone re-reads the last email thread to remember where things stand.
- They check the CRM for the opportunity stage and recent activity.
- A follow-up gets written that may or may not sound like the rep.
The context is scattered, so the follow-up is late or generic.
The flow
With fastn, your agent drafts a follow-up with deal context. Your agent writes it; fastn pulls the last thread and the CRM activity so it's grounded in reality.
- Read the last thread. fastn pulls the recent email exchange from Gmail.
- Pull deal context. fastn fetches the opportunity stage and recent activity from Salesforce.
- Your agent drafts the follow-up. With the thread and deal state, the agent writes a follow-up that sounds like you. This is your agent's reasoning, not fastn.
The agent decides what the follow-up says; fastn does the reading across Gmail and Salesforce.
The trigger
This blueprint is agent-invoked: your agent calls the Gmail and Salesforce tools live when it's time to follow up. Through fastn's MCP Gateway these run as governed tools, scoped to each customer's permissions.
The payoff
Follow-ups go out on time and grounded in the deal.
- No re-reading. The thread and deal state are pulled for you.
- Sounds like you. The draft matches your voice and the context.
- Nothing slips. Follow-ups stop falling through the cracks.
Make it yours
Swap Gmail for your email or Salesforce for your CRM - fastn connects to the tools your customers already use, and your agent runs the same flow. Talk to us to see it on your stack.