Asking for feedback at the counter stops being awkward when the ask is one sentence that every customer hears, it points at a code the customer uses on their own phone after the staff member has stepped away, staff know what the messages are for and see what comes back, and nobody is measured on how many customers send one. It becomes awkward when staff have to choose whom to ask, wait while the customer does it, explain a form, hint at what to say, or chase a target. The ask is a line in the handover, like "would you like a receipt", and that is all it should feel like.
This article covers why staff avoid the ask, what the one sentence should and should not contain, where in the visit it goes, how to brief a team so the ask is theirs rather than head office's, and how to tell whether it is happening at a branch without standing behind the counter.
Why staff do not ask
Three reasons, and they are all reasonable.
They do not know what happens to the messages. A team member asked to point customers at a code they have never seen the other end of assumes the worst: that it is a way of rating them. Nobody promotes a tool they think is pointed at them.
It feels like selling. "Would you mind leaving us some feedback" has the cadence of an upsell, and front-line staff who are not salespeople dislike delivering it. The ask needs to sound like a service, not a request for a favour.
They have to decide whom to ask. If the instruction is "ask customers for feedback", each team member is now making a judgement at every transaction: is this one in a hurry, is this one annoyed, is this one going to say something bad about me. The judgement is tiring and it is also the thing that biases the whole channel, because the people most often skipped are the ones with something to say.
Remove the three and the ask becomes a habit within a week.
The one sentence
Short, the same for everyone, and about the customer's chance to be heard, not the business's need for data.
Workable shapes: "If anything was off today, or anything was good, that code goes straight to head office." Or: "There's a code on the card there if you want to tell head office anything about your visit." Or, where the customer is clearly a regular: "You know the drill, the card's there if there's anything."
What the sentence does: names where the message goes (head office, not the branch), says it is for anything (not just complaints, not just praise), and points at an object the customer can act on without the staff member.
What it does not do: ask for a rating, ask for a review, say "positive", say "five stars", say "it would really help us", mention anything the customer might get, or wait for an answer. The staff member says it and moves to the next thing.
Head office writes the sentence. Branches do not improvise their own, because the wording is where bias creeps in ("if you enjoyed your visit...") and because the same sentence at every branch is what makes branches comparable.
Where in the visit it goes
At the natural end of the transaction, in the same breath as the receipt, the change or the "see you next time". Not at the start, when the customer has not experienced anything yet, and not as a separate moment that interrupts the flow.
In a sit-down setting, the card on the table does most of the work and the sentence is said once when the bill is brought. In a service setting with a booking (a salon, a clinic, a workshop), it goes with the checkout, or with the reminder of the next appointment. In a gym or a membership business, it goes with the door, the check-in or the desk, whichever is where staff and member actually speak.
The one rule that matters: the staff member says the sentence and then leaves the customer to it. If the staff member stands and waits, the customer either declines or writes something polite. The point of a code on the customer's own phone is that nobody is watching.
What the customer has to do
As little as possible, because every step removes customers who had one sentence to offer.
Point a phone at the code, or tap the link. Type a sentence, or record a short voice or video message if they prefer, up to a minute. No app, no account, no required fields. Name and rating optional. A choice at the end of whether someone may contact them. Done.
If the first screen asks for a name, an email and a star rating before the customer can say anything, the staff member's one sentence was wasted, and after a few customers walk away from the form the staff member stops saying it.
Briefing the team
The ask belongs to the team only if they have been told the truth about the channel. A ten-minute briefing covers it.
Where the messages go. To head office, read by the same reader at every branch. The branch manager sees everything about this location. Head office sees every branch.
What they are used for. Fixing things customers notice that the branch cannot see: the rota at the peak, the thing that has been broken for a month, the policy that lapsed. Patterns across weeks, not single messages. Praise, which goes to the manager by name when the customer gave one.
What they are not used for. Scoring individuals. Comparing team members. Deciding anyone's shift or pay. Single messages are a reason to look, never a reason to act against a named person.
What comes back. The manager will share what customers said, the good as well as the rest, in a short weekly conversation. The team will hear when something changed because of a message. If that does not happen, the briefing was a lie and the team will treat it as one.
What to say and what not to say. The sentence, and the reasons it does not mention ratings, reviews or rewards.
A team that has had this briefing asks because it is in their interest: the channel is how the rota gets fixed and how their good days get noticed.
Making it the same for everyone
The ask is said to every customer, not to the ones who seem happy. This is a fairness point, a data point and a compliance point at once.
Fairness: the customer who had a bad visit is the one most worth hearing from, and the one a staff member is least inclined to ask.
Data: if branch 4 asks everyone and branch 12 asks the happy ones, head office is comparing two different populations and learning nothing.
Compliance: selectively inviting customers to review, by mood, by rating or by anything else, is the practice Google's Maps user contributed content policy lists under rating manipulation, with removal of the content as the stated consequence. The counter ask is not a review invitation, but keeping it universal keeps the business a long way from that line, and it is simpler to brief than any rule about whom to ask.
Outhentik is built so that the choices offered are the same for everyone who sends a message, and the ask at the counter should be too.
Telling whether the ask is happening
Head office cannot stand behind every counter. It can see messages per branch against footfall, and that is the number to watch in the first weeks.
A branch producing a steady stream has a team that is asking. A branch with similar footfall producing almost nothing has a code behind the till, a team that was never briefed, or a manager who did not pass the briefing on. In each case the first conversation is about the ask, not about the branch's service.
Within a branch, a sudden drop in messages often lines up with a change of shift lead or a run of new starters who were not briefed. That is the moment to repeat the ten minutes, not to add a target.
What not to do
Set a target for messages per shift or per team member. It changes the ask into a chase, and staff under a chase ask the easy customers and skip the rest.
Have staff hand the customer a device. The customer writes while being watched and says it was fine.
Let the team choose whom to ask. The judgement is tiring and the skipped customers are the ones who matter.
Mention reviews, stars or anything positive in the sentence. It biases the ask, and it moves the sentence toward the selective invitation Google's policy treats as rating manipulation.
Offer the customer anything for sending a message. It changes who writes and what they write, and the business then cannot trust its own channel.
Brief head office and assume the branches heard. The briefing reaches the counter only if the branch manager gives it, and new starters need it again.
Read a quiet branch as a satisfied one. It is unknown until someone checks the code and the ask.
What to expect
A team that has been briefed and given the sentence will ask within a week, inconsistently at first, then as a habit.
How many customers respond to the ask is not knowable in advance and will differ by branch, by time of day and by the kind of visit. The number that matters early is whether the branch is producing anything at all against its footfall.
Customers who are asked, and customers who are not, can leave public reviews anywhere they like. The ask gives head office the customer's account and the chance to act. It does not change what the customer does elsewhere and should not be presented to the team as if it does.
Frequently asked questions
What should staff say when asking a customer for feedback?
One sentence, the same for every customer, written by head office: where the message goes (head office), that it is for anything about the visit, and where the code is. No request for a rating or a review, no "it would help us", no mention of a reward. Say it with the receipt and move on.
When is the best time to ask a customer for feedback?
At the natural end of the transaction, in the same breath as the receipt or the goodbye. Not at the start, and not as a separate moment. In a sit-down setting, when the bill is brought. In a booked service, at checkout.
How do you get staff to ask customers for feedback?
Tell them where the messages go and what they are used for, including what they are not used for. Give them the sentence. Show them what comes back, every week, including the praise. Staff ask when the channel is visibly in their interest and never when they suspect it is pointed at them.
Should staff ask every customer or just some?
Every customer. Choosing whom to ask is tiring for staff, biases the channel toward customers with nothing to say, makes branches impossible to compare, and drifts toward the selective invitation Google's review policy treats as rating manipulation. The same sentence to everyone is simpler and safer.
Should staff be rewarded for collecting feedback?
No. A target or a bonus turns the ask into a chase, and staff under a chase ask the easy customers. Recognition for what customers say about staff, by name, is a different thing and works.
What if a customer does not want to give feedback?
Nothing. The sentence is an offer, not a request. The staff member has already moved on. The code stays on the counter for next time.
Try Outhentik free for 7 days, no credit card required
Outhentik gives head office a direct line from customers at every branch: every message read the same way, a case with an owner for each customer who asks to hear back, and a daily view of which problems repeat and where. The customer sends the message from their own phone, with nothing required, after the staff member has stepped away.