Why nobody clicks your chat widget

You did everything right. Picked a support tool, pasted the script tag, matched the brand color, told the team. A week later you open the dashboard and there are three conversations. Two of them are you, testing it.

The widget isn't broken. It's being ignored, which is worse, because nothing shows up in an error log.

Here's the thing about that little circle in the corner: clicking it is a small action that feels expensive. The visitor has to start a conversation with a stranger, in a blank box, with no idea what happens next or how long it takes. Most people look at that deal and go back to skimming your pricing page with a question still in their head.

Every fix below removes one reason not to click. None of them takes more than a few minutes.

1. Stop waiting to be clicked

A bare launcher makes the visitor do all the work: notice it, decide it's worth it, open it, compose a message. That first step is the most expensive one in the whole funnel, and the widget does nothing to help.

Teaser bubbles flip it. A line or two of real text floats up above the closed launcher ("Questions about pricing? I can help"), and suddenly the visitor isn't starting a conversation. They're replying to one that's already open. Replying is cheap. Starting is not.

In Clanker Support, each line of your welcome message becomes its own teaser bubble automatically. Write two short lines and you get a little opening move on every page. If a visitor dismisses them, they stay gone for the session. Nagging is the fastest way to teach people to hate the corner of your website.

2. Give people their first sentence

Open any chat widget and you get a cursor blinking in an empty box. Now the visitor has to write. What do I call this thing? Is my question too vague? Am I about to talk to a bot that answers in riddles?

Composing is work, and work loses to the back button.

Starter questions fix this with one tap. Three or four chips under the greeting ("What's included in the free plan?", "Do you integrate with Shopify?") and the visitor's first message is already written. As a bonus, the chips quietly tell them what the agent is actually good at, which sets the conversation up to go well.

Don't invent these. Pull them from your last month of tickets. The questions people ask by email are the questions they'd tap in the widget, if only you'd offer them.

3. Rewrite the greeting like a person wrote it

"Hi! How can I help you today?" is what every widget on the internet says. Visitors have seen it a thousand times, so it reads as furniture. Generic greeting, generic expectations, no click.

Compare:

Hi! How can I help you today?

with:

Hey, I'm the Acme support agent. Pricing, setup, weird CSV imports: ask me anything. If I get stuck, a human takes over.

The second one does three jobs in two sentences. It says what the agent covers, it sounds like someone actually typed it, and it answers the fear nobody voices out loud: "what if the bot can't help me?" You already know the answer to that objection. Put it in the greeting instead of hoping people find out on their own.

4. Ask for less before the conversation

Some widgets open with a form. Name, email, sometimes a dropdown for "topic." Every field is a toll booth between a visitor and their question, and plenty of people just turn around.

We ship with the pre-chat form off. The widget opens straight into the conversation, and you ask for an email only when there's a real reason, like an escalation that needs somewhere to send the reply. You will capture fewer email addresses up front this way. You'll also have far more conversations, and a conversation tells you more about a prospect than an email field they filled with "asdf@asdf.com" anyway.

5. Hand off to humans fast, and say so

Most visitors test a widget before they trust it. The first question is a softball. What they're really checking is whether this thing loops them through canned answers forever, because everyone has been trapped in that maze before, and nobody goes back in twice.

So make the exit visible and make it early. We default to offering a human handoff after three exchanges, and honestly, for high-stakes topics like billing you may want it sooner. It feels backwards to advertise the escape hatch from your own bot. It isn't. The visitor who sees a clear path to a person asks the hard question. The one who doesn't ask the easy question, gets a decent answer, and still leaves with the hard one unasked.

We wrote more about scoping the handoff in our guide to AI first-response layers.

How you'll know it's working

Three numbers, checked weekly, no dashboard archaeology required:

• Conversations started. The raw count. This is the number the five fixes above move.
• Escalation rate. The share of conversations that reach a human. High isn't bad, and neither is low. What you want is a number that matches your intent: a filter in front of your team, or a full first line of support.
• Ratings. Thumbs on individual answers and the end-of-conversation score tell you whether the conversations you earned were worth having.

The bubble in the bottom-right corner of this page has all five of these turned on, so you can judge for yourself how it feels from the visitor's side. Ask it something you'd normally dig through docs for.

And if you'd rather your own corner stopped being decorative: it's one script tag, and the first 7 days are free.