WORKSHOP · REVENUE OPS · WS·06

CloseBot — AI Lead Qualification

A worked example: turning anonymous inbound into a confirmed discovery call, automatically. From five-channel chaos to one configured agent. 16 slides, 35 minutes.

16 SLIDES · ~35 MIN · PLAYBOOK OVERVIEW
Key Takeaways
  • Inbound is not a staffing problem anymore. It's a configuration problem.
  • 100% — Inbound channel coverage — zero lead leakage across DMs, webchat, SMS, and email.
  • 24/7 — Operational coverage including after-hours, weekends, and holidays.
  • 4 — Qualification questions collected through natural conversation — no forms.
  • Audit your inbound channels. Map every channel where a prospect can reach you today. If any of them lack instant response, that is your first gap. Twenty minutes, not a project.
WORKSHOP · REVENUE OPS

CloseBot

AI-powered lead qualification — from anonymous inbound to confirmed discovery call, automatically.

BuildClub Academy
01 · THESIS

Inbound is not a staffing problem
anymore. It is a
configuration problem.

The Thesis
02 · THE NUMBERS

What it delivers.

100%
Inbound channel coverage — zero lead leakage across DMs, webchat, SMS, and email
BuildClub CloseBot deployment data
24/7
Operational coverage including after-hours, weekends, and holidays
BuildClub CloseBot deployment data
4
Qualification questions collected through natural conversation — no forms
BuildClub CloseBot operating spec
03 · THE PROBLEM

Why leads go cold.

1
Volume floods five channels
Instagram DMs, Facebook, webchat, SMS, and email arrive simultaneously with no unified intake layer. Each channel has its own UI, its own latency, and its own way of being ignored.
2
Response delay kills intent
A lead who waits four hours for a reply has already moved on — to a competitor, to a different solution, or to inertia. Human SDR capacity cannot cover all five channels around the clock without melting.
3
Calendar stays empty
After-hours and weekend inbound — often the highest-intent traffic — converts at near zero without automation. The most motivated buyers reach out on Saturday morning. Your team finds them on Monday afternoon. They're gone.

The pattern is consistent across industries: the lead is not lost to a competitor. The lead is lost to silence.

04 · ARCHITECTURE

How it works: Capture → Qualify → Book.

1
2
3
1
Capture
Every inbound channel — Instagram DM, Facebook, webchat widget, SMS, email — flows through one source API into a unified contact record in the CRM. Five channels become one queue.
2
Qualify
The agent runs the four-question conversation: operational challenge, implementation timeline, budget alignment, decision authority. Answers write back to the CRM record automatically. No forms, no rep, no friction.
3
Book
Real-time calendar lookup against the team's availability, appointment booked into the consultant's calendar, confirmation email sent, CRM stage auto-advances to Qualified Lead. The whole loop closes in one conversation.

Three stages, one workflow. No human in the loop until the discovery call itself.

04b · ARCHITECTURE DIAGRAM

The architecture, in one picture.

The architecture, in one picture.
Source: CloseBot architecture diagram — five inbound channels collapse to one agent, one CRM record, one calendar.
05 · QUALIFICATION ENGINE

The four qualification questions.

Operational Challenge
What specific problem are you trying to solve as you scale? The opening question — it determines whether this conversation should continue at all.
Implementation Timeline
What is your target window for addressing this challenge? Separates 'researching' from 'ready to move' without making the prospect feel sold to.
Budget Alignment
What is your approximate investment range for this type of engagement? Filters out tire-kickers before a senior consultant's calendar gets touched.
Decision Authority
Are you the primary decision-maker, or will others need to be involved? Determines whether the discovery call should expand to multiple stakeholders.

Asked one at a time, in conversational order. The agent waits for an answer before advancing. No multi-question messages — they kill conversion.

06 · CONFIGURATION

Configure your agent: persona, cadence, language.

1
Human persona, not a bot label
Give the agent a first name and a conversational tone. Prospects engage roughly three times longer when the agent presents as a junior team member than when it identifies as 'AI Assistant' or 'Support Bot.' The name does the work.
2
One question at a time
Multi-question messages kill conversion. The agent asks, waits, then advances. The discipline is conversational rhythm, not throughput. A four-question qualification spread over four turns outperforms the same four questions in one bulleted message every time.
3
Multilingual by default
Responds in the prospect's language automatically — no configuration required. For inbound that crosses borders (or US markets with significant Spanish-speaking buyers), this turns a hard ops problem into a free side effect.

Three configuration choices that punch above their weight. None require code. All require discipline.

06b · PRODUCT VIEW

Configuring the agent: what it actually looks like.

Configuring the agent: what it actually looks like.
Source: CloseBot configuration screen — persona, cadence, and language are settings, not engineering tickets.
07 · INTEGRATIONS

What the agent can actually do.

SmartFAQ
Answers product questions using the company knowledge base. The agent reads from a connected document store and replies in the prospect's language.
Email
Sends confirmation and follow-up emails during the conversation itself. The prospect gets a receipt before they leave the chat.
Book Appointment
Books discovery calls directly into the CRM calendar — no scheduling link, no back-and-forth. The agent owns the booking flow end to end.
Check Availability
Reads open staff slots from the CRM calendar in real time. The agent only offers times that are actually free, on the right consultant's calendar.
Update Tags
Tags the CRM contact with the qualification answers — challenge, timeline, budget, authority — so sales sees the context before the call.
Update Contact
Writes name, email, phone, and any verified data back to the CRM contact record. No duplicate records, no manual entry, no data hygiene drift.
Cancel / Reschedule
Modifies existing appointments on request. Optional — turn on if your team wants the agent to manage post-booking changes too.
Send Proposal
Dispatches a scoped proposal document after qualification. Optional — most teams keep this human-only at this stage.
07b · INTEGRATIONS

The tools grid: what the agent can reach.

The tools grid: what the agent can reach.
Source: CloseBot tools panel — every tile is a capability the agent can invoke mid-conversation.
08 · THE CONVERSATION

One lead. Four minutes. Zero human intervention.

1
Lead introduces the problem
Madison: 'Hi — what are you working through?' Lead: 'We doubled our volume this year and we're still doing everything manually.' Madison: 'That's a real bottleneck. What's hitting you hardest right now?' Lead: 'Manual follow-up. We're losing leads over the weekend.' The agent opens with the operational-challenge question and listens.
2
Agent qualifies + updates CRM
Madison: 'Sounds like a good fit for a discovery call. What's your last name?' Lead: 'Forte.' Madison: 'And the best email?' Lead: 'stephen@buildclub.com.' Madison: 'Got it. What times work next week?' Three turns, four data fields written to the CRM. No form.
3
Appointment confirmed
Lead: 'How about tomorrow 10am EST?' Madison: 'All set for Thursday May 28th at 10:00 AM. Confirmation going to stephen@buildclub.com.' Booking sent, CRM stage auto-advances, consultant gets the brief — qualification answers attached.

Three turns from cold inbound to confirmed call. The agent never broke conversational tone. The CRM updated itself.

08b · LIVE TRANSCRIPT

The conversation, as the prospect sees it.

The conversation, as the prospect sees it.
Source: CloseBot live chat transcript — four minutes, four qualification answers, one booked appointment.
09 · FAILURE MODES

Where this still breaks.

1
Bad data plumbing
If the CRM contact record is stale or your calendar integration is flaky, the agent's booking is worthless. The agent is only as good as the systems it writes to. Audit the pipes before you turn it on.
2
Wrong handoff threshold
Agents that try to qualify everyone burn brand. The four-question filter exists to reject leads gracefully. If the agent books every conversation, the discovery-call team loses trust in the pipeline within a week.
3
Stale knowledge base
SmartFAQ pulls from a connected doc store. If the docs haven't been updated in eight months, the agent confidently delivers wrong product details. Knowledge-base hygiene is now a sales discipline, not a marketing one.
4
No human escalation path
Some inbound deserves a human in the first response — enterprise inquiries, complaints, partnership pitches. Without a clear escalation trigger, the agent answers everything and you find out three months later you missed a $2M deal.

The agent isn't the failure point. The system around the agent is. Each failure mode is a configuration choice waiting to be made.

10 · MONDAY-MORNING ACTIONS

Five actions for CEOs.

Monday Morning
  1. 1
    Audit your inbound channels. Map every channel where a prospect can reach you today. If any of them lack instant response, that is your first gap. Twenty minutes, not a project.
  2. 2
    Define your qualification criteria. Nail down the four variables that make a lead worth a senior consultant's time: challenge, timeline, budget, authority. If your team can't list them today, the agent can't either.
  3. 3
    Configure a persona, not a bot. Give the agent a first name, a tone, and business context. The prospect should feel like they're talking to a junior team member, not a form.
  4. 4
    Connect your calendar and CRM. The booking only closes the loop if it lands in a real calendar and updates a real contact record. The plumbing is the project.
  5. 5
    Measure qualified pipeline, not lead volume. The metric that matters is confirmed discovery calls, not form fills or conversation starts. Change the dashboard first; the team's behavior follows.
11 · CLOSING

The pipeline
shift.

Every lead reaching out after hours,
on a weekend, or on a channel your team
cannot monitor is now capturable.

The Thesis
WS·06 · Questions CEOs Ask

Frequently Asked Questions

What is the core idea of CloseBot — AI Lead Qualification?
Inbound is not a staffing problem anymore. It's a configuration problem.
What does the data say a CEO should pay attention to?
100% Inbound channel coverage — zero lead leakage across DMs, webchat, SMS, and email. 24/7 Operational coverage including after-hours, weekends, and holidays.
What should a CEO do Monday morning after reading CloseBot — AI Lead Qualification?
Start here: Audit your inbound channels. Map every channel where a prospect can reach you today. If any of them lack instant response, that is your first gap. Twenty minutes, not a project; Define your qualification criteria. Nail down the four variables that make a lead worth a senior consultant's time: challenge, timeline, budget, authority. If your team can't list them today, the agent can't either; Configure a persona, not a bot. Give the agent a first name, a tone, and business context. The prospect should feel like they're talking to a junior team member, not a form.
What are the steps in CloseBot — AI Lead Qualification?
1) Capture; 2) Qualify; 3) Book.
Where do the claims in CloseBot — AI Lead Qualification come from?
The playbook cites BuildClub CloseBot — internal product walkthrough; BuildClub CloseBot operating thesis; CloseBot product overview; BuildClub inbound conversion analysis.
WS·06 · Sources

All Sources in This Playbook

00 / 16