Using AI to build a simple client-facing chatbot for your service business that answers booking and pricing questions after hours without a developer

You close up shop at 5pm, and somewhere around 7pm a potential customer lands on your website, ready to book — but they have one question about pricing. No one answers. They click away and book your competitor. That's the problem this post fixes: a no-code AI chatbot for your small business website that answers booking and pricing questions for you, even when you're watching TV. You don't need a developer, a big budget, or a background in anything technical to set this up.

What you need before you start

Chatbase{:target="_blank"} — a tool that lets you train a chat assistant using your own content (a PDF, your website, or typed FAQs), then embed it on your website as a chat widget. The free tier gives you one chatbot with 20 message credits per day. Paid plans start at $19/month for heavier use.

Time required: About 2 hours total — roughly 45 minutes writing your knowledge base, 15 minutes training the bot, and another 10–15 minutes getting it on your site.

Skill level: If you can copy and paste, and you've ever filled out a form online, you can do this.

---

Build the knowledge base that makes your no-code chatbot actually useful

This is the most important part of the whole setup. The chatbot can only answer what you give it. Vague input, vague output. If you type "prices vary by project," your bot will tell visitors exactly that — which helps no one.

Open a Google Doc or a plain text file and write out answers to the questions you hear most. Think of it like writing a FAQ page for someone who's never heard of your business.

Here are the five things your knowledge base should cover:

1. Write out your pricing clearly. Not "starting from" — actual numbers with context. "Our standard house clean starts at $120 for up to 2 bedrooms. A 3-bedroom home is $160. Add-ons like oven cleaning or fridge cleaning are $25 each." Specific inputs produce specific, useful answers.

2. Describe each service or package in plain language. What does a client actually get? How long does it take? What should they expect?

3. List your hours and location. Include whether you serve a specific area, your phone number, and your email.

4. Write a short paragraph about how booking works. Something like: "You can book online using our Calendly link [paste your link]. We confirm within 24 hours and send a reminder the day before."

5. Add your cancellation and refund policy. Even one or two sentences here prevents a lot of awkward conversations.

One more thing before you move on: add a fallback instruction at the bottom of the document. This is what your bot will say when someone asks something it can't answer. Here's a version you can adapt:

If you're unsure about something or can't find the answer in your knowledge base, say: "That's a great question and I want to make sure you get the right answer. Leave your name and email below and someone on our team will follow up within one business day."

This matters more than it sounds. AI chatbots will occasionally make up answers when they're out of their depth — a behavior called "hallucination." A clear fallback message keeps the bot honest and makes sure real leads don't fall through the cracks.

---

How to add an AI chatbot to your small business website using Chatbase

Now you've got your knowledge base document ready. Here's how to turn it into a working chatbot.

1. Go to chatbase.co{:target="_blank"} and create a free account. You'll land on a dashboard with a button to create your first chatbot.

2. Click "New Chatbot" and choose how you want to upload your content. For most service businesses, "Text" (paste directly) or "Files" (upload a PDF) is the easiest route. Paste or upload your knowledge base document.

3. Click "Create Chatbot." Chatbase will process your content — usually takes less than a minute. You'll see your bot appear in the dashboard.

4. Click on your new bot, then head to "Settings." Here you can give your bot a name (something like "Booking Assistant" or just your business name works fine), set a greeting message, and adjust the tone. Keep the tone friendly but professional.

5. Go to the "Playground" tab and test your bot by asking it a few of the questions you wrote in your knowledge base. Ask it something you didn't include, too — this is how you check that your fallback message kicks in properly.

6. Tweak anything that sounds off. If an answer is vague, go back to your knowledge base document, make it more specific, and retrain the bot by updating the source content in the "Sources" tab.

This is also a good moment to read the answers out loud. If something sounds robotic or confusing, rewrite it in your document the way you'd actually say it to a client on the phone.

---

Embed the chatbot on your website

Here's the part that sounds scary but genuinely isn't.

1. In your Chatbase dashboard, click on your bot and go to the "Connect" tab. You'll see an embed code — a short snippet of text that starts with <script> or looks like an <iframe>.

2. Copy that code. The whole thing.

3. Open your website editor. For Squarespace{:target="_blank"}, look for a "Code Block" in the page editor and paste it there. For Wix{:target="_blank"}, use the "Embed HTML" element. For WordPress{:target="_blank"}, paste it into a Custom HTML block or your theme's footer area. For most builders, you're looking for anywhere it says "embed" or "custom code."

4. Save and preview your site. You should see a small chat icon appear in the corner of the page. Click it — your bot should open and greet you.

That's it. No developer. No plugins (unless you're on WordPress, where Chatbase also offers a plugin if you'd prefer that route). Just a paste.

---

Connect the chatbot to your booking flow

Here's a small thing that makes a big difference: your chatbot doesn't need to actually do the booking. It just needs to get the visitor to the right link.

In your knowledge base document, include your booking URL clearly — whether that's Calendly{:target="_blank"}, Acuity Scheduling{:target="_blank"}, Jane App{:target="_blank"}, or whatever you use. Write it like this in the doc: "To book an appointment, visit [your link here]. You can choose your service, pick a time, and we'll confirm by email."

When someone asks "how do I book?" or "can I schedule a consultation?", the bot will pull that answer and drop the link right into the conversation. Clean and simple.

You don't need to build a fancy multi-step flow where the bot collects dates and times itself. That's a more complex setup (tools like Voiceflow{:target="_blank"} handle that well, but the learning curve is steeper and it's overkill for most service businesses starting out). Link to your booking page, let your scheduling tool do its job.

---

When something goes wrong

The bot gives a vague or unhelpful answer. This almost always means the knowledge base document was vague on that topic. Go back, find the question the visitor asked, and write a more specific answer. Retrain the bot. It usually only takes a few minutes.

The bot says something that isn't true. This happens when a visitor asks something that isn't in your knowledge base and the fallback message wasn't set up properly. Go back to your Chatbase settings, check that the fallback instruction is clearly written in your source document, and make sure you haven't accidentally deleted it.

Nobody's using the chat widget. The widget sitting quietly in the corner doesn't always get noticed. Chatbase lets you set a proactive greeting — a little message that pops up after someone's been on your page for 10 seconds or so. Something like "Hey! Got a question about pricing or booking? I can help." Enabling that one setting can make a real difference in how many people actually use it.

---

What to do next

Once your bot's been live for two or three weeks, open the conversation logs in Chatbase and read through what people have been asking. You'll almost always spot a question you forgot to include in your knowledge base — add it, retrain, and your bot gets a little better. Do this once a month and it'll keep getting more useful over time.

If you want to take this further and think about handling more complex client follow-up automatically, check out what Owen wrote about using AI to manage client communication sequences.

---

FAQ

Does adding a chatbot to my small business website hurt my search ranking? No — Google's guidance is clear that chatbot widgets on pages are SEO-neutral. They don't affect how your pages are indexed as long as the chatbot isn't replacing your main navigation or core page content. Your existing pages work exactly the same.

What if someone asks my bot something personal or complicated? That's exactly what the fallback message is for. Set it up to collect their name and email and promise a human follow-up. The bot's job isn't to handle every possible conversation — it's to answer the common stuff and route the tricky stuff to you.

Is there a no-code chatbot for service businesses other than Chatbase? Yes — Tidio{:target="_blank"} is another solid choice, especially if you want a live chat option alongside the AI bot. Tidio's free plan includes a basic AI assistant called Lyro (powered by Claude) that handles up to 50 conversations per month for free, and it installs on WordPress and Wix with a single click. Chatbase tends to be the easier starting point if you're brand new to this, but Tidio is worth a look if you want live chat built in from day one.

Do I need to tell visitors they're talking to a bot, not a person? Good question — most people wonder this. You don't have to phrase every response as "I am an AI," but it's good practice (and in some places, legally sensible) to make it clear in the bot's greeting that it's an automated assistant. Something like "Hi, I'm [Business Name]'s virtual assistant" sets the right expectation without making it feel cold.

Is it okay that the chatbot stores visitor conversations? Chatbase stores conversation logs by default, which means if your visitors share their name or email, that data is being held. If you serve customers in the EU or California, you may need to mention this in your privacy policy. Worth a quick check — and if you don't have a privacy policy on your site yet, this is a good nudge to add one.