FeedbackHub
When the work is personal, so is the feedback
Salons, clinics, garages, trades, repair shops and agencies all share the same shape: a person does a job for a customer, and the quality of that specific person's work decides whether the customer comes back. FeedbackHub asks once the job is finished and tracks the answer down to the individual.
The average tells you nothing when the work is individual
A salon with four stylists does not have one customer experience, it has four. A garage with three technicians has three. Averaging them produces a number that describes nobody and hides both the person who is quietly excellent and the one whose customers do not come back.
Asking the customer who looked after them changes what the data is for. Every response then carries a name, so the feedback stops being a general health check and becomes something you can act on: recognising the people doing well, and having a specific, evidenced conversation with someone who needs support rather than a vague one about attitude.
It also changes how staff relate to it. Feedback attached to a name and read weekly gets taken seriously in a way that a company-wide average never does.
How service businesses usually run it
Request sent when the job closes
Whether that is an invoice being saved, an appointment being marked complete or an order status changing, the trigger comes from the system you already use. If your software has no integration, the browser extension can watch the screen instead.
SMS as the primary channel
Service customers frequently give a mobile number and rarely an email address, and SMS is read within minutes. For trades and mobile services it consistently produces higher response rates than email.
A "who looked after you" question
A single choice listing your team, added to the form. It takes the customer one tap, and it means every response carries the name of the person who did the work, so praise and complaints can be read per person rather than only in aggregate.
An effort question
Service businesses lose customers to friction more often than to poor work. Asking how easy the whole process was, from booking to collection, surfaces problems in the parts of the experience nobody thinks to measure.
Immediate alerts on complaints
A low score emails the owner or manager with the comment and the customer's details. In service work the window for recovery is short but real, and a call the same day frequently resolves what a week's delay would not.
Review routing for local search
Happy customers see your Google link on the thank-you screen. For a local service business competing on the map results, a steady flow of recent reviews is worth more than almost any other marketing activity.
Salons and barbers
Ask by SMS an hour after the appointment, tagged to the stylist. The complaints that matter are usually about listening rather than technique, and they show up clearly in the comments. Rebooking rates and feedback scores tend to track each other closely.
Clinics and practices
Ask about the visit rather than the clinical outcome. Waiting times, being kept informed and how the reception process felt are the recurring themes, and all three are within your control. Keep forms short and avoid collecting anything you do not need.
Garages and workshops
Ask two days after collection, once the customer has driven the car. Asking at collection measures the paperwork; asking later measures the repair. Effort scores are particularly revealing here, because the process usually involves more customer work than anyone realises.
Trades and home services
Send from the invoicing system when the job is signed off. A QR code on the invoice or the van catches customers who do not respond to messages. Punctuality and tidiness dominate the comments, more so than the quality of the work itself.
Agencies and professional services
Longer engagements suit periodic rather than transactional feedback. Ask at milestones, use NPS rather than stars, and treat a falling score as an early warning about a relationship rather than a complaint about a deliverable.
Repairs and equipment servicing
Ask once the customer has used the repaired item. Whether the problem actually got fixed is the question that matters, and it cannot be answered at the counter.
Using per-person feedback without poisoning the team
Scoring individuals is genuinely useful and genuinely easy to get wrong. Handled badly, it becomes a leaderboard people learn to game, and staff start steering unhappy customers away from the form rather than fixing what went wrong.
A few things keep it healthy. Look at the comments before the scores, because the comments explain and the scores merely rank. Compare people over a meaningful sample, since one bad week is noise and a stylist with twelve responses cannot be fairly compared to one with ninety. Watch for structural causes, because the technician who takes the difficult jobs will always score lower than the one who takes the simple ones, and that is not a performance problem.
Above all, use it more often for recognition than for correction. Staff who see their own positive comments read out in a Monday meeting will start asking customers to leave feedback themselves, and at that point the whole system runs on its own.
Timing the request in service work
The right moment is when the customer knows whether the job actually worked, which is usually later than the point of payment.
For appointments where the experience is the service itself, such as a haircut or a consultation, the same day is right. For repairs and installations, wait until the customer has used the result. For projects and ongoing work, ask at defined milestones rather than only at the end, because feedback that arrives after the relationship has already deteriorated is a record rather than an opportunity.
Deduplication protects regular customers who come in frequently. A configurable gap prevents the same person being asked again too soon, which matters in businesses where the same customer might visit every three weeks for years.
Built around how your jobs actually close
Tell us what system you book or invoice in and how many people are on the team. We will work out the trigger, the channel and the form with you.