The bot that books while you sleep: Conversation AI
Deploy GHL’s Conversation AI to answer, qualify, and book across SMS and chat, rolled out supervised so it earns autonomy instead of assuming it.
- 1
Give it one job
The winning first deployment: answer common questions and book the calendar. Define the goal, the calendar it books, and the questions it must ask. Vague scope makes hallucinating bots.
- 2
Feed the knowledge base
Load business facts: services, hours, pricing posture, service area, policies, FAQs. It answers from what you feed it; thin knowledge means invented answers.
- 3
Configure channels and personality
Choose where it operates (SMS, web chat, social DMs), name it honestly (do not pretend it is human when asked), and match the brand voice in its instructions.
- 4
Start in suggestive mode
Run supervised first: the AI drafts, a human approves each send. Review a week of drafts, correct the knowledge gaps its mistakes expose, then graduate to autopilot channel by channel.
- 5
Define the escape hatch
Certain triggers always route to a human: anger, refunds, complex quotes, anything legal or medical. Configure handoff and make sure the human actually gets notified.
- 6
Audit weekly
Read a sample of conversations every week forever. Update the knowledge base from real questions; the bot is a living asset, not a set-and-forget toggle.
Do it with Claude
The Conversation AI Persona prompt in the library interviews you and writes the whole configuration: personality, instructions, knowledge base entries, and handoff rules.
Watch out for
- Autopilot on day one; a week of supervised drafts would have caught the pricing hallucination.
- No human-handoff triggers, so an angry customer argues with a bot.
