Free for 30 days on Scale.Start free
Run5 steps45 min setup, ongoing zero touch

Inbound lead qualification and routing

A workspace where every inbound lead is scored against your ICP, routed to the right rep in under 15 minutes, and surfaced as a Leads row + Slack ping + Routing log section. Nothing falls through the cracks.

Open in DockSee every step →

A workspace where every inbound lead is scored against your ICP

A workspace where every inbound lead is scored against your ICP, routed to the right rep in under 15 minutes, and surfaced as a Leads row + Slack ping + Routing log section. Nothing falls through the cracks.

Spin up an agent for the heavy lifting

Polls CRM every 15 minutes for status=NEW leads, scores each against ICP via Claude, routes by territory rule (enterprise / SMB / round-robin), flips CRM status to IN_PROGRESS, pings the assigned rep in Slack on Hot + Warm, writes one Leads row. Never edits Hot/Warm/Cold tiers after the rep takes action.

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
  • tableLeads
  • docSetup guide
  • docRouting 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>/inbound-lead-qualification-routing and follow the agent prompt.”

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

Common questions on this template.

How does this handle the case where I have multiple lead sources (forms, demo booking, inbound email)?
The agent treats them uniformly. As long as the lead enters the CRM with hs_lead_status=NEW, the 15-min poll picks it up. Lead Source from the CRM (hs_analytics_source on HubSpot) shows up on the Leads row + Slack alert so the rep knows the channel.
What if my CRM uses a different status name?
Edit fetch_new_leads() in the script. The default queries hs_lead_status=NEW; Salesforce uses Status='Open - Not Contacted'; Pipedrive uses a custom field. The Setup guide doc has the verification query for each CRM.
Can I add more routing rules beyond company size?
Yes. Edit route_lead(). The default routes by territory size (enterprise / SMB / round-robin). Common extensions: route by state, industry, or a custom CRM field. Read the contact's full properties + branch the logic.
What if a lead gets routed wrong?
Manually reassign in the CRM + edit the Leads row's Assigned To. The agent never reverses a routing decision; that's a rep-controlled action. The Status entry will note the manual override if you log it.
Does the agent edit the lead's identity (name, email, company)?
No. The agent only reads identity fields from the CRM. The only field it writes back is hs_lead_status (flipped to IN_PROGRESS so the same lead doesn't fire twice). Everything else lives in Dock.
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.