CX Outlet logo CX OutletCustomer experience, made practical for small businesses
Customer Experience

How to Turn Repeated Customer Questions Into Fixes

A bike repair shop I worked with last year kept a note taped to the till that said gift receipts: ask Marco. Nobody could tell me when it went up.

An index card beside a shop till marked with tally lines next to short handwritten customer questions

A bike repair shop I worked with last year kept a note taped to the till that said gift receipts: ask Marco. Nobody could tell me when it went up. Two members of staff had started after it appeared and had simply absorbed the rule, and in a fortnight of tallying, customers asked about receipts and returns 51 times. At roughly ninety seconds per answer that is about an hour and twenty minutes of staff time, every two weeks, spent explaining something a line on the receipt would have settled.

That is the part owners usually miss. A question that keeps coming back is not a quirk of your customers. It is a bill you pay in small instalments, and it is the cheapest feedback you will ever collect, because the customer has already done the work of telling you where your experience stops making sense. Complaints arrive late and loud. Repeated questions arrive early and quiet, which is why almost nobody writes them down.

Why the same question keeps arriving

Most repeated questions come from one of four gaps, and it helps to know which you are looking at before you try to fix anything.

Some are information that exists but sits in the wrong place. Opening hours printed on a door that is propped open all summer. A delivery radius buried on page two of your site. The answer is written down, just not where the question gets asked.

Some are questions about something your business does not say out loud because it feels obvious to you. Whether you take card payments under five pounds. Whether a repair quote includes parts. Whether the cafe will mind if someone works there for two hours. The curse of running the place is that the obvious stuff goes invisible.

Some are permission questions, and these are the ones I pay most attention to. Is it alright if I bring the dog in. Can I try two sizes. Would you mind if I pay separately. A customer who has to ask permission is a customer who has already half decided to leave, and the asking is the last moment you get.

And some are not really questions. When a customer asks how long the repair will take for the third time in a week, they are checking whether you remember them and whether your first answer was honest. Answering the words and missing the worry is how a small irritation becomes a one star review three weeks later.

Two weeks with an index card

You do not need software. Put a plain index card next to the till and a second one by the phone, and draw three columns: the question in four words, a tally mark, and a letter for how it ended. I use S for sorted on the spot, W for had to wait or come back, and L for lost the sale.

Ask staff to mark anything they have answered more than twice that week. Not every interaction, which nobody sustains past Tuesday. Just the repeats. The bike shop filled both sides of one card in nine days.

Two weeks is the right window. One week misses your quiet day and your busiest day, and a month turns into a project that never gets reviewed. Set a date to read the cards before you start tallying, because the step everybody skips is the reading.

Keep the wording the customer used rather than your translation of it. Someone asking do you fix these means something different from do you work on carbon frames, and the difference tells you what they expected before they walked in.

Ranking by cost, not by count

The question asked most often is rarely the one worth fixing first. What matters is the frequency multiplied by what each instance costs you, and a lost sale costs a great deal more than ninety seconds.

What the question sounds likeWhat it usually meansFix that tends to hold
Are you open on SundayYour hours are not where people look for themHours on the door at eye level, on the voicemail greeting, and in the first line of your listing
Does that price include fittingYour pricing stops one step short of the whole jobQuote the finished thing, with the breakdown underneath for anyone who wants it
Can I bring it back if it does not fitPermission question, and a sale wobblingSay the returns rule out loud at the counter before they ask, not after
How long will it takeAsked twice, it is a question about trust rather than timeGive a date and a name, then send one unprompted update before that date
Do you still do the repairsSomething about your front of house says you stoppedCheck what the window and the home page actually show, from the pavement
Who did I speak to last timeYour notes live in one person's headOne shared line per customer in the booking system, written the same day

Score each row roughly. Twelve asks a week at two minutes each is nearly half an hour of paid time. Three asks a week that end in L, a lost sale on an average basket of forty pounds, is a hundred and twenty pounds. The second row wins, even though it looks smaller on the tally.

Where the obvious answer goes wrong

The standard advice is to collect your repeated questions and put them on an FAQ page. I have watched that fail often enough to argue against it as a first move.

An FAQ page is read by people who are already on your site, already looking, already patient. The question at the counter is asked by someone standing in front of you with a coat on. Moving the answer to a page they will not visit does not reduce the asking, it just lets you feel you have dealt with it. The bike shop had a returns section on its site the whole time those 51 questions were being asked.

There is a second problem. A long FAQ page quietly signals that your business is complicated, and customers read that as risk. Twenty two questions about delivery is not reassurance, it is a warning. I would rather see three sentences in the right three places than twenty on one page.

Fix the question at the point where it gets asked. If it is asked at the counter, the answer goes on the counter. If it is asked on the phone, it goes in the greeting. If it is asked at checkout, it goes above the button, not behind a link. An FAQ page is a reasonable backstop once the frontline fix is in, and a poor substitute for it. The same logic sits behind small friction quietly losing customers, which is worth a read alongside this.

Start with three, not thirty

Take the two cards, pick the three rows with the highest cost, and make the change this week while the tally is still fresh. Write each fix as a single sentence and stick it next to the till so staff can see what changed and why.

Then run the cards again in six weeks. If a question has dropped from fourteen tallies to three, the fix worked. If it is still at fourteen, the fix was in the wrong place, which is useful information rather than failure. In my notes the most common reason a fix fails is that the answer went somewhere the customer was never going to look.

One habit worth adding permanently: ask whoever is newest on the team what they get asked that they still have to check. New staff hit the gaps in your experience at full speed before they learn to route around them, and they will hand you two or three things nobody else can see any more. If you want a wider view of the same ground, a one page customer journey map pairs well with the tally, and more on this side of the work sits in the customer experience section.

FAQ

How many repeated questions is normal for a small shop?

Every shop I have tallied found between six and fifteen distinct questions that came up more than twice in a fortnight. Fewer than six usually means staff were marking only the ones they found annoying. More than twenty is worth taking seriously as a sign the experience needs a wider look.

Should staff log questions on their phones instead of a card?

A card wins in practice, because it takes two seconds and sits where the work happens. Phone logging adds a step and tends to stop by day four. Move to a spreadsheet later if the habit sticks.

What if a question is only asked by one difficult customer?

Then it is not a repeated question and it does not belong on the card. The point of the tally is to separate a pattern from a one off, which is exactly what a complaint log cannot do on its own.

Does this work for an online only business?

Yes, and the source is your inbox and chat transcripts rather than a counter. Tally the pre purchase questions separately from the post purchase ones, because the first group tells you what your product page is missing and the second tells you what your confirmation email left out.

TA
Tanvir Ahmed

Tanvir writes about using feedback and handling complaints, turning difficult moments into stronger customer relationships.

More posts by Tanvir

More in Customer Experience

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto