AI Sales Automation Setup Guide: How to Use Claude as Your Sales Agent
You want Claude to handle your inbound leads — qualify them, follow up, and book the call — without you sitting in the conversation for every enquiry. This guide shows you exactly how to set that up.
No coding required. No custom API. Just a structured system prompt, a clear handoff rule, and the right connection between Claude and your inbound channel.
Most guides on AI sales automation are written for enterprise sales teams with dedicated reps, a RevOps function, and a stack of tools to integrate. If you’re running a professional service business with a small team — or you are the sales function — those guides don’t apply to you. This one does.
What AI Sales Automation Means for a Service Business
For an enterprise sales team, AI sales automation means routing leads between reps, enriching CRM records, and generating pipeline forecasts.
For a founder-led service business, it means something more specific: replacing the manual work of reading an enquiry, deciding if it’s worth your time, following up, and booking a call. Four tasks. Claude can handle all of them.
The difference between a service business that has made this work and one still doing it manually isn’t technology — it’s the quality of the setup. McKinsey’s 2025 State of AI survey found that only 29 percent of companies with revenues under $100 million have scaled AI beyond pilots, compared with nearly half of companies above $5 billion [1]. The gap isn’t budget. It’s workflow design.
This guide closes that gap for the sales function specifically.
Why Most Founders Set Claude Up Wrong
Most founders who try to use Claude for sales make the same mistake: they use it as a chatbot, not an agent.
A chatbot waits to be asked. An agent runs a process.
When Claude is a chatbot, it answers questions when leads reach out to you. When Claude is a sales agent, it reads every new inbound lead, scores it against your qualification criteria, sends the first qualifying question, waits for a response, categorises the outcome, and either books a call or closes the thread — all without you touching it.
The difference is entirely in the system prompt.
Every article ranking for “AI sales automation” right now talks about which enterprise platforms to evaluate. None of them explain how to write the instruction set that turns Claude from a general-purpose assistant into a process that runs itself. That’s what the next four steps cover.
For a deeper look at how the qualification agent specifically works, see how to build a Claude AI agent for sales qualification. This guide focuses on the full setup — from system prompt to CRM connection to handoff logic.
Step 1 — Map Your Sales Process Before You Open Claude
Before you write a single word of a system prompt, define five things.
Your ideal client. Be specific. Not “small businesses” — “accounting firms with 5–20 staff in the US who need monthly bookkeeping.”
Your qualification criteria. Three to five yes/no questions that tell you whether a lead is worth a call. Examples: minimum project budget, decision-making authority, service timeline.
Your hard disqualifiers. Anything that’s an immediate no — budget below your minimum, wrong industry, wrong geography.
The one next step for a qualified lead. Do they book a 30-minute call? Fill in a short intake form? Define exactly one.
Your tone. Direct, warm, formal? Match it to how you’d personally write to a new enquiry.
This takes 20 minutes. Without it, any Claude setup produces generic, off-brand responses that don’t convert. The output of this step is a one-page reference document — decisions on paper, not a workflow yet.
If you’re not clear on what an agentic sales system actually is and how the qualification layer fits into a broader conversion infrastructure, that’s worth reading before you build anything.
Step 2 — Write Your Sales Agent System Prompt
The system prompt is Claude’s job description. It tells Claude who it is, what it knows, and exactly how to behave in every scenario.
Here’s the architecture.
Role definition: “You are the sales agent for [Business Name]. Your job is to receive inbound enquiries, qualify them against our criteria, and either book a discovery call or explain why the enquiry isn’t a fit.”
ICP and criteria: List your ideal client profile and your three to five qualification questions exactly as they should appear in the conversation.
Response rules: Maximum two questions per message. What to do if a lead doesn’t reply after 48 hours. How to handle a price objection.
Handoff triggers: “If the lead has answered YES to three or more of the five qualifying criteria, send the Calendly booking link with a one-sentence warm note. If fewer than three, send a short close message and end the thread.”
Tone and style: “Write in first person as if from [Your Name]. Keep it warm and direct. No corporate language. Short paragraphs.”
The system prompt doesn’t need to be long — it needs to be specific. Two hundred words of precise instruction outperforms two thousand words of vague guidance.
Step 3 — Connect Claude to Your Inbound Channel
Claude needs a way to receive new leads automatically. The right connection depends on where enquiries first arrive.
Email: Route new enquiry emails to Claude via Claude Cowork’s email integration. Claude reads the email, runs the qualification logic, and replies from your address.
Web form: Connect your enquiry form to Claude through Zapier or Make. Each new form submission triggers Claude to send the first qualifying question within minutes.
HubSpot connector: Anthropic’s Claude for Small Business package includes a direct HubSpot integration that handles lead triage and pipeline visibility inside Claude [2]. If your leads arrive through a HubSpot form, this is the most direct path.
The output is the same regardless of channel: Claude receives the lead, processes it against your system prompt, and either moves it forward or closes it out. Test with five to ten sample enquiries before going live.
The full picture of how this fits into a connected sales infrastructure is covered in the sales automation guide for professional services. For connecting Claude directly to your CRM, a full walkthrough is coming soon.
Step 4 — Set the Handoff Logic
Handoff logic tells Claude exactly when to handle the conversation itself and when to involve you.
Two triggers cover most service businesses.
Trigger 1 — Qualified: The lead has hit your qualification threshold and responded positively to the booking prompt. Claude sends the booking link. You show up to the call.
Trigger 2 — Disqualified: The lead is below budget, wrong geography, or wrong service type. Claude sends an honest close — “Based on what you’ve shared, I don’t think we’re the right fit right now” — and ends the thread. No ghosting. No awkward silence.
Everything else goes into a daily review queue: ambiguous leads, complex requirements, stalled conversations. You review once a day and make the call.
The flag pile should be small — five or fewer per week for most service businesses. If it’s growing, your qualification criteria aren’t specific enough and Claude is being asked to make judgment calls without sufficient rules.
A detailed walkthrough of how Claude handles the qualification conversation itself is coming soon.
Step 5 — Track the Three Numbers That Tell You If It’s Working
Check these three metrics each week once the system is live.
Lead response time. How long between a lead enquiring and Claude’s first reply. Target: under five minutes. Delays usually mean the channel connection trigger isn’t firing quickly enough.
Qualification rate. Of all leads entering the system, what percentage reach the booking trigger? Below 15 percent usually means the lead source quality is low. Above 60 percent might mean your criteria are too loose and you’re booking calls that shouldn’t happen.
Show rate on booked calls. Of calls Claude books, how many actually show up? Below 60 percent suggests the call was booked too far in advance, or the booking message didn’t set clear expectations.
These three numbers give you a complete diagnostic. McKinsey’s 2025 research found that organisations redesigning their workflows around AI — rather than layering AI on top of existing manual processes — are the ones capturing real business value [1]. The same principle applies at the service business level: measure the system, not just the output.
Run the Revenue Leak Calculator
If you’re not sure where your current sales process is losing leads before they reach Claude, run the Revenue Leak Calculator first. It maps the gaps in your response time, qualification, and follow-up sequence — so you know what to fix before you build anything.
Run the Revenue Leak Calculator →
Sources
[1] McKinsey & Company, The State of AI in 2025: Agents, Innovation, and Transformation, November 2025.
[2] Anthropic, Introducing Claude for Small Business, May 2026.
Frequently asked questions
No. Setting Claude up as a sales agent requires no coding. You write a system prompt — a structured set of instructions — that tells Claude how to respond to leads, what to ask, and when to hand off to you. The more specific your instructions, the better Claude performs. The connection to your email or CRM is handled through no-code integration tools like Zapier or Claude's built-in connectors.
A chatbot answers questions when someone asks. A sales agent runs a process on its own initiative. When you configure Claude as a sales agent, it reads every new inbound lead, applies your qualification criteria, sends the right follow-up questions, and either books a call or closes the thread — without waiting for you to prompt it. The difference is whether Claude is reactive (chatbot) or proactive (agent).
Claude sends a polite close message that explains the fit issue honestly — along the lines of "Based on what you've shared, I don't think we're the right fit right now" — and ends the conversation. This preserves your reputation with inbound leads who aren't a match and keeps your pipeline clean. Leads that Claude can't confidently categorise are flagged for your daily review queue.
Yes. Once a lead hits your qualification threshold, Claude can send a booking link automatically. The meeting appears in your calendar without any manual action from you. You can also configure Claude to notify you before booking if you prefer to approve each one. Most service businesses find the fully automated booking works well once they've tested and refined their qualification criteria.
HubSpot currently has the deepest native integration with Claude through Anthropic's Claude for Small Business connectors. If you're already using HubSpot, this is the most direct path — Claude reads lead records, runs qualification, and updates contact status automatically. For businesses using other CRMs, Zapier or Make can bridge the connection. A full guide to connecting Claude to your CRM is coming soon.