Website chat that books vs chat that only logs tickets

A chat bubble on your website is not a lead path. It is a box someone types into. What happens after they type is the part you are paying for, and most owners never test that part until a real customer falls through it.

Here is the version that goes wrong. Someone lands on your site at 9:40 on a Sunday night. They want to know if you can fit them in this week. They open the chat, type a question, and get a friendly line saying the team is away and will reply soon. The widget asks for an email. They give it, close the tab, and call the next business on the list Monday morning. On your end, that conversation is now a ticket in an inbox nobody opens until Tuesday. The software worked exactly as designed. You still lost the customer.

The other version looks the same from the outside. Same bubble, same corner of the screen. But it asks what they need, asks for a name and a phone number before it lets them go, offers a time or tells them plainly when someone will call, and drops all of that into the place you already work. Monday morning you have a person, a reason, and a number. You call them before they call anyone else.

Both of those get sold as “website chat.” That label tells you almost nothing.

The tools in this aisle were mostly built for support teams

Look at who these products were made for and the split makes sense. LiveChat prices per person answering, $25 a user a month on Text Essential, and its native connections are Shopify, WooCommerce, HubSpot, and Salesforce. Crisp calls itself an AI customer support platform: a shared inbox, a widget, and a metered AI agent. Tidio is a cheap widget with a real free plan and an AI agent called Lyro, and its reviews come mostly from Shopify and WordPress stores. Chatbase is a bot you train yourself on your own pages and PDFs.

None of that is bad. A support inbox is the right tool when the person typing is already a customer with a problem, because a ticket is a fine way to track a problem. It is the wrong shape when the person typing is a stranger deciding whether to hire you. A stranger does not wait for a ticket to be worked. They leave.

So the question is not which widget is best. It is whether the path behind the widget ends with you holding a lead, or with a conversation sitting in a queue.

Question one: what happens after hours?

This is where the two kinds of chat split hardest, and it is the easiest thing to check. Open your own site at night, or set the widget to offline, and start a chat as if you were a customer.

If a human is supposed to answer and nobody is on, most widgets fall back to a form or an away message. That is a ticket. If an AI agent is supposed to answer, find out what it is allowed to do. Can it collect a name and number? Can it say when someone will call back? Or can it only answer questions from your FAQ and then say goodbye?

Read the meter too, because an after-hours bot that runs out stops working at the worst moment. Chatbase’s Hobby plan is $40 a month with 700 message credits, those credits reset on the 1st, and when you hit zero the public agent stops unless auto-recharge is on. Tidio bills human conversations, Lyro conversations, and Flows visitors as three separate meters. LiveChat’s Text Essential includes 10 AI resolutions a month. Crisp’s Mini plan includes about 90 automated conversations. Know which number your Sunday-night visitor is spending.

Question two: what does it make people give you?

A chat that ends without a phone number is a chat you cannot follow up on in time. Email feels polite, but you will not see it until you sit down at a desk, and by then the person has moved on.

Check which fields the widget can require before the conversation is handed off, and whether you can make the phone number one of them. Then check what it asks about the job itself. “What do you need and when?” is worth more than three questions about how they found you. One short reason line from the customer saves you a full call of guessing.

If the widget cannot require a number, or the AI agent cannot be told to ask for one, you have a support inbox. That may still be useful. It is not a lead path.

Question three: where does the lead land?

This is the question owners skip, and it is the one that decides whether anyone calls back.

If the chat lands in the widget’s own inbox, someone has to log into one more app to see it. If it lands in your email, it competes with every receipt and newsletter you get. If it lands in the CRM or job software you already open every morning, with the name and number filled in, it gets called.

Look at what each tool connects to natively before you trust a sales page that says “integrates with everything.” LiveChat and Crisp list HubSpot and Salesforce. Chatbase lists WordPress, Shopify, and Zapier. Our reviews did not find native pages for Jobber or Housecall Pro on any of these four. That does not make them useless. It means the handoff into your daily tool is a connector you will have to build, test, and watch, and that connector is where leads quietly go missing.

A ten-minute test before you pay

Run this on a free plan or a trial, on your real site, before you put a card down.

1. Set the widget to its after-hours state. Start a chat from your phone as a new customer with a real question.
2. Try to leave without giving a phone number. Write down whether it let you.
3. Ask something your FAQ does not cover. Write down whether it promised a callback or just said goodbye.
4. Go find the conversation. Time how long it takes and note which app you had to open.
5. Ask yourself if the person who usually returns calls would have seen it by 8 the next morning without being told.

If the answer to the last one is no, the widget logs tickets. Fix where the lead lands before you add anything else, or start with the website chatbot vs phone AI question, because for a lot of businesses the phone is still the bigger leak.

If you would rather not wire the chat, the fields, and the handoff yourself, we set it up for businesses nationwide. Tell us what you run, see how installs work, or write to support@counterandcrew.com.