What an AI front desk does (and doesn't)
Set clear expectations for a website chat assistant: what it handles well, where it fails, and the best use cases before you build.
Step 1 of the pathway. Before you build anything, get clear on what an AI front desk actually is. It is a chat assistant that lives on your website and does three jobs, 24/7: answers common questions, qualifies the visitor, and books the next step. That is the whole promise. Set the expectation now and the rest of this pathway goes smoothly.
What it does well
- Answers repeat questions: hours, pricing ranges, service area, what you do, how you work. The stuff your team explains ten times a day.
- Qualifies visitors: asks a few questions to figure out if someone is a real prospect and how urgent they are.
- Books the next step: hands off to a calendar link or captures contact details so nothing slips.
- Works after hours: most website visits happen when no human is watching. This catches them.
What it does NOT do
- It is not a salesperson. It sets up the human, it does not close the deal.
- It is not a knowledge oracle. It only knows what you feed it (Chapter 3 covers that). Outside its material, it should say so rather than guess.
- It is not a replacement for judgment. High-stakes, legal, medical, or money questions get routed to a human.
- It is not a support ticket system unless you wire it to one later.
Best use cases
- Service businesses where speed-to-lead wins the job.
- Any site where visitors ask the same 15 questions.
- Businesses losing after-hours inquiries to voicemail.
Caution: keep sensitive data private. Your front desk should never collect payment card numbers, government IDs, health details, or passwords in a chat window. Design it to book a call instead. We will reinforce this in later chapters.
Your artifact: the scope card. Fill this in before building:
AI FRONT DESK SCOPE CARD
Business: ____________________
Top 3 jobs it must do:
1. Answer: (list your 10-15 FAQs)
2. Qualify: (what makes a good lead? e.g., in service area, budget, timeline)
3. Book: (calendar link OR capture name + email + phone)
Hard NO list (route to human): ______________________
Sensitive data it must NEVER collect: payments, IDs, health, passwords
Hours it covers: 24/7
Next up, Chapter 2: pick your no-code chat platform.