Website Chat App Requirements: Write a One-Page Spec Before You Choose (Free Spec Builder)

Website chat app demos all look the same: a friendly bubble, a fast reply, a tidy inbox. The differences that matter show up weeks later, when your iPhone-using partner can’t get notifications, the bill jumps because you added a third person, or after-hours messages vanish. The fix is old-fashioned and it works: write down what you need before you look at any provider. This guide walks through each requirement a small business should decide, explains why it matters, and gives you a builder that turns your answers into a one-page spec and a list of questions to send every provider.

2 websites, 3 people answering, ~1,800 visitors a month, WordPress.
Must: Android app, after-hours form, bot answers from our FAQs.
Budget: ₹500 a month. No per-seat charges.

⚡ In short

  • Decide your requirements before you watch any demo, or the demo decides for you.
  • The costly surprises are usually pricing rules, team devices, after-hours handling and limits.
  • Turn every requirement into a question and send the same list to every provider.
  • Then test your top choice for a week against real scenarios, not the vendor’s script.
Website chat app in LiveChatBot: the LiveChatBot Android app showing a new chat notification
How it looks in LiveChatBot: the LiveChatBot Android app showing a new chat notification.

Why a spec

The demo shows the best day; your spec covers the ordinary ones

A sales demo is designed to show a product on its best day. Someone visits, the bot answers perfectly, an agent jumps in, everyone is happy. Your real days look different: two people answering from their phones while serving customers in the shop, a festival rush, a visitor who writes in Tamil at 11 pm, a returning customer chasing a refund from last week.

A one-page spec moves the conversation from “what can your product do?” to “can it do what we need?” It also stops a common mistake: picking the product with the longest feature list, then using five features and paying for fifty.

The spec doesn’t need to be formal. One page, in plain language, with four parts:

  • Scope: how many websites, how many people answering, roughly how many visitors, what your site runs on, and your budget.
  • Must-haves: the few things you would walk away without.
  • Nice-to-haves: things that would help but aren’t deal-breakers.
  • Questions: each requirement turned into a direct question, so answers are comparable.

Writing it takes twenty minutes. It saves far more than that in demos you don’t need to sit through, and it gives you something concrete to check the trial against. The builder below drafts it for you.

Free tool

Build your one-page spec

Fill in your numbers and tick what you need. The builder writes the spec and the questions to send every provider.

Your team answers from
Needs (tick must-haves)

Runs only in your browser; nothing is saved. The spec is vendor-neutral: send the questions to every provider on your shortlist.

Requirement by requirement

What to decide, and why each one matters

Go through these one at a time. For each, write down what you need in your own words before reading any provider’s website.

Who answers, and from which device

List the actual people and what they carry. A shop owner on an Android phone, a part-timer on a laptop, a partner on an iPhone. Team apps vary a lot between providers: some have both Android and iPhone apps, some only one, some only a browser dashboard. Notifications on a locked phone are the real test, not whether an app exists.

How many websites

If you run two brands or a shop plus a booking site, check whether one account can cover both with separate settings, and how each extra site is priced.

How you’ll be charged

Pricing is counted per person (seat), per visitor, per conversation, or a mix. A per-seat plan is cheap for one person and expensive for five. A per-visitor plan is the reverse. Our guide to chat pricing models works through the maths.

What happens over a limit

Some providers charge automatically, some pause features, some stop the chat. Know which before a busy month surprises you.

After hours

Decide what a visitor sees when nobody is online: an away form that collects an email or phone, a bot that answers common questions, or both. Check where those messages go and who sees them next morning.

Automatic answers

If you want a bot, decide what it should answer from (your FAQs, your pages) and what happens when it doesn’t know. A good bot hands over to a person or the away form rather than guessing.

Your platform

WordPress, Shopify, Wix and custom sites install chat differently. Confirm the install method for yours: a plugin, an app, or pasting one line of code.

Ask and listen

Questions that separate the products

Send them in writing. Vague answers to these are a signal in themselves.

RequirementQuestion to askAnswer that should worry you
PricingWhat would our team size and visitor numbers cost, all-in?“It depends” with no worked example
LimitsWhat happens when we go over a limit?Automatic upgrade to a higher plan
Team devicesDo notifications arrive on a locked phone?“Keep the browser tab open”
After hoursWhere do after-hours messages go?“Visitors can come back later”
BotWhat does the bot do when it doesn’t know?It always answers something
IntegrationsHow do leads reach our sheet or CRM?Only on the top plan
ExitCan we export chats and contacts if we leave?No, or only on request for a fee

For a deeper security and privacy review, use our due diligence checklist. For warning signs that only appear after you sign up, see chatbot maker red flags.

Must or nice

Sorting must-haves from nice-to-haves

Most people tick too many boxes. When everything is a must-have, nothing is, and you end up choosing on price or looks. A simple test sorts the list quickly.

The walk-away test

For each requirement, ask: “If the best-priced website chat app on my list lacked only this, would I walk away?” If the honest answer is yes, it’s a must-have. If you’d grumble but sign up anyway, it’s a nice-to-have.

Tie must-haves to a real moment

A must-have should point to something that already happens in your business. “Customers message us at night and we lose them” justifies an after-hours form. “It would be cool to have AI” doesn’t justify anything yet. If you can’t name the moment, move it down the list.

Keep must-haves to five or six

Fewer is better. Five clear must-haves make providers easy to compare. Fifteen produce a spreadsheet nobody reads.

Write nice-to-haves as tie-breakers

Use them only when two products both pass every must-have. Then the nice-to-haves, plus how easy the product felt to your least technical team member, decide it.

Revisit after three months

Once you’re live, your real chats will show what matters. Things you thought were essential may go unused, and gaps you never considered will appear. Update the spec, so the next decision, whether to stay, upgrade or switch, starts from evidence.

Three example specs

How the same builder gives different answers

Illustrative businesses, not real customers. Notice how the must-haves change with the situation.

🧁

Home bakery, 1 person

One website, the owner answers on an Android phone between bakes, about 400 visitors a month. Must-haves: phone notifications, after-hours form, a few saved answers for prices and delivery areas. Bot answers are a nice-to-have.

🎓

Coaching institute, 4 people

Two websites (courses and admissions), four counsellors on laptops, evening enquiries from parents. Must-haves: no per-seat pricing, one inbox for both sites, opening hours, tickets for admission follow-ups, Hindi and English.

🛒

Online store, 2 people

WooCommerce shop, two people on laptop and Android, festival peaks. Must-haves: WordPress plugin that works on cart pages, bot answers for delivery and COD questions, leads sent to a sheet, visitor page tracking.

Trial week

Test the shortlist against your spec, not the demo

Once two or three products pass the questions, install your favourite website chat app on your real website for a week. Most providers offer a free plan or trial, so this rarely costs anything except attention.

Use real scenarios from your business, played by you, a family member or a friend on a different device and network:

  1. A pre-sale question on a product or service page during working hours.
  2. The same question at 11 pm, to check the after-hours experience and next-morning follow-up.
  3. A question your bot shouldn’t be able to answer, to see how it hands over.
  4. A message from a phone on mobile data, with your team member’s phone locked in their pocket.
  5. A returning visitor chasing an earlier conversation.
  6. A visitor writing in another language your customers use.
  7. A lead that should end up in your sheet or CRM.

Write down what happened against each line of your spec: met, partly met, or not met. After a week you’ll have evidence, not impressions. If two products tie, choose the one your least technical team member found easiest.

Trial log

Tick each scenario as it passes

Your ticks stay in this browser tab only.

Trial log

Where LiveChatBot fits

An honest match against common requirements

Here’s how LiveChatBot lines up with the requirements in the builder, so you can score it like any other website chat app on your list.

Pricing: no per-seat charges. The free plan covers two websites with 100 visitors per website each month; extra visitors come in packs per website (100 for ₹99, 500 for ₹299, 1,000 for ₹499) that never expire. Over the limit, tracking and alerts continue but chat pauses for new over-limit visitors until you add a pack or the month resets. There are no automatic charges. See pricing.

Team devices: a browser dashboard and an Android app. There’s no iPhone team app, so iPhone users on your team would answer from the web dashboard.

Automatic answers: an AI Agent that answers from the knowledge you give it, with a small free monthly allowance per website; when it’s unavailable, a free keyword bot answers from your saved replies.

After hours, tickets, greetings: opening hours with an away form that collects email or phone, tickets with owners and statuses, and Flows for proactive messages with up to six conditions.

Platforms and integrations: WordPress plugin (WooCommerce too), Joomla extension, React and Vue plugins, paste-the-code for Shopify, Wix and Squarespace, plus Zapier, webhooks and a REST API. See integrations.

Branding: “Powered by LiveChatBot” stays on all plans. If removing branding is a must-have, that’s a mismatch, and your spec has just saved you a trial.

Try it against your spec on livechatbot.in.

Frequently asked questions

What is a website chat app?

Software that puts a chat window on your website and gives your team an inbox, on a computer or phone, to answer visitors. Many include bots, visitor tracking and after-hours forms.

What should I decide before choosing one?

Who answers and from which device, how many websites, how pricing is counted, what happens over limits, after-hours handling, bot behaviour and your website platform.

How long should a trial last?

About a week, with real scenarios: a daytime question, an after-hours message, a question the bot can’t answer and a locked-phone notification test.

Per-seat or per-visitor pricing: which is cheaper?

Per-seat suits one or two people with lots of visitors; per-visitor suits bigger teams with modest traffic. Work out both with your real numbers.

Do I need a developer to install chat?

Usually not. Most providers offer a plugin or a single line of code to paste into your site’s settings.

Keep reading

Related guides

📘

Website Bot Visitors: How to Spot Crawlers, AI Scrapers and Spam Bots in Your Traffic and Chat

Read the guide →

🧭

Web Chatroom Safety for Members and Moderators: Room Rules, Scam Patterns and a Free Oversharing Screener

Read the guide →

Choose with a spec, not a demo

Build your one-page spec, test against it for a week, and see if LiveChatBot fits. Start free on livechatbot.in.