AI Bot Software Requirements: Write a One-Page Spec Before You Compare a Single Tool

AI bot software is easy to buy badly. Most owners open five vendor websites, watch a few demos, and pick the one with the smoothest video. A month later they discover it can’t hand chats to staff, charges per seat, or stops answering when the AI allowance runs out. The fix takes about an hour: write a one-page requirements spec first, then make every vendor answer it. This guide shows how to write that spec, which requirements matter for a small business, and gives you a builder that turns your choices into a page you can send.

1

Must

Deal-breakers. If a tool misses one, it’s out.

2

Nice

Bonuses that break a tie.

3

Skip

Things you’ll ignore in demos.

⚡ In short

  • Write the spec before you look at any tool, so demos can’t set your priorities.
  • Keep 5 to 7 must-haves. More than that and nothing passes; fewer and everything looks the same.
  • Turn every must-have into a question the vendor answers in writing.
  • Include the boring requirements: hand-over, offline hours, fallback, seats and branding.
Ai bot software in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them
How it looks in LiveChatBot: AI Agent knowledge sources and a sample chat answered from them.

Why a spec

Demos answer the questions the vendor chose

A sales demo is a guided tour. The presenter asks the bot questions it has been prepared for, on a website that was set up for the demo, with no angry customers and no Sunday-night traffic. Everything looks good because the route was planned.

A requirements spec flips that. It’s a short list of what your business needs, written before you meet anyone, in your own words. When you take it into a demo, you set the route. “Show me what happens when the visitor asks something your bot doesn’t know.” “Show me what my receptionist sees on her phone.” “Show me the bill if two more people join the team.”

For a small business, the spec doesn’t need to be a formal document. One page is enough. It has three lists (must, nice, skip), a few facts about your business, and the questions you’ll ask. The point isn’t paperwork. The point is that you decide what matters while you’re calm, rather than in the middle of a polished demo.

There’s a second benefit. A written spec makes it easy to involve your partner, manager or the person who’ll actually answer chats. They can add the requirement you forgot, such as “must work on Android because that’s what the front desk uses”, before you’ve committed to anything.

Free tool

Build your one-page spec

Fill in four facts, mark each requirement, and press the button. Copy the result into an email or a note.

Mark each requirement (Must = deal-breaker, Nice = bonus, Skip = not needed)

Runs only in your browser; nothing is saved or sent. The defaults are an illustrative starting point, not a recommendation for your business.

The four facts

Numbers every vendor will ask you, so have them ready

Before the requirement lists, write down four facts. They decide which pricing model suits you, and vendors ask for them anyway.

1. How many websites

One shop site, or a main site plus a booking site, or several brands? Some tools price per website, some per account. If you run more than one site, read our guide to running chat on several sites.

2. Visitors per month

Your analytics tool shows this. Use monthly unique visitors, not page views. Visitor-based plans charge on this number, so write the real figure, not a hopeful one.

3. People who will reply

Count everyone who’ll ever answer a chat, including the owner on weekends. Per-seat pricing multiplies by this number. Our pricing models explainer shows how the same team can cost very different amounts on different models.

4. Busiest hours

When do questions arrive? If half come after 8 pm, offline handling and AI answers matter more than a fancy team inbox. If they come during shop hours, fast human replies matter most.

Write these at the top of your spec. They take five minutes, and they stop a vendor from quoting you for a plan that fits someone else.

Must-haves

Six requirements most small businesses should not skip

These are the ones owners most often forget until after they’ve paid.

📚

Answers from your knowledge

The bot should answer from the facts you give it, not from the general internet, and say so when it doesn’t know. Ask how you limit it, and test with a question you know isn’t covered.

🙋

Hand-over to a person

A visitor should always be able to reach a human, and your team should see the earlier conversation. See how hand-over should work.

🌙

Offline handling

Outside opening hours, the chat should collect a name and email or phone, not just show ‘we’re offline’.

🛟

A fallback

Ask what answers when AI replies are unavailable or used up. A silent widget is worse than no widget.

📥

A team inbox

One place for all chats, with a clear owner for each. Check per-seat charges at the same time.

🔌

Easy install

A plugin for your platform, or a single line of code you can paste. If installation needs a developer, cost that in.

Nice-to-haves

Bonuses that should break a tie, not drive the choice

Nice-to-haves are real benefits, but none of them should outweigh a missing must-have. Treat them as tie-breakers between two tools that pass all your musts.

A mobile app for staff. Useful if the owner answers chats from the shop floor. Check which phone platforms are supported; not every vendor supports both.

Proactive messages. The bot opens the conversation on a pricing page or for a returning visitor. Valuable for lead generation, but only once the basics work. Our proactive chat guide shows when it helps.

Indian languages. If your customers write in Hindi or Hinglish, test this during the trial with real questions rather than trusting a language list.

Tickets. Questions that need a follow-up, such as refunds or quotes, are easier to track as tickets with an owner and a status.

Integrations. Sending leads to a sheet or CRM saves copying, but you can run for months without it.

Visitor tracking. Seeing which page someone is on helps your team reply better, and it’s useful for sales.

A good rule: if you can’t name the exact week you’ll start using a nice-to-have, it isn’t one. It’s a feature you’ll pay for and forget.

Questions to send

Turn each must-have into a written question

Copy these into an email to each vendor. Written answers are easier to compare than demo memories.

How do I limit answers to my own content?
What does the bot say when the answer isn’t in my content?
Can I see and edit what it learned?
How does a visitor reach a person?
What does my team see when a chat is handed over?
Is there a per-seat charge? What happens when we add one more person?
What exactly is counted: visitors, chats, messages or AI replies?
What happens when we go over the limit? Is anything charged automatically?
What answers visitors if AI replies stop?
Is there a plugin for our platform?
Can we export our chats if we leave?
Can we remove your branding, and on which plan?

Scoring

How to compare AI bot software answers without overthinking

When the answers come back, don’t build a 40-row spreadsheet. Use a simple pass-fail on the musts, then a count on the nice-to-haves.

Step 1: musts are pass or fail

For each tool, mark every must-have as pass, fail or unclear. A fail removes the tool. An unclear answer gets one follow-up question; if it’s still unclear, treat it as a fail. Vague answers usually mean “no”.

Step 2: count the nice-to-haves

Among the tools that passed every must, count how many nice-to-haves each one covers. Weight them only if one really matters more, such as the staff app for a one-person shop.

Step 3: price on your own numbers

Use your four facts (websites, visitors, people, hours) to work out a real monthly price for the next year, including the extra person you might hire. The cheapest headline plan is often not the cheapest bill.

Step 4: a two-week test

Shortlist one or two tools and run them on your real website. Our 14-day free trial plan gives you a day-by-day script, and the platform scorecard helps if two tools are still tied.

Worked example

An illustrative clinic’s spec, start to finish

A made-up two-branch dental clinic. The numbers are for illustration only.

Part of the specWhat they wroteWhy
Facts1 website, about 1,800 visitors a month, 2 people replying, most questions 7 pm to 10 pmEvening questions mean offline handling matters
MustAnswers from our treatment and fees pagePatients ask the same fee questions every night
MustHand-over to the front deskPain and emergencies need a person
MustOffline form collecting phone numbersThe desk calls back at 9 am
MustFallback when AI is offNo silent widget at night
MustNo per-seat chargeA third receptionist joins next year
NiceAndroid app, Hindi replies, ticketsTie-breakers
SkipVoice calls, branding removalNot worth paying for now

Five musts, three nice-to-haves, two skips. That spec fits on one page, and every vendor can be checked against it in a single email exchange. For more on clinic chats, see our healthcare live chat guide.

Common mistakes

Five ways an AI bot software spec goes wrong

Copying a vendor’s feature list. If your spec reads like a pricing page, you wrote down their strengths, not your needs. Start from your customers’ questions instead.

Every feature is a must. Fifteen must-haves means no tool passes, so you end up ignoring the spec. Be strict: a must is something that would make you cancel.

Forgetting the people. Specs often describe the bot and forget the humans. Who answers at 9 pm? Who owns a refund question? If the answer is “the owner, on her phone”, then a staff app and good notifications matter.

Ignoring limits. “Unlimited” usually has a fair-use clause, and AI replies are often counted separately from chats. Ask what is counted and what happens at the limit.

No exit plan. Ask how you’d leave: can you export chats and contacts? A tool you can’t leave is a tool that can raise prices freely.

Where LiveChatBot fits

How our free plan maps to a typical spec

We’d rather you choose AI bot software with a spec than with a demo, so here’s how LiveChatBot answers the common must-haves, honestly.

The AI Agent answers from the knowledge you give it, and when AI replies aren’t available, a free keyword bot answers from your saved replies, so the widget never goes silent. Visitors can reach your team, who reply from a shared inbox or the Android app (there’s no iOS team app). Opening hours and an away form collect email or phone after hours, and offline messages can become tickets with owners and statuses.

On pricing, there are no per-seat charges. The free plan covers two websites with 100 free visitors per website each month, and visitor packs (100 for ₹99, 500 for ₹299, 1,000 for ₹499) never expire. Over the limit, nothing is charged automatically. The “Powered by LiveChatBot” line stays on all plans, so if branding removal is a must for you, we’re not the right fit. Test it against your spec on livechatbot.in.

Frequently asked questions

What should a requirements spec for AI bot software include?

Four facts (websites, monthly visitors, people replying, busiest hours), a short list of must-haves, a list of nice-to-haves, the things you’ll skip, and the written questions you’ll send to each vendor.

How many must-haves should I have?

Usually five to seven. Fewer and every tool looks the same; more and no tool passes, so the spec gets ignored.

Should I watch demos before writing the spec?

No. Write the spec first so the demo follows your priorities. You can add a requirement afterwards if a demo reveals something you genuinely missed.

What is the most forgotten requirement?

What happens when the bot can’t help: hand-over to a person, offline handling and a fallback when AI replies stop.

Do I need a developer to write the spec?

No. It’s a list of business needs in plain language. A developer only matters if a must-have involves custom integration.

Choose with a spec, not a demo

Write your must-haves, send the questions, then test one tool on your real site. Start free on livechatbot.in.