GUIDE / CHOOSING AN AI ASSISTANT

Website chatbot or AI receptionist?

A chatbot answers on your website. A receptionist answers the phone. The better starting point depends on where your customers need help and which conversations you’re struggling to keep up with.

Start with where your customers need help.

A chatbot helps people browsing your website.

A chatbot gives visitors a place to ask while they browse. They might want to know if you work in their area, how estimates work, or which service they need. It’s useful for people who prefer to type or aren’t ready to call.

The assistant can point people to a useful page or ask for more detail. If you want it to send project requests or book appointments, those connections need to be set up and tested too.

Consider chat when

Visitors often ask the same questions about your services, process, or service area before they contact you.

Prepare for chat with

Your business information, common questions, and instructions for when the assistant should send someone to your team.

An AI receptionist helps people who call.

A phone assistant needs to handle a real conversation. Callers may interrupt, change their minds, or want to speak to someone directly. Plan for those moments, including what happens if a transferred call goes unanswered.

You’ll need to decide when it answers, how it greets callers, and who it can transfer to. Your phone provider affects what’s possible. If it will book appointments, the calendar connection needs testing as well.

Consider a receptionist when

You miss calls while working, helping other customers, or after hours, and someone on your team can follow up on the messages.

Prepare for phone service with

Your phone provider details, hours, service area, common types of calls, and who should receive messages or transfers.

Both need good information and clear limits.

Decide what the assistant can answer and what needs your judgment. It shouldn’t guess a price or promise a time you haven’t approved. When information is missing, it should ask or help the customer reach a person.

Think about what you need after the conversation: a name and number, project details, a summary, or a transferred call. Then test that you receive it. Only collect information you actually need.

Start with the problem you actually have.

Write down the questions customers ask and where they ask them. If most of the problem is missed calls, start with the phone. If website visitors need help understanding your services, improve the pages and consider chat.

You might use both eventually. Give each a clear job and the same accurate business information. Be specific about what each can do, especially when it comes to taking requests, transferring calls, and booking appointments.

Try the awkward questions before you launch.

Ask about a service you don’t offer, a town you don’t cover, and a price it shouldn’t quote. Ask to speak to a person. For phone service, try interrupting and transferring to someone who doesn’t answer. Check what happens next in each case.

AI can get things wrong. Make time to review answers and update the business information. A good demo is a starting point; testing your own setup tells you how it actually works.

A few things you might be wondering

Can we start with one and add the other later?

Yes. Get the first one working well, then decide whether the other would help. Each needs its own setup, even when they share your business information.

Does an assistant have to book appointments?

No. Answering questions and collecting requests may be all you need. Add booking only if you want it and the calendar connection is ready.

LET’S TALK

Where does the conversation get stuck?

Tell us how customers reach you now. We can define a useful first step from there.

Discuss your projectPlan your project