Claude Managed Agents · Inbound · Walkthrough + Playbook

Claude Managed Agents for Inbound Sales: Interactive Walkthrough & Playbook

Replace the "fill out the form and wait three days" inbound queue with a buying agent that answers, qualifies and recommends a plan in minutes, then hands complex deals to a rep with the full conversation attached. Click through the build, then take the operator playbook.

Claude Managed Agents HubSpot Salesforce Slack

Based on Anthropic's How Anthropic's sales team rebuilt inbound with Claude Managed Agents. Walkthrough screens are an illustrative JayOh recreation with fictional data, not the live product.

What you'll learn

Inbound that answers in seconds, not days

01

Where the form-and-queue model breaks and which inbound questions an agent should own outright.

02

The three endings every buying-agent conversation should have: checkout, a rep, or an answer.

03

What you build vs. what Managed Agents runs: prompt, knowledge base and tools on your side; loop, sessions, hosting and versions on theirs.

04

How JayOh wires it into HubSpot or Salesforce so every hand-off lands as a qualified, routed, measurable lead.

Interactive walkthrough · 10 steps · ~6 min

Watch the buying agent work, end to end

Use Next / Back or your arrow keys. Orange boxes point to what matters on each screen. Illustrative recreation with fictional companies (Brightline Software and its buyers).

Illustrative mockup · fictional data

Tip: tap the expand button (top right of the guide) and turn your phone sideways for the full screen.

The JayOh playbook

The play: an AI buying agent in front of your inbound queue

Put a Claude Managed Agents buying agent on your pricing page, contact-sales page, product and emails. It answers pricing, security and fit questions immediately, qualifies the buyer, recommends the right plan and seat count, and ends every conversation in one of three ways: self-serve checkout, a hand-off to a rep with the full transcript and the reason, or a quick answer. The outcome: speed-to-lead measured in seconds, reps who only work educated buyers, and a CRM record for every conversation instead of a queue nobody clears. It's the agent version of our speed-to-lead work.

Who owns it

Head of Sales Development or RevOps owns outcomes and the prompt. One engineer owns the code and tools. Sales and content leads edit the prompt and knowledge base. Sales leadership owns the escalation rules.

Systems involved

Claude Managed Agents (beta) + Claude Console, your website chat widget, CRM (HubSpot or Salesforce) for leads and routing, billing/checkout (e.g. Stripe or HubSpot Commerce), Slack for rep alerts.

Prerequisites

Claude API org with Managed Agents access, an approved pricing & security answer set (each answer with a source), a clean lead object with owner routing, a checkout or quote path that works without a human, and a defined escalation policy.

Step-by-step setup

  1. Write the goal, not a flowchart.In Claude Console, create the agent and give it a one-paragraph goal: understand what the buyer is solving, qualify, recommend the best-fit plan, and hand off when a human changes the outcome. Done = prompt under ~40 lines, no qualification decision trees.
  2. Build the knowledge base from approved answers.Pull pricing, seat minimums, billing terms, security/compliance and plan comparisons into one source set. Every answer cites its source doc. Done = top 25 inbound questions from the last 90 days each map to an approved answer.
  3. Define four tools.recommend_plan, show_proposal, send_to_checkout, handoff_to_rep. The hand-off tool requires a reason, a summary and the transcript. Done = each tool returns real data from your pricing and CRM APIs in staging.
  4. Connect the hand-off to the CRM.The hand-off creates or updates the contact + lead in HubSpot or Salesforce, writes the summary, plan interest, seat count and escalation reason to properties, and routes to an owner with a task. Done = a test hand-off appears in the CRM with owner, task and properties in under 60 seconds.
  5. Deploy on the pages where buyers already ask.Pricing and contact-sales pages first, then in-product and email. Keep it opt-in: the buyer picks agent or rep. Done = both paths work and both create CRM records.
  6. Run staging before production, always.Every prompt change goes to the staging agent first; SMEs test it, then you point production sessions at the new version. Keep the previous version ready to roll back. Done = a written release checklist and a named approver.
  7. Review escalation reasons weekly.Export sessions, tally hand-off reasons, and split them into "a rep is the right answer" vs. "self-serve gap we can fix." Fix the top gap every sprint. Done = a weekly 30-minute review with one shipped fix.

How JayOh runs it for clients

We treat the agent as a new lead source with an SLA, not a website widget. In HubSpot we add properties for Agent conversation ID, Agent outcome, Escalation reason, Recommended plan and Recommended seats, a lead source value of "Buying agent", round-robin or territory routing on hand-off, and a one-business-hour follow-up task. In Salesforce the same fields live on Lead with an assignment rule and a Flow for the task. Guardrails: the agent can quote list price only, discounts and non-standard terms always escalate, regulated or legal questions cite the source or escalate, and every session is logged. QA: 20 scripted buyer personas run against staging before each release, plus a weekly sample of 25 live transcripts scored for accuracy and plan fit.

MetricTypeWeakAcceptableStrong
Time to first answerLeading> 1 hour< 5 min< 1 min, 24/7
Hand-offs worked within SLA (1 business hour)Leading< 60%60–85%> 85%
Share of conversations escalated to a repLeading> 40%20–40%< 20% and falling
Answer accuracy on weekly transcript sampleLeading< 90%90–97%> 97%
Hand-off lead → opportunity rate vs. old form leadsLagging≤ 1x1.3–2x> 2x
Sales cycle on agent-assisted deals vs. baselineLaggingNo change2–4 days faster5+ days faster

Ranges are JayOh working benchmarks for B2B SaaS inbound, set against the improvements Anthropic reports (2x+ conversion to opportunity, ~5 days faster close). Calibrate to your own baseline in the first 30 days.

Building more agent plays on your CRM? See the HubSpot Agent Playbook, the AI-enabled SDR model and the AI agent governance guide.

Common mistakes / what good looks like

Where teams get the buying agent wrong

Rules instead of a goal

A 400-line prompt that encodes every BANT branch. It gets brittle, contradicts itself and still escalates the easy stuff.

A clear goal + good knowledge

One goal paragraph, sourced answers, and four tools. Iterate weekly from transcripts.

Hand-offs that drop context

The rep gets an email address and "wants to talk to sales," then re-asks every question the buyer already answered.

Hand-offs that carry the conversation

Summary, plan, seats, reason and transcript are written to CRM properties, with an owner and a 1-hour task.

Upselling by default

Pushing every buyer to Enterprise. Small teams churn or stall in procurement they didn't need.

Right plan, every time

The agent recommends the plan that fits. Buyers who land on the right plan stay longer.

Shipping prompt edits straight to prod

A well-meaning wording change breaks pricing answers for a weekend.

Staging, versions, rollback

Every change is a version, tested in staging by SMEs, promoted on purpose, and reversible in one click.

FAQ

Claude Managed Agents for inbound: common questions

What is a buying agent built on Claude Managed Agents?

It's a Claude-powered agent that sits where buyers already ask questions (pricing page, contact-sales page, product, email), answers pricing, security and fit questions, recommends a plan and seat count, and ends in checkout, a rep hand-off with full context, or a quick answer. Managed Agents hosts it and runs the agent loop, sessions and versioning.

Does a buying agent replace SDRs or BDRs?

No. It removes the queue work: answering questions the docs already cover and chasing buyers for basics. Reps spend their time on hand-offs where a person changes the outcome, plus events and earlier-stage education.

What do we actually have to build?

Three things: the prompt (a goal, not a rulebook), a sourced knowledge base of approved answers, and a handful of tools such as recommend plan, show proposal, send to checkout and hand off to a rep. Managed Agents runs the loop, sessions, hosting, Console and versions.

How does the hand-off reach our CRM?

The hand-off tool calls your CRM API: it creates or updates the contact and lead, writes the summary, recommended plan, seats and escalation reason to properties, assigns an owner and creates a follow-up task. JayOh builds this for HubSpot and Salesforce.

How should we measure whether it's working?

Leading: time to first answer, escalation share, hand-offs worked within SLA and answer accuracy. Lagging: hand-off lead-to-opportunity rate vs. old form leads and sales-cycle length on agent-assisted deals.

How long does it take to launch?

Anthropic reports one engineer built the first version in a few weeks. With JayOh, plan on a 30-day pilot: week 1 knowledge base and tools, week 2 CRM hand-off and staging, week 3 opt-in launch on the pricing page, week 4 readout.

Your next step

Want this running in your revenue team?

JayOh designs the agent, wires the hand-off into HubSpot or Salesforce, and runs the 30-day pilot with you.

Talk to JayOh