AI assistant or a simple FAQ: how to tell what your small business really needs

An AI assistant on your website looks modern. But before you shop for a tool, ask yourself what problem you're trying to solve. Sometimes the right answer is a well-made FAQ page. Sometimes it's an assistant. And sometimes it's sticking with the phone.

Here are concrete criteria to help you decide, including the cases where an AI assistant would waste your time.

Start with your questions, not the tools

For two weeks, write down every question a customer asks you, whatever the channel: phone, email, social media, the counter. A notebook will do. Record the question in the customer's own words and how long it took to answer, then note whether the answer already existed in writing.

Then sort them into three piles:

1. Identical questions: “Are you open on Sundays?”, “Do you have parking?”
2. Variations: the same information, asked ten different ways. In a bike shop: “Do you repair e-bikes?”, “My pedal-assist bike is making a weird noise. Can you take it in?”
3. Special cases: a complaint, a quote, a case that means digging through past records.

The size of each pile tells you almost everything. Lots of identical questions: an FAQ. Lots of variations: an assistant can help. Lots of special cases: you need a human, period.

The three options, in plain terms

A static FAQ is a page of questions and answers where customers look things up themselves. It only answers the questions you anticipated, in the words you chose.

An AI assistant is a chat window where customers type in their own words; the assistant searches the documents you've provided and puts together an answer, even in the evening.

A human alone means you or an employee answering. It's the best quality of answer, and the most time-consuming.

The comparison table

When an AI assistant isn't useful

Let's be honest: for many small businesses, an AI assistant would be an unnecessary expense. Here are the four clearest cases.

You don't get many questions

A landscaper who receives a few emails a week, mostly quote requests, doesn't have a volume problem. Each request is a potential sale that deserves a personal reply. An assistant would put a middleman between the landscaper and a future customer.

Your questions are always the same

If almost everything you're asked comes down to five questions (hours, address, parking, payment, returns), a clearly visible FAQ on your home page does the job. An assistant would give the same answers, with a risk of error and one more tool to keep an eye on.

Your customers prefer the phone

If your customers have always called you, a chat window on your website won't necessarily change their habits. When almost everything comes in by phone, invest instead in good voicemail, clear callback times and a greeting that answers common questions right away.

Your information changes every day

A fish market announcing that morning's deliveries, a caterer with a daily menu, a snow removal company tracking its routes: the information is out of date almost as soon as it's written. An AI assistant answers based on what it has been given. If the document is from yesterday, so is the answer. A same-day post on your social media, or a person on the phone, is still more reliable.

When an FAQ is no longer enough

On the other hand, some signs show that your FAQ has reached its limit:

• you answer questions by email when the answer is already on your website;
• customers ask the same question using words your FAQ doesn't use;
• the answer depends on combining several pieces of information, such as “Does the warranty cover a part I bought online if I have you install it?”;
• in the evening, customers write to you anyway, because they couldn't find the answer in the FAQ;
• your FAQ has become so long that nobody reads it anymore.

Think of a physiotherapy clinic: the answers about insurance receipts exist, but every patient asks for them in their own way.

The hidden costs of each option

A tool's price is never its real cost. Here's what people forget to count.

Static FAQ

• Update time: an FAQ that nobody ever rereads ends up showing summer hours in the middle of January.
• Customers who can't find the answer: they call anyway or quietly go elsewhere, and you don't see it.

AI assistant

• Preparation: an assistant is only as good as what you give it to read. You have to gather your documents and clean them up: return policy, procedures, terms of service.
• Errors: a language model can phrase an inaccurate answer with great confidence. You need to review conversations regularly, especially at the start.
• The failed handoff: if the assistant hands off and nobody responds, the customer ends up angrier than if they had simply left a message.
• Data: your customers' questions go through one or more external AI providers. Ask the company behind the tool which providers receive them, and make sure that's acceptable for the kind of information your customers entrust to you.

Human alone

• Repetitive time: answering “Do you deliver to Mississauga?” for the twentieth time is time that doesn't go into your actual work.
• Delays: an email received on Friday evening often waits until Monday morning.
• Dependence: when the person who knows all the answers goes on vacation, everything slows down.

Five questions to help you decide

1. How many questions do you get per week, across all channels? If it's only a few, keep it simple.
2. What share of those questions already has a written answer? If it's next to none, start by writing those answers: that work is just as useful for an FAQ as for an assistant.
3. Do your customers write or call? If it's the phone, written support isn't your priority.
4. Does your information change every week, or even every day? The more it shifts, the less reliable automation becomes.
5. Who answers when the tool doesn't know, and how quickly? Without a clear answer to that question, no tool will help you.

If you choose an assistant: three good habits

• Start from your FAQ. A good FAQ isn't the enemy of an assistant; it's the raw material. Depending on the tool, you'll often need to copy its content into the assistant's documents rather than simply pointing to the page.
• Plan a path to a human. Customers must be able to ask to speak with someone, and someone must be notified. State on your website how quickly you respond.
• Review the conversations. The questions left unanswered tell you which document to write next.

---

A word about the tool we're building

We're designing Echo Support for small businesses that see themselves in the middle column of the table: a chat widget you paste onto your website, an assistant that answers from the files you upload (PDF, CSV or plain text .txt) and the published articles in your help centre, and a shared inbox. When it can't find the answer, the assistant is designed to offer a human rather than guess; if the customer accepts, the conversation goes to your team, the assistant stops replying in it, and team members who have turned on alerts receive an email. The application and its database are hosted in Quebec; AI responses and indexing go through external AI providers.

A free Echo Support plan lets you try the widget and the inbox, without the AI assistant. And if the table and the five questions above tell you that a good FAQ is enough, follow that advice. To learn more: echo-group.ca.