Handling the Same Question Over and Over

A repeat question is a signal, not a nuisance

When the same question lands ten times in a week, the temptation is to sigh and answer it ten times. But a question that keeps coming back is telling you something specific is unclear — on a product page, in an email, in the onboarding flow. The answer is the immediate job; the pattern is the real one. Teams that only ever answer never stop answering.

Answer the repeat fast, without sounding bored

The person asking has no idea they are the tenth today, and they deserve the same care as the first. A canned response keeps your answer accurate and quick, but paste it with a personal opening line so it reads as help, not as a form letter. Speed and warmth are not in tension here; the template buys you the time to be warm.

Trace it to the root cause

For each recurring question, ask where the customer should have found the answer and didn't. “Does it work on mobile?” asked repeatedly means your product page is silent on mobile. “How do I cancel?” asked repeatedly means the setting is buried. The chat is the symptom; the missing or unclear content is the disease.

Fix it where the question is asked

Once you know the root cause, put the answer in the path the customer was already on — the product page, the checkout step, the confirmation email — not just in a help article they will never look for. A published help article deflects the searchers; fixing the source page deflects everyone. Do both, but do the source first.

How MyLiveChat helps you spot the repeats

MyLiveChat's transcripts and tagging let you label chats by topic and see which questions cluster, and canned responses keep your answers fast and consistent while you work on the fix. The tool surfaces the pattern and speeds the reply; deciding what to change on the page is the human's part — and the part that actually reduces the volume.

Sort the repeats into causes, not topics

Grouping repeat questions by subject tells you what people ask about. Grouping them by why they had to ask tells you what to fix, and the fix is different in each case.

• The answer is not on the site. The simplest case — write the page.
• The answer exists but cannot be found. A navigation or search problem, not a content problem. Adding another page makes it worse.
• The answer is there but is not believed. Usually because it is vague or hedged. People chat to get it confirmed by a human.
• The answer is there but is confusing. Jargon, or a policy written for legal rather than human consumption.
• The product itself is unclear. The most valuable to find and the most expensive to ignore, because the question is a symptom of a design problem.

The last category is why repeat questions deserve attention beyond support efficiency. A question asked a hundred times a month is a hundred people confused by the same thing, and only a small fraction of the confused ever ask.

Keep the answer fresh without retyping it

Canned responses solve the typing problem but introduce two of their own. The first is staleness: a saved answer outlives the policy it describes, and nobody notices until a customer is given the wrong information confidently. Put a review date on the library and actually keep it — a quarterly pass over the twenty most-used responses catches nearly everything.

The second is tone. A response pasted verbatim into a conversation that has already gone a different direction reads as though nobody is listening. Treat saved answers as the accurate core, then adjust the opening line to the person in front of you. The customer should never be able to tell which parts were stored.

Fix it where the question is asked

A repeated question tends to be asked at a specific moment: on the shipping page, at the payment step, on a particular product. That location matters more than the answer itself, because most people who are confused do not ask — they leave.

Put the answer where the doubt occurs rather than only in a help centre. A single line of copy next to the delivery estimate removes far more contacts than a well-written article three clicks away. When the same question keeps arriving on one page despite the answer being on it, the answer is probably below the fold, in a collapsed section, or written in language that does not match the words customers use.

Run a monthly review

1. Pull the most frequent chat tags or subjects for the month.
2. Read five real transcripts from the top three, in full. The transcript shows the wording people use, which is usually not the wording on your page.
3. Classify each into one of the five causes above.
4. Assign one owner and one fix per item — a page edit, a navigation change, a product change — with a date.
5. Check next month whether the volume moved. If it did not, the diagnosis was wrong, not the effort.

Half an hour a month is enough. What makes it work is that it ends in an owned change rather than a list, and that someone verifies the outcome.

What to measure

Track the share of chats accounted for by your top ten question types. A concentrated distribution is good news — it means a small number of fixes can move a large amount of volume. Watch each fixed question individually after the change; a real fix shows up as a sustained drop in that tag, not a general improvement.

Also watch first-response time on the repeats. These should be your fastest conversations, and if they are not, the saved-answer library is either hard to search or out of date. Finally, keep an eye on satisfaction for chats answered from canned responses — a gap against hand-written replies usually means the saved answers have drifted into sounding automated.