Back to articles

The widget that steps in when visitors hesitate

Automation•4 min read

A visitor reads your page about bookkeeping for five minutes, scrolls up and down and closes the tab. The visitor may well have had a question. But nobody asked it, and you never find out that it existed.

Most websites wait for the visitor to take the first step. It can be turned around: let the site say something when behaviour shows that the visitor is hesitating. Here we go through how it works and, above all, how you decide whether it helps.

What hesitation looks like

Hesitating visitors leave traces. There are five signals that are easy to read without asking anyone anything: how far down the page the visitor has scrolled, how long the visitor has stayed, whether the mouse pointer is heading towards the tab to leave the page, whether the visitor has stopped moving and whether the visitor clicks repeatedly in the same place.

Each one tells you a little. Together they tell you more. Someone who has read for a long time but done nothing is in a different position from someone who is about to leave.

A suggestion, not an interruption

When the pattern usually ends with the visitor leaving without getting in touch, the site can show a short greeting with a suggestion. The suggestion should be small and suit the situation.

  • Someone who has read for a long time might get: "Do you have a question? The chat answers straight away."
  • Someone who is about to leave might get: "Would you rather get a call? Within 45 seconds."
  • Someone who clicks repeatedly in the same place might get: "Is something not working? We'll help."

The wording should sound like you, not like an advert. And if the visitor doesn't bite, the site should back off and not insist.

Why it has to be measured

This is where it usually goes wrong. You switch on a nudge, the number of calls goes up, and you conclude that the nudge worked. But the number may have gone up for other reasons: a campaign, the season or another page getting more visitors.

The solution is a control group. A share of the visitors never see the nudge, even though they behave in exactly the same way. The difference between the groups is the effect. Without that comparison, you are only measuring what the traffic looked like that week.

It takes patience. You need enough visitors in both groups for the difference to mean anything, and you should resist declaring victory after a couple of days.

Consent and an off switch

A nudge relies on reading behaviour, so a few simple rules apply. No nudge should be shown unless the visitor has accepted analytics cookies. It should also be possible to switch the feature off completely, without the chat or the call function stopping working. A feature you cannot switch off is a feature you should not switch on.

Start on a single page, for example one where many people leave without getting in touch, and let it show what it can do before you build it out.

How it looks at Leadcaller

Leadcaller has built this as Ambient Agent, a proactive AI chat that is in beta. It reads the signals described above, lets the widget take the first step and is measured against a control group that never sees the nudge. The feature is switched on per customer under the chat in the admin panel, requires accepted analytics cookies and can be switched off centrally. On the Ambient Agent page you can watch the sensors at work in your own browser, and we promise no figures until the evaluation is complete.

Key takeaways

  • Behaviour on the page shows when a visitor hesitates, without anyone filling anything in.
  • A nudge is a short suggestion: ask a question or get a call.
  • Measure against a control group that never sees the nudge, or you won't know what it gave you.