Blog Best practice

Website chat: how to choose and configure the widget

When a chat on your site makes sense, how to set availability and response times, and the mistakes to avoid on desktop and mobile.

Website chat: how to choose and configure the widget
In this article
  1. What is a chat widget?
  2. Types of chat widget
  3. When does a chat widget make sense?
  4. Yes, you need one if:
  5. No, you probably do not need one if:
  6. The benefits of a well-built chat widget
  7. 1. Higher conversions
  8. 2. A channel customers choose
  9. 3. Team efficiency
  10. 4. What chat lets you discover
  11. How to configure the chat widget
  12. Step 1: Where to show it
  13. Step 2: When to show it
  14. Step 3: Welcome message
  15. Step 4: Opening hours
  16. Step 5: Helpdesk integration
  17. Chatbot: yes or no?
  18. When to use a chatbot
  19. When NOT to use a chatbot
  20. Common mistakes to avoid
  21. 1. Aggressive pop-ups
  22. 2. Fake "live"
  23. 3. Asking for too much information
  24. 4. A chat cut off from everything else
  25. 5. An ugly widget
  26. Metrics to monitor
  27. First response time
  28. The verdict at the end of the conversation
  29. How many close in the chat
  30. Conversion rate
  31. Volume per hour
  32. On a phone, with extra care
  33. Chat widget implementation checklist
  34. Conclusion

A support widget often appears at the moment closest to a customer's decision: while they are evaluating a purchase, looking for information or trying to solve a problem.

Opening a chat window is not enough. It needs clear availability, credible response times, a smooth handoff from live conversation to ticket and a consistent desktop and mobile experience.

This guide covers the choices that determine whether the widget removes friction or simply creates another queue to monitor.

What is a chat widget?

A chat widget is a conversation window built into your website. The visitor clicks the icon, writes a message and gets a reply (from an agent or from a chatbot).

Types of chat widget

1. Chat with an operator A person replies while the visitor is still on the page. The acceptable wait is measured in seconds, not hours.

2. Chatbot A program replies, using predefined answers or generated ones. It covers simple questions even when the office is shut.

3. Hybrid The chatbot handles frequently asked questions. When it cannot answer, it hands over to a human agent.

4. Asynchronous The visitor leaves a message. The reply arrives by email. This is not really a "live" chat.

When does a chat widget make sense?

Yes, you need one if:

E-commerce with pre-sales support

  • Customers have doubts before buying
  • "Is this product compatible with...?"
  • "When will it arrive if I order today?"

Replying in real time = immediate conversion.

SaaS / software

  • Active trials with questions
  • Users stuck on a feature
  • Onboarding that needs assistance

Fast support = a user who does not walk away.

High-value services

  • Consultancy, quotes, demos
  • The customer wants to talk before buying
  • working out straight away who you are talking to

A request captured while the person is still interested is worth more than a form filled in three days later.

A site with significant traffic

  • Enough visitors to justify a dedicated agent
  • Or enough repetitive questions for a chatbot

No, you probably do not need one if:

Nobody can reply in real time

  • If "live" turns into "I will reply in three hours"
  • The visitor expects immediacy
  • An honest contact form is better

Very low traffic

  • few visits a day means very few conversations
  • whoever is watching the chat waits for nothing
  • the cost is real, the benefit is not

Self-service product

  • No explanations needed
  • The purchase journey is simple
  • A good FAQ is enough

Team too small

  • One person does everything
  • They cannot sit on the chat while working
  • Slow replies = a terrible experience

The benefits of a well-built chat widget

1. Higher conversions

The visitor has a doubt. Without chat:

  • They look for the answer on the site (and may not find it)
  • They send an email (and wait hours or days)
  • They give up and go to a competitor

With chat:

  • They ask and get an answer within seconds
  • Doubt resolved → they buy

The value of chat is measured on the pages where a doubt blocks the purchase: product, pricing, checkout. Measure the conversion rate of people who chatted against those who did not, on your own site: that is the only comparison that tells you anything.

2. A channel customers choose

Chat works for people because:

  • It is fast (vs email)
  • It is convenient (vs phone, no waiting)
  • It is asynchronous when needed (I write, I keep browsing)
  • It keeps a history (I can read it back)

3. Team efficiency

Someone on chat can follow several conversations at once, use canned responses and send the link to the right article. On the phone, one call at a time. How many parallel conversations your people can actually hold is something you find out by measuring, not by copying a number.

4. What chat lets you discover

The conversations show you:

  • Which questions visitors ask
  • Where they get stuck on the site
  • What is missing from your FAQ
  • Which products generate the most doubts

How to configure the chat widget

Step 1: Where to show it

On every page? Pro: always available Con: it can be intrusive

Only on key pages?

  • Product/pricing pages (pre-sales)
  • Checkout page (reduce abandonment)
  • Account area (customer support)
  • Contact page (obviously)

How to proceed: start on the pages where doubt blocks the purchase, and extend only if the numbers justify it.

Step 2: When to show it

Straight away on page load? Aggressive. It can be annoying.

After a few seconds? Give the visitor time to get their bearings before interrupting them.

When they are about to leave? It appears as the visitor moves away from the page: the last moment where a question still makes sense.

Only on request? The icon is there, but it does not open by itself. Less intrusive.

Advice: never open it automatically. A visible icon is enough.

Step 3: Welcome message

Wrong:

"Hi! Can I help you?"

Generic, adds nothing.

Better - contextual:

On a product page:

"Any questions about Product Name? I am here to help."

On the pricing page:

"Weighing up our plans? I can help you pick the right one."

At checkout:

"Problems with your order? Write to me, I am here now."

Step 4: Opening hours

Be honest about your hours:

  • "Online: Mon-Fri 9-18"
  • "We reply within 1 hour during office hours"

Outside those hours:

  • show a form so people can leave a message
  • say clearly when you will reply
  • or hide the widget altogether

Working hours and public holidays go into the SLA too, so the clock does not run overnight: how that works is in the customer service KPIs worth measuring in a small company.

Never: show "Online" when nobody is there.

Step 5: Helpdesk integration

Chat conversations must land in your helpdesk as tickets:

  • Complete history
  • Continuity when the customer comes back
  • Unified metrics
  • One place for everything

Do not use an isolated chat.

Chatbot: yes or no?

When to use a chatbot

Repetitive FAQs:

  • "What are your opening hours?"
  • "How much is shipping?"
  • "How do I return something?"

The program replies straight away, even when nobody is in.

Initial triage:

  • "What do you need help with? Orders / Products / Something else"
  • It gathers information before handing over to the agent
  • It shortens the human conversation

Outside opening hours:

  • It answers the basic questions
  • It collects requests for the next day
  • Better than "We are closed"

When NOT to use a chatbot

Complex problems:

  • Complaints, refunds, technical issues
  • The customer wants a human
  • The bot frustrates them and makes things worse

Significant purchases:

  • the higher the spend, the more the person wants to talk to someone
  • a program answering in place of a salesperson says the opposite of what you intended

The rule: people must be able to get from the chatbot to a person, and the way out has to be visible without hunting for it. What works and what does not once AI is involved is in AI in customer support.

Common mistakes to avoid

1. Aggressive pop-ups

Wrong:

  • A widget that opens by itself
  • It opens on every page
  • A notification sound
  • It takes up half the mobile screen

Result: an annoyed visitor who closes everything.

Right:

  • A discreet icon in the bottom right corner
  • It only opens when clicked
  • No sound
  • Responsive on mobile

2. Fake "live"

Wrong:

  • it is called live chat but the reply arrives half an hour later
  • the indicator says "online" and there is nobody there
  • the program pretends to be a person

Result: broken expectations = an angry customer.

Right:

  • if you cannot reply there and then, do not call it live chat
  • use "leave a message" and say when you will reply
  • if a program is answering, say so

3. Asking for too much information

Wrong: Before you can chat:

  • Name
  • Email
  • Phone
  • Company
  • Role
  • Reason for contact

The visitor gives up before starting.

Right:

  • Email only (so you can continue the conversation)
  • Or nothing at all (ask later if you need to)

4. A chat cut off from everything else

Wrong:

  • An isolated chat conversation
  • If the problem is complex, I have to start again by email
  • No history

Right:

  • The chat becomes a ticket
  • If it needs digging into, the agent already has the context
  • The customer repeats nothing

5. An ugly widget

Wrong:

  • Colours that clash with the site
  • A different font
  • It looks like a foreign body

Right:

  • Customised with your brand colours
  • Consistent with the site design
  • It looks like part of the whole

Metrics to monitor

First response time

How long before someone replies. There is no universal threshold, but there is a rule of thumb: if the visitor has time to change page and forget about it, that is no longer live chat. Set your own limit, state it and measure it.

The verdict at the end of the conversation

Ask for it as soon as the chat closes:

"How would you rate this conversation?"

The absolute value matters little: watch whether it falls, and read the negative ratings one by one.

How many close in the chat

How many conversations are resolved there, and how many end up as a ticket to work on later. If the second share is high, the chat is not answering the questions you put it there for: either the content is missing, or the questions are harder than you assumed.

Conversion rate

For pre-sales chat:

Visitors who chat and buy / Visitors who chat × 100

Compare it with visitors who do not chat.

Volume per hour

What time visitors write, and on which days. This is the figure that sets your shifts, not the office's habits.

On a phone, with extra care

On many sites, smartphone traffic exceeds desktop traffic. The widget must:

  • Not cover important content (CTAs, prices)
  • Be easy to close
  • Have readable text (no tiny fonts)
  • Be comfortable to type in (the keyboard must not cover the chat)
  • Load quickly (it must not slow the site down)

The test: open your own site on a phone, with the widget live, and try to buy something. If it annoys you, it annoys everyone.

Chat widget implementation checklist

Before switching it on:

  • Can someone reply in real time?
  • Are the opening hours defined?
  • Is a contextual welcome message configured?
  • Are the colours/branding customised?
  • Has it been tested on mobile?

Configuration:

  • Integrated with the helpdesk (conversations → tickets)?
  • Offline form configured?
  • Automatic reply outside opening hours?
  • Metrics switched on?

Launch:

  • Is the team trained on how to use the chat?
  • Predefined replies for common questions?
  • links to the relevant articles ready to send?
  • Escalation process defined?

After launch:

  • Monitor FRT daily
  • Review conversations for quality
  • Collect customer feedback
  • Adjust hours/coverage if needed

Conclusion

A website chat helps where doubt blocks the purchase. It becomes a problem when there is nobody to reply, when it opens by itself on every page, or when the conversation stays locked in a tool separate from the rest of your support.

The rule is simple: no chat is better than a chat nobody watches. If you do not have the people to answer on the spot, name a different channel and keep to that time: how to set the commitment and hold to it is in how to reduce response times.

Uppo

Turn the method into customer service that works.

Centralise conversations, assign clear ownership and keep response times and quality under control from one helpdesk.

Start your free trial Talk to the team