Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing zero touch (webhook path) or ~30 sec per call (manual paste)

Post-call CRM update and follow-up agent

A workspace where every sales call from your recording tool flows into the CRM as a meeting note with contact + deal + next steps + stage change, lands a draft follow-up email for the rep to send, and shows up as a Calls row in Dock for the manager.

Open in DockSee every step →

A workspace where every sales call from your recording tool flows into the CRM as a meeting note with contact + deal + next steps + stage change

A workspace where every sales call from your recording tool flows into the CRM as a meeting note with contact + deal + next steps + stage change, lands a draft follow-up email for the rep to send, and shows up as a Calls row in Dock for the manager.

Spin up an agent for the heavy lifting

Catches each Fireflies webhook (or processes pasted transcripts manually), extracts call data via Claude, creates a CRM meeting note tied to the contact and deal, writes one Calls row, appends to Activity log, drafts the follow-up email. Never sends the email without explicit opt-in.

5 steps, 0 official links, 2 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

4Surfaces
5Steps
2Agent prompts
5Tools mapped
Surfaces
  • tableCalls
  • docSetup guide
  • docActivity log
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/post-call-crm-update-agent and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Do I need Fireflies, or can I use Gong / Zoom AI?
Any transcript source works. Fireflies has the cleanest webhook out (recommended). Gong requires admin access to the REST API plus a polling job to find new calls. Zoom AI exports transcripts manually from the Zoom portal. The Setup guide doc has all three paths.
What if the prospect's email is not in the transcript?
Two paths. Pass it as a 2nd CLI argument: python post_call_update.py transcript.txt prospect@company.com. Or set OVERRIDE_EMAIL_TO in .env as the fallback. Either way the contact lookup runs and the meeting note ties to the right CRM record.
Does this send follow-up emails automatically?
Only if AUTO_SEND_EMAIL=true is set in .env. Default is false: the agent generates the draft and writes it to follow_up_draft.txt for the rep to review and send. Flip the flag after the first week once you trust the email quality.
What happens if the deal stage Claude extracted isn't in our CRM?
The script logs the mismatch to Status and skips the stage update (rest of the flow continues). Open run_pipeline_report.py and add the missing display name + internal ID to STAGE_NAME_TO_ID. Run the MCP stage query if you need the IDs.
Can a manager review what got processed each day?
Yes. The Activity log doc surface has a running narrative log: one section per processed call with rep, contact, summary, next steps, and meeting note link. Managers open the doc and walk through the day's activity end-to-end.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.