Team routines
Ask for feedback as a team, without duplicate messages
Agree on the moment, the person and a simple phrase so asking for feedback fits into your service without pressuring customers.
A customer receives a link after their visit and another message from a colleague a few hours later. Nobody meant to push, but a simple agreement was missing. Coordinating the request matters as much as writing it well.
You can manage this routine with an internal checklist. It does not assume Sayso automatically detects visits or coordinates shifts. Define the process first, then use the capabilities available in your tools.
Choose a moment everyone can recognise
Pick a point in the service you can verify: work delivered, appointment finished or query resolved. ‘When they look happy’ is not a consistent criterion and excludes experiences you also need to hear about.
Agree who asks. If the usual person is away, make it clear who takes over. The agreement should be easy to explain to someone joining the shift.
Example to adapt
When the service closes, the person saying goodbye offers the link. If it has already been sent, nobody asks again during that visit.
Share the intention, not a compulsory script
Write a phrase that thanks the customer and invites them to describe the experience. Colleagues can adapt it to their own voice without requesting a particular rating or promising an outcome.
Practise what to say when someone does not want to reply, too. Accepting that decision naturally keeps the request from becoming uncomfortable. There is no need to ask for an explanation.
Example to adapt
If you would like to tell us how it went, I can share our feedback link. No problem at all if now isn't a good time.
Record only what prevents duplicate requests
Use your team's existing work record to note that the request has been made. Avoid creating another database with unnecessary personal information. The useful detail is whether the next colleague should ask.
If you combine an in-person request with email, agree which is the main channel. A reminder, when appropriate, should have a reason and a limit. Never turn a missing response into an open-ended task to keep contacting someone.
- Who makes the request.
- When they make it.
- Where to check whether it has already happened.
- When contact stops.
Review the process with your team
Ask which phrases feel natural and when the request interrupts the service. Adjust those details before setting volume goals. A number per employee does not explain workload or the customer experience.
Share what you learn without turning individual comments into a competition. Collecting feedback does not automatically make it suitable for your website either: review permission and publication separately.
Put it into practice
Write a four-line agreement: when to ask, who asks, how to prevent duplicates and when to stop. The routine should make the conversation more comfortable for everyone.
Give your next customer a way to tell you.
Create a review link, share your QR and collect feedback in one place. Start with 5 free responses per month, no card required.