Chatbot Features That Only Work in Pairs: A Dependency Map So Nothing You Switch On Breaks a Chat (Free Broken-Pair Finder)

Chatbot features are usually sold one at a time, as a list of ticks on a pricing page, but in a real chat they work in pairs. AI answers need your content. Handover needs opening hours. Opening hours need an away form. A proactive message needs someone to answer the reply. Switch on one half of a pair without the other and the feature doesn’t just fail to help: it creates a bad chat. This guide maps the 13 pairs that matter, shows what each broken pair looks like to a visitor, and gives you a free tool that finds the broken pairs in your own setup.

15features on the map
13pairs to check
5chains they form
10 minto audit your setup

⚡ In short

  • A feature on its own is half a job. Most bad bot chats come from a feature switched on without its partner.
  • The pairs form five chains: answers, after hours, people, nudges and data out.
  • Broken pairs make a promise the bot can’t keep, such as offering a person at 2 am. Fix those before launch.
  • Weak pairs only cost you some chats. Fix them in the first month.
  • Tick what you use in the free tool below and it lists every broken and weak pair, plus the one feature to add next.
Chatbot features 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 pairs

A feature is half of a pair

Most comparison pages list features in a column: AI answers, handover, opening hours, proactive messages, integrations. You tick the ones you want, pick the tool with the most ticks, and switch everything on. Then the first week of real chats shows problems nobody listed.

A visitor asks “where is my order?” and the AI bot replies with your returns policy, because it has no way to pass the chat to a person. Another visitor clicks “Talk to a person” at 11 pm and waits, because there were no opening hours to say the team was offline. A third gets a pop-up on the checkout page asking if they need help, and closes the tab.

None of those are bugs. Each feature did exactly what it was set to do. The problem is that a feature depends on another one to make sense, and the partner was missing.

That’s the angle this guide takes. Instead of asking “which features do I need?” (our guide to which AI features to switch on first answers that), it asks: “for each feature I already use, is its partner switched on too?” It’s a check you can run on any tool, before launch or on a bot that’s been live for a year.

The map below covers 15 common features and 13 dependencies between them. It’s deliberately generic: the names differ between products, but the pairs are the same. Where LiveChatBot is mentioned, it’s to show where each setting lives.

The map

13 pairs of chatbot features, grouped into five chains

Read each row as: if you use the feature on the left, you also need the one on the right. Broken means visitors see a bad chat. Weak means you lose some chats.

If you use……you also needIf it’s missing
AI answersYour knowledge addedBroken: the bot dodges or guesses
AI answersHandover to a personBroken: order and complaint questions go nowhere
AI answersA fallback bot or saved repliesWeak: nothing answers if AI is unavailable
HandoverAn inbox someone checksBroken: chats wait where nobody looks
HandoverOpening hoursBroken: a person is offered at 2 am
HandoverPhone alertsWeak: chats only seen at the desk
Opening hoursAn away formBroken: dead end outside hours
Away formTicketsWeak: offline messages have no owner
Proactive messagesConditions on who sees themBroken: everyone gets the same nudge
Proactive messagesSomething that repliesBroken: visitors answer and hear nothing
ConditionsVisitor trackingWeak: targeting is guesswork
Chat rescuerAn inbox someone checksWeak: the rescued chat waits again
Webhooks or ZapierTickets or an away formWeak: nothing to send

Chain 1 · Answers

AI answers, knowledge, fallback and handover

The answers chain is where most bots break first, because AI answers look complete in a demo. Ask a sample question, get a fluent reply, done. In practice, the feature has three partners.

Knowledge (broken if missing)

An AI bot that answers “from your content” has only what you give it. If you switch it on with an empty knowledge base, or just your homepage, it has nothing to say about delivery times, COD limits or your return window. Good tools then admit they don’t know; weaker ones guess. Either way the feature is useless until you add your real answers. Start with the 20 questions you get most. Our guide to training your AI chatbot shows how to write them.

Handover (broken if missing)

Some questions shouldn’t be answered by a bot at all: “where is my order 4471?”, “my payment failed”, “I want to complain”. The AI needs a way to say “I’ll pass this to our team” and actually do it. Without handover, it will answer something nearby, which is worse than no answer.

A fallback (weak if missing)

AI replies can be unavailable for a while, or a monthly allowance can run out. If nothing else is set up, chats go unanswered at exactly the moment you’re busiest. A simple keyword bot that replies from saved answers covers that gap. In LiveChatBot, when the AI Agent can’t reply, the free keyword bot answers from your saved replies, so writing 10 good saved replies completes this pair.

Chain 2 · After hours

The after-hours chain: chatbot features that fail at night

Most small businesses answer chats for 8 to 10 hours a day. The other 14 to 16 hours are where the after-hours chain matters, and where a missing partner does the most quiet damage, because you never see the chats that went wrong.

Opening hours need an away form (broken if missing)

Opening hours tell the widget when your team is around. That’s useful only if something sensible happens outside them. Without an away form, a visitor at 10 pm types a question, gets told the team is offline, and has no way to leave a contact. You lose the lead and don’t even know it existed. An away form that asks for an email or phone number turns that dead end into a morning task. See setting opening hours.

Away messages work better as tickets (weak if missing)

Once the away form is collecting messages, the next problem is volume. Twelve overnight messages in a general inbox get read by whoever opens the dashboard first, and some get missed. Tickets give each message an owner and a status (open, pending, solved), so nothing slips. In LiveChatBot, offline messages can become tickets, and the customer can follow their ticket on a page without logging in. Our guide to turning a chat into a ticket walks through it.

Handover needs opening hours too

This one crosses chains. If the bot can hand over to a person but doesn’t know your hours, it offers a person at 2 am. The visitor waits, nobody comes, and they leave thinking you ignored them. With hours set, the bot can say “our team is back at 10 am, leave your number” instead.

Free tool

Find the broken pairs in your setup

Tick the features you have switched on, or plan to at launch. The tool checks all 13 pairs, lists broken ones first, then weak ones, and names the single feature that would complete the most pairs.

Tick every feature you have switched on (or plan to switch on at launch). Leave the rest blank.

Runs only in your browser; nothing is sent or saved.

Chain 3 · Nudges

Proactive messages, conditions, tracking and rescue

Proactive messages are the most powerful feature on most lists and the easiest to get wrong, because a nudge is the bot speaking first. If it speaks to the wrong person, at the wrong time, with nobody to follow up, it annoys people who were happily browsing.

Conditions (broken if missing)

A proactive message with no conditions shows to every visitor on every page. That includes someone halfway through checkout, someone reading your privacy policy and someone who has visited six times this week and knows you well. Conditions narrow it down: only on the pricing page, only after 30 seconds, only for visitors from an ad, only on a second visit. In LiveChatBot, Flows allow up to six conditions, including page, source, country, device, browser language, number of visits, lead score and whether you already have contact details.

Something that replies (broken if missing)

A nudge invites a reply. If no AI, fallback bot or person is there to answer, the visitor replies “yes, I have a question” and hears nothing. That’s worse than no nudge.

Visitor tracking (weak if missing)

Several conditions depend on knowing what the visitor did: pages viewed, number of visits, where they came from. Without tracking, you can only target by the current page. See visitor tracking.

A chat rescuer needs an inbox

A rescuer, or follow-up message, re-engages a visitor whose chat has gone quiet. It’s a good feature, but if the reason the chat went quiet is that nobody is working the inbox, the rescued chat simply waits again. Our guide to proactive live chat has examples of nudges that work.

What visitors see

Broken pair vs complete pair

AI answers without handover
🚩 BrokenVisitor: “Where is my order?” Bot: “Our return window is 7 days from delivery.”
✅ CompleteBot: “I can’t see orders, so I’ll pass this to our team. They’re online till 7 pm.”
Opening hours without away form
🚩 BrokenVisitor at 10 pm: “Do you do bulk orders?” Widget: “We’re offline.” Visitor leaves.
✅ CompleteWidget: “We’re back at 10 am. Leave your number and we’ll call you.”
Proactive message without conditions
🚩 BrokenPop-up on the checkout page: “Need help choosing a product?”
✅ CompleteShown only on product pages after 30 seconds, never on checkout.
Handover without phone alerts
🚩 BrokenChat waits 25 minutes while the owner is at the counter.
✅ CompletePhone buzzes, owner replies in two minutes from the app.

Chain 4 · People

Handover, the inbox and phone alerts

Handover sounds like a single feature: the bot passes the chat to a person. In practice it’s a promise, and keeping it needs three things to be in place.

An inbox someone checks (broken if missing)

It seems obvious, but it’s the most common gap in small businesses. The inbox exists, chats arrive in it, and nobody is assigned to look. Decide who watches it during opening hours, and who covers lunch and leave. If that person is you, say so in writing to yourself.

Opening hours (broken if missing)

Covered above: the bot needs to know when handover is possible, so it can offer a person during hours and an away form outside them.

Phone alerts (weak if missing)

Small teams rarely sit at a dashboard all day. The owner is on the shop floor, the support person is also packing orders. Without alerts, a handed-over chat waits until someone happens to open the dashboard. With alerts, the chat finds the person. LiveChatBot’s Android app gives new-chat alerts; note that there’s no iOS team app, so iPhone users on your team would need the web dashboard open.

The test for this chain is simple. During opening hours, open your own website on a phone, ask the bot for a person, and time how long it takes someone to reply. If the answer is “nobody did”, one of these three partners is missing.

Chain 5 · Data out

Tickets, webhooks, Zapier and language

The last chain is about what happens after the chat: where the details go, and whether visitors who don’t write in English get the same experience.

Webhooks or Zapier need something to send (weak if missing)

Integrations are a popular tick on feature lists. But a webhook only fires when an event happens, and the useful events (a ticket created, a ticket solved, a lead collected) depend on you collecting them. If you connect Zapier to your CRM sheet but never switch on tickets or an away form, there’s nothing to send. In LiveChatBot, the REST API and webhooks cover ticket.created and ticket.solved; see connecting to Zapier. For developer documentation, ask our team.

Language: greeting versus answers

Auto language and translated welcome messages are a good start for visitors who browse in Hindi, Tamil or Marathi. But check the answers too. If your bot replies only from saved replies written in English, the greeting is in the visitor’s language and every answer after it isn’t. AI answers handle this better; a keyword bot needs saved replies in each language you want to serve. Our guide to multilingual live chat covers the setup.

These two pairs rarely break a single chat, which is why they’re marked weak. They cost you slowly: leads that never reach your sheet, and visitors who give up halfway through a chat because the answers switched language.

Before launch

Pair check

Pairs complete

When comparing tools

Check that both halves live in the same product

The pair map is useful when choosing a tool, not just setting one up. When you look at a pricing page, check that each feature you need comes with its partner, on the same plan, without an extra add-on.

Common gaps to look for:

  • AI answers on a cheap plan, handover only on an expensive one. The AI then has no way out.
  • Proactive messages without conditions. Some tools only let you show a nudge on all pages or none.
  • Opening hours with no away form, or an away form whose messages can’t become tickets.
  • Handover with phone alerts only on paid seats. Per-seat pricing can make phone alerts expensive for a team of five.

Be honest with yourself about what each tool doesn’t have, too. LiveChatBot, for example, has no pre-chat form, no WhatsApp inbox (there’s a WhatsApp button card that opens WhatsApp) and no iOS team app. If one of those is the partner of a feature you rely on, factor it in.

If you want a fuller way to test tools before you pick, our guide to chatbot characteristics gives ten test messages, and the chatbot maker red flags guide covers what demos hide. A list of chatbot features tells you what a tool can do; the pair check tells you whether it will hold together in a real chat.

Getting started

Audit your setup in ten minutes

Open your bot’s settings in one tab and the tool above in another. Tick every feature that’s switched on. Fix any broken pair today, starting with the one the tool names as “switch on next”. Then send three test chats from your phone: one during opening hours asking for a person, one at night, and one on the page where your proactive message shows.

LiveChatBot’s free plan covers both halves of every pair on the map: an AI Agent with a small free monthly allowance, a free keyword bot from saved replies, handover to the team inbox, Android app alerts, opening hours with an away form, tickets, Flows with conditions and a chat rescuer, visitor tracking, auto language, webhooks and Zapier. It’s free for two websites with 100 visitors per website each month, with no per-seat charges. See pricing and start at livechatbot.in.

Frequently asked questions

Which chatbot features depend on each other the most?

AI answers and handover, handover and opening hours, and opening hours and an away form. Those three pairs cause most bad bot chats when one half is missing.

What is the difference between a broken pair and a weak pair?

A broken pair makes a promise the bot can’t keep, such as offering a person at night. A weak pair only means you lose some chats or data. Fix broken pairs before launch.

Can I switch everything on at once?

You can, but only if every partner is set up too. It’s usually easier to launch one chain at a time: answers first, then after hours, then nudges.

Do I need AI answers to have a working bot?

No. A keyword bot that answers from saved replies, plus handover and an away form, is a complete setup. AI answers add coverage for questions you didn’t predict.

Does the broken-pair finder send my answers anywhere?

No. It runs entirely in your browser and nothing is sent or saved.

Keep reading

Related guides

📘

Chatbot Dialogue Turn-Taking: Who Talks, Who Asks and How Many Turns to an Answer (Free Turn Analyser)

Read the guide →

🧭

Chatbot Development, Stage by Stage: How Long Each Step Takes and Where the Hours Really Go (Free Effort Estimator)

Read the guide →

🛠️

Chatbot Design Blueprint: Sketch Your Bot’s Menu Tree on Paper and Catch Problems Before You Build

Read the guide →

Switch on features in complete pairs

AI answers, handover, opening hours, away form, tickets and Flows with conditions, all on the free plan. Start free on livechatbot.in.