Installing a live chat widget takes ten minutes. Running live chat takes a routine. The widget appears on every page, so shoppers expect an answer, and a chat bubble that nobody answers is worse than no chat at all. It tells the visitor that you are there and then shows them you are not.
This guide is about the operating side of live chat on a WooCommerce store: who covers it and when, what the widget says when nobody is online, which replies to save, how to look up an order mid-conversation, when to move a conversation to email or a ticket, and how to tell whether it is working. It does not rank tools. If you are still choosing one, our list of WooCommerce live chat plugins compares them, and the pages on live chat plugins for WordPress and live chat software widen the view. Everything below applies to whichever tool you pick, because the problems are about people and process, not features.
A note on numbers. You will not find response time benchmarks or conversion lifts here. Those figures vary by store, product and audience, and quoting a number from nowhere would only give you a target that has nothing to do with your shop. Where a number matters, this guide tells you where to find your own.
Decide what chat is for
Before you set hours or write replies, decide the job. Chat can serve several purposes, and a small team cannot do all of them at once.
| Purpose | What the chat handles | What it does not handle |
|---|---|---|
| Pre-sale questions | Sizing, compatibility, stock, delivery times, which product to choose | Complaints, refunds |
| Order support | Where is my order, change of address, cancellations | Product advice |
| Both | Everything above | Only as much as your hours and staff allow |
Most stores end up with both. That is fine, as long as you know which type of conversation gets answered first. Pre-sale questions are usually worth answering first, because the visitor is still on the product page and may leave in a minute. Order support questions can usually wait a little longer, because the customer already bought.
Write the answer down in a single line, such as “Chat answers pre-sale questions live and sends order problems to email.” That line will guide every choice that follows.
Staffing hours without guessing
The common mistake is to open chat during office hours because those are the hours somebody is at a desk. A better starting point is when your customers are on the site.
Find your busy hours from your own data
Two sources tell you most of what you need:
- Order timestamps. Your WooCommerce orders list shows the date and time of every order. Export a few weeks of orders and count them by hour of day and day of week.
- Chat starts. Once chat is running, your chat tool’s reports show when visitors try to start conversations, including the ones nobody answered.
Cover the hours when orders and chat attempts cluster. If you cannot cover all of them, cover the shortest window that captures most conversations, and make the offline experience good for the rest.
Time zones matter
If you sell in more than one region, the busy hours in your logs will be spread across several time zones. Show the hours on the widget in the visitor’s own time, or in a clearly labelled zone, so nobody turns up outside them.
Staff in shifts, not heroics
One person watching chat all day alongside other work will miss conversations. If you have a team, assign chat to one person per shift, with a named backup. If you are a solo owner, set chat hours as a block in your calendar, and close the widget outside it, rather than trying to be available all day.
Match the workload to the channel
Chat is quick but demanding, because a visitor is waiting. Two simultaneous conversations is manageable for most people, and more than that makes replies slow and sloppy. Check how many conversations your tool lets one agent hold, and set the limit to what a person can handle well, not the maximum the software allows.
Offline mode: what the widget does when nobody is there
Outside your hours the widget still appears, so decide what it says. There are three honest choices.
| Option | How it works | Good for |
|---|---|---|
| Hide the widget outside hours | No bubble, no promise | Small teams that cannot answer promptly the next day |
| Offline form | The bubble stays, but turns into a message form that collects an email address and a question | Stores that answer email reliably |
| Self-service first | The bubble offers links to delivery, returns and FAQ pages before it offers a form | Stores with good help pages |
Most live chat tools offer some version of an offline message form. Check the settings of yours rather than assuming, and test it by sending a message when you are offline.
Whichever you pick, three rules apply.
Say when you will reply
“We are offline, leave a message” is incomplete. Add when they can expect an answer, and only promise a time you can keep.
Collect an email address, not just a question
If the form lets a visitor send a question without contact details, you cannot reply. Make the email field required.
Route the message somewhere that gets read
Offline messages that land in a shared inbox nobody opens are a quiet way to lose sales. Send them to the same inbox or ticket queue you use for email, and include them in whatever daily check you already do.
Saved replies that sound like people
Saved replies go by other names: canned responses, shortcuts, snippets, macros. They cut typing time and keep answers consistent. They also make chat sound robotic if you use them badly. The aim is a library of accurate paragraphs that an agent edits slightly before sending, not scripts pasted word for word.
Start from your real questions
Do not write replies in a vacuum. Go through the last few weeks of support email and any chat history you have. List the questions that came up more than once. Those are your first saved replies.
A starting set for most WooCommerce stores:
| Category | Reply covers |
|---|---|
| Greeting | A short hello that asks what the visitor needs |
| Delivery | Delivery options, costs and typical times, with a link to the shipping page |
| Returns | The return window, condition rules, and how to start a return |
| Order status | How to find tracking, what each order status means |
| Product advice | Questions to ask before recommending a size, model or variant |
| Payment | Which payment methods you accept, and what to do if a payment failed |
| Discount codes | How to apply a code, and the conditions on it |
| Handoff | A line explaining you will continue by email, and what happens next |
| Closing | Thanks, and an invitation to come back |
Write them as starting points
Each saved reply should leave room for the agent to add one specific detail, such as the customer’s name or the product they asked about. A reply that could be sent to anyone reads like it was.
Keep the facts in one place
If a saved reply says “returns within 30 days” and your policy page says something else, you have two sources of truth and one of them is wrong. Link to the policy page from the reply, and review all saved replies whenever the policy changes.
Review the library regularly
Once a month, look at which replies get used and which do not. Delete the ones that never get used, edit the ones that agents always change before sending, and add replies for questions that keep coming up.
Looking up an order during a chat
Order questions are where chat feels slow, because the agent has to leave the conversation to find the order. A little preparation fixes that.
Ask for the right identifier
Ask for the order number and the email address used at checkout. Together they let an agent confirm that the person asking is the customer, which matters before you discuss delivery addresses or order contents. Never ask for full card numbers or passwords in a chat. A payment problem can be described without them.
Keep the orders screen open
In the WordPress admin, the WooCommerce Orders screen has a search box, so an agent can search by order number or customer email. Keep it open in another tab while on chat. Open the order to see its status, items, shipping address, notes and payment details.
Use order notes
When you handle a chat that touches an order, add an order note describing what was agreed. That way the next person to open the order, including you in a week, sees the history without hunting through chat transcripts.
Some tools connect to WooCommerce
Some chat tools can show the visitor’s recent orders inside the chat window. Others do not. If yours does, check exactly what it displays and to whom before you rely on it. If it does not, the search routine above works for any tool.
Know what the agent may do
Decide in advance which actions an agent can take in chat alone. Typical examples: update a shipping address before dispatch, resend an order email, explain a status. And which need approval: refunds, discounts, exceptions to the returns policy. A written list stops delays while the agent asks someone, and stops generous mistakes.
Handing off to email or a ticket
Not every conversation should finish in the chat window. Handing off well is a skill, and it prevents the customer repeating themselves.
Hand off when
- The issue needs investigation, such as a missing parcel or a payment problem.
- The customer needs to send files, such as photos of a damaged item.
- Someone else has to decide, such as a refund over your agent’s limit.
- The chat is going to end because your hours are over.
How to hand off
- Say it plainly. “I am going to continue this by email so I can attach the details. You will get a message from us shortly.”
- Confirm the email address. Check it matches the order, and read it back.
- Summarise the issue in the ticket or email, so the next person does not need to ask again.
- Attach or paste the transcript, if your tool allows.
- Give a time frame you can keep.
- Follow up. A handoff nobody follows is a dropped conversation.
Choosing between email and a ticket system
| Option | Strengths | Limits |
|---|---|---|
| Shared email inbox | Simple, no extra tool | Hard to see who owns what, easy to double reply |
| Helpdesk or ticket system | Assignment, status, history, reporting | Another tool to set up and learn |
If you receive a handful of handoffs a week, an email inbox with clear rules is enough. When handoffs pile up or more than one person handles them, a ticket system gives you a queue and an owner for each conversation. Many chat tools integrate with a helpdesk, so check what yours offers.
Reduce the handoffs you need
Every question that keeps getting asked is a page you have not written. Publish clear delivery, returns and sizing pages, and link them from the widget. If you want customers to help each other, a support forum can take pressure off chat. Our guide to building a customer support community on WordPress covers when that is worth doing.
Privacy and honesty in chat
Chat conversations contain personal data, such as names, email addresses and order details. A few habits keep you on the right side of it.
Tell visitors what is recorded
If transcripts are stored or sent by email, say so in your privacy policy, and consider a short line in the widget. Rules about disclosure differ by country, so check the requirements where you sell.
Do not collect what you do not need
Ask for an email address and an order number. Do not ask for dates of birth, full addresses or anything you cannot justify.
Be clear when it is a bot
If you use an automated assistant, do not let it pretend to be a person. Say it is automated, and give a clear way to reach a human. Customers forgive a bot that admits it is one far more readily than one that misleads them.
Keep chat out of your payment flow
Never ask a customer to type card details into chat. If a payment is the problem, direct them to the checkout or to your payment provider’s own page.
Measuring whether chat is working
You do not need a complex dashboard. A few numbers from your chat tool’s own reports, reviewed weekly, tell you most of what you need.
| Measure | What it tells you | Where to find it |
|---|---|---|
| Conversations started | How much demand there is | Chat tool reports |
| Missed or unanswered chats | Where your hours or staffing fall short | Chat tool reports |
| Time to first reply | Whether visitors wait too long | Chat tool reports |
| Conversations per topic | What your help pages are missing | Tag chats by topic as you close them |
| Handoffs to email or tickets | How many issues chat cannot resolve | Your ticket or inbox count |
| Orders after a chat | Whether pre-sale chats lead to sales | Compare chat contacts with order emails in your own records |
Your tool may define terms such as response time differently from another. Read its documentation so you know what each figure measures before comparing weeks.
Set targets from your own baseline
Run chat for a few weeks, note your typical first reply time and your missed chats, then set a target slightly better than that. A target taken from another store’s blog post may be impossible for your team, or too easy.
Tag every conversation
If your tool allows tags, tag each conversation with a topic as you close it: delivery, returns, sizing, payment, other. After a month, the largest tag shows you where to write a better help page or change a product page. That is often the most valuable result chat produces.
Ask for feedback carefully
A short rating question at the end of a chat is useful. Keep it to one question, and read the comments. Treat the scores as a signal to investigate, not a score to chase.
Watch for chat that hurts
Sometimes chat makes things worse. Signs include many unanswered chats, repeated complaints about slow replies, and visitors who open the widget and leave. If that is happening, reduce hours rather than staying open and failing. A smaller, reliable service beats a larger, patchy one.
A weekly routine that keeps chat healthy
- Check missed and unanswered chats from the last seven days, and see which hours they fall in.
- Read a sample of transcripts, including a few that went badly, and note what to change.
- Review the topic tags and pick the top question to fix on the site.
- Update any saved reply that does not match current policy or stock.
- Clear the handoff queue, and confirm nothing is more than a few days old.
- Adjust hours or staffing if the data points to it.
Thirty minutes a week is enough for a small store. The aim is to keep chat connected to the rest of your support, so it improves your shop rather than sitting beside it.
Frequently asked questions
How many hours a day should live chat be open?
Open it for the hours you can staff reliably, starting with the times your orders and chat attempts cluster. Check order timestamps and your chat tool’s reports for your own pattern. A short, dependable schedule is better than long hours with unanswered chats.
What should the chat widget do when nobody is online?
Either hide itself, or switch to an offline form that requires an email address and says when you will reply. Send those messages to an inbox or ticket queue that you check daily, and test the form yourself.
Should I use chatbots on a small WooCommerce store?
A bot can answer simple, repeated questions such as delivery times, but only if you keep its answers current and give visitors an easy route to a person. Say clearly that it is automated. If you cannot maintain it, skip it and rely on saved replies and good help pages.
How do I find a customer’s order during a chat?
Ask for the order number and the email used at checkout, then search the WooCommerce Orders screen in your admin. Check that the email matches before sharing details. Some chat tools can display orders inside the chat, so check what yours shows.
When should I move a chat to email or a ticket?
Move it when the issue needs investigation, files, a decision from someone else, or when your hours are ending. Confirm the email address, summarise the issue in the ticket, and tell the customer when they will hear back.
How do I know if live chat is worth keeping?
Look at your own numbers: conversations handled, missed chats, topics, handoffs and orders that followed chats. If chat answers real questions and you can staff it reliably, it is working. If it mostly generates missed chats, shrink the hours or close it until you have the capacity.