Why comments at the counter go missing
A business with premises or a phone line can have a listening post that no dashboard shows.
The voice of the customer guide lists the feedback customers volunteer and says that each source has its own bias, so the sources are read side by side to cover each other's blind spots. A remark made to a person behind a counter is volunteered in the same way. What it lacks is a place to live: no ticket or review page holds it.
The service blueprint tutorial shows the weakness in a salon example, where information passed on by voice from the front desk is dropped when the mornings are busy. A comment made across a counter is also passed on by voice, if it is passed on at all.
This tutorial covers the remarks, comments and observations that customers make and that are not requests. A request for help at the counter or on the phone is a contact, and the first step below draws that line.
Before you start
- The shared reason list. The tagging tutorial builds it and is the prerequisite for this page. Have the list to hand, with its definitions and its rule for "other". This page applies the list and adds nothing to it.
- The complaints procedure. Have the business's written complaints procedureThe written process for complaints: what counts as one, how every channel feeds one log, the response promised, who decides and how customers escalate. and its log in front of you, because remarks that turn out to be complaints leave this log for that one.
- The places where staff hear customers. List them with the people who work there: the counter, the shop floor, the phone line, the collection or return point, the door where deliveries are handed over.
- One person to own the notes. As general practice, name someone who keeps the card and the place where notes are made, reads what arrives and runs the shared read described below.
- The people who own the causes. Whoever sets the opening hours, looks after stock, writes the signs, runs bookings or handles returns will need to see what the notes say about their part of the service.
- Whoever handles data protection. They agree who may read the notes and how long the notes are kept, which the step on names and details returns to.
The steps
Decide which comments are worth recording
Start by drawing the boundary. A request for help made on the phone, such as a booking to change or a delivery time to check, is a contact. It goes into the business's contact record and is tagged with a reason from the shared list, which the reason-list guide, tagging contacts by reason, sets up, and it does not go into this log. As general practice, a request for help made at the counter is handled in the same way. A question from someone deciding whether to buy has its own record, with its product, type and outcome, set out in the guide to answering pre-purchase questions. What this log takes is the other remarks a customer makes, once they pass the test below: a remark that the sign was hard to read, a comment that the price came as a surprise, a compliment, an observation that the door said open while the lights were off.
Then decide what is worth a note. This is general practice, not something a linked guide sets out. The voice of the customer guide starts each survey from a decision, asking who would act on the answer and what that person would do differently, and the same test works for a remark. A remark is worth a note when someone in the business could act on it, or when it supports or contradicts what other sources say. Write the test and a few examples from your own counter on a card that staff can hold. Cover what is not worth a note: small talk, and anything that is a request, which goes to the contact record. A complaint is passed on when it is made, as the step on complaints sets out, and the note only carries its log reference.
Pick where the note is made
As general practice, choose one place for each point where customers speak to staff, and choose it for the moment of hearing rather than for the end of the day. At a counter that may be a clipboard or a bound book within reach of the till. On the phone it may be a pad or a form on a screen that is already open. On the shop floor it may be a card in a pocket, emptied into the shared place at a set point in the shift. This tutorial describes no particular product, and what any system stores or shares is a question for its own documentation.
As general practice, whatever the choice, the place should be one the business controls and the note's owner can read without chasing anyone, not a personal notebook or a private message thread. Paper that waits to be typed up later loses the wording and the moment, so the place and the time of the remark go on the note while they are still known.
Write the note in the customer's words
As general practice, write what the customer said as close to their words as memory allows, and put quotation marks only around words the customer actually used. Where the note is a paraphrase, write it without quotation marks so that a reader can tell evidence from interpretation. The guide to turning customer language into page copy keeps exact phrases for the same reason: a phrase tidied by the team stops being evidence of what the customer said.
Add the situation in a few words, as general practice: what the customer was doing when they said it. The place and moment where a remark arises is a touchpointAny interaction between a person and a brand, paid, owned or earned, before, during or after a purchase., such as collecting an order, paying, returning an item or ringing about opening hours, and naming it lets the reader see where in the service the remark belongs. Leave out the writer's guesses. A note records what was said, not what the writer thinks lies behind it and not a judgement of the customer. The cause of a remark is worked out later, with the people who own it, and kept apart from the reason, as the tagging tutorial does.
Add a reason from the shared list
Choose the reason for the note from the list the help desk already uses, so that what customers tell staff and what they write to the business can be read by the same reasons, and do not start a second list for the counter. Contact reasonsThe main reason a customer contacted support, tagged by the agent from a fixed, defined list so volume and other service metrics can be read by cause. are used exactly as the tagging tutorial sets them out. This step applies that list and builds nothing new in it.
A remark is not quite a contact, and that changes the tagging. A contact is tagged when it closes, and a remark has no close, so, as general practice, the writer picks the reason while making the note and the reader checks it at the shared read. A remark may also be praise, or an observation that no reason on the list was written for. In that case, as general practice, choose "other", add a line on what it was about, and leave the list owner to read those lines under the rule the tagging tutorial gives. A growing "other" is a message about the list, not about the note.
Pass complaints and promises to their owner when they are made
A remark that turns out to be a complaint does not wait in the notes. Whether it is one is decided by the business's complaints procedure, not by the person writing the note, and the guide to writing a complaints procedure advises that a contact is handled as a complaint whenever staff are unsure. When the procedure's definition applies to what a customer has said, the member of staff passes it to the owner the procedure names and into its log, as that tutorial sets out for anything staff in the field hear, at the speed the procedure sets. A remark that sounds like one of the cases the procedure sends straight to its senior stage goes straight there.
The note then carries the log reference, so that the complaint is counted once, in the log, and is not mistaken for a second complaint at the shared read. This cross-reference is general practice. Promises cannot wait either. If a member of staff tells a customer they will find out, ring back or pass something to a manager, that promise has an owner from that moment. Telling a customer that you will find out and ring back beats guessing, as the pre-purchase guide says, but only when the promise is kept, so, as general practice, write who owns it and what the customer was told in the place where that owner will see it.
Keep names and details out unless a follow-up needs them
A note about a remark needs the remark, the place and the reason. It does not need the customer's name. Notes can still hold personal dataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier., because a customer's words can identify them when combined with other details and because a name or a phone number can be jotted down beside the remark. The GDPR text, as the site's data guides read it, asks for processing only what is needed, for entries to be held for a period the business sets and for access limited to the people who handle the records. Keep names, numbers and other identifying detail out of the note, give readers only the access they need, and agree with whoever handles data protection how long the notes are kept. Write "the person on the till" rather than a colleague's name. Treat this as general direction and not as legal advice.
A follow-up is the exception. The voice of the customer guide says that contacting a customer about their feedback needs their agreement first, so, as general practice, a note carries a way to reach a customer only when they have said they want to hear back, and it records that they agreed. Keep that detail in its own field, apart from the remark, so the words can be shared at the read without it.
Make recording quick and part of the shift
As general practice, keep the note short, because a queue may be waiting: keep it to the fields in the table below, make them tick-boxes or short lines where possible, and let staff jot a few words at the moment and complete the note at the next gap in the shift. Fit the step into the routine at points where staff already pause, such as after serving a customer or after a call, and add a check at handover that the notes have reached the shared place. As general practice, train everyone who serves customers in the card from the step on what is worth a note, in how to write the words, in what to pass on when it is heard and in what to leave out.
The counter sign-up guide, collecting email sign-ups in person, is a model for the staff side: it writes the words staff say, records the source at the time and thanks staff without rewarding counts alone. The last point matters here. Goodhart's law says a figure that becomes a target stops describing what it measured, so a target for the number of notes could reward trivial notes, and any wish to see fewer problems recorded could reward silence. Thank people for notes that led to a change instead.
Read the notes with the people who own the causes
A note that nobody reads changes nothing. As general practice, set a time that the business chooses and keeps for a short shared read, with the notes' owner and the people who own the causes of what the notes describe. It follows the outer loop of the voice of the customer guide.
As general practice, read the notes by reason first, then read a few in the customers' own words. Where the reason list cannot sort them, the "other" lines go to the list owner under the tagging tutorial's rule, and, as general practice, the method in coding open-text answers by hand, which is written for survey answers, with a codeframeThe defined set of codes open-text answers are tagged with, built from a sample, applied consistently, checked by a second coder and counted against a base., can be borrowed for the words already held; it does not replace the shared reason list. Keep the counts honest: counts of notes can be small, so follow the guide to reading small numbers, show the count beside each statement and treat a movement in a handful of notes as rough. As general practice, do not rank counters or phone lines by the number of notes they produce, because a place with more notes may only be a place with more people writing, and treat a single remark as a lead to follow, not a finding. As general practice, keep the notes' counts apart from contact counts such as contact rate, which the customer service metrics guide builds from contacts, because a remark is not a contact and adding it would change what the rate measures.
Check the notes against other sources and ask who is missing
The notes have a bias of their own, like each unsolicited source the voice of the customer guide lists. They come from the customers who spoke to staff, in the places and at the moments when staff had time to write. Read them beside the help desk contacts by reason, the reviews and the other sources the guide lists, and see where they agree and where they differ. As general practice, treat a reason that appears in the notes and in another source as better supported. Treat a reason that appears in one source only as a lead, and ask whether the other sources cannot reach those customers or whether the remark belongs to the counter alone. A reason that other sources show and the notes do not may point to a place or a moment where recording is thin, so ask staff what they heard there before taking the quiet for calm.
The habit of asking who is missing, which the survivorship bias framework names, is the question to put to the notes. Customers who did not speak to staff, customers who left and comments nobody wrote down are not in them, so the notes are one view and not the whole picture. Do not use them to put a figure on the customers who feel something. They show where to look.
Tell staff what changed because of what they recorded
When the shared read leads to a change, tell the people who wrote the notes and say which notes it came from. This is general practice, and it applies to staff what the voice of the customer guide says about closing the loop with customers. A change that customers can see, such as a reworded sign, a new line on a confirmation or a different return time, can carry a short note that customers raised it, and a customer who agreed to hear back is told directly. When the read leads to no change, say so and say why, then return to the card and ask whether it still names what is worth a note.
What a note holds
The table shows the fields a note holds. It is a general-practice layout to adapt, not a standard, and each field earns its place by serving a step above.
| Field | Contents | Purpose |
|---|---|---|
| The words | What the customer said, in quotation marks where the words are exact and without them where they are a paraphrase | Keeps the customer's terms and lets a reader tell evidence from interpretation |
| Where and when | The place and the moment, such as the counter at collection or the phone about opening hours | Records the touchpoint at the time instead of rebuilding it later |
| Reason | One main reason from the shared list, or "other" with a line on what it was about | Lets the notes be read by the reasons the help desk uses |
| What was said back | The answer or promise the customer was given, in a line | Shows what the customer was told and whether a promise is outstanding |
| Passed on | For a complaint or a promise, who received it and the log reference | Ties the note to the record that owns it, so it is not counted twice |
| Follow-up | Only where the customer agreed to hear back: how, and about what | The one place a contact detail belongs, kept apart from the words |
Leave out a customer's name, a colleague's name, the writer's view of the customer and a guess at the cause. Nothing in the table is a score or a rating: this tutorial asks nobody to rate anything and reads no sentiment from the words, and the surveys, interviews and help desk methods that other pages own stay with those pages.
A party hire shop starts a counter log (illustrative)
Troiwax Party Hire starts a counter log
Troiwax Party Hire, an invented shop that hires out tables, chairs, urns and gazebos, has one counter, one phone line and two vans for deliveries. Customers collect and return equipment at the counter, and staff hear what goes wrong without writing any of it down. The owner already tags the shop's email inbox with a reason list. Neither the counter nor the phone has a record of the remarks customers make.
For a fortnight the owner puts a clipboard of slips at the counter and a pad by the phone. Each slip has room for the customer's words, where it was heard, a reason from the inbox list, what the customer was told, a box for a log reference and a box for a follow-up that is filled in only when a customer agrees to hear back. A card on the clipboard says that a request for help goes into the shop's contact record and not onto a slip, and that a complaint goes to the complaints log at once. Slips carry no names.
The fortnight produces 34 slips. Staff tag 11 with the reason for gazebo set-up, in words such as "the pegs were not in the bag" and "nobody said which end goes up". Another 8 go under "other" with a line each, and they share a theme: an evening return slot that customers had not been told about, in words such as "I thought you shut at five". Four slips are complaints. Each went to the complaints log on the day and carries its reference, so each is counted once, in the log. One of those four complaints also carries a promise to ring back about a damaged urn; the customer agreed to be rung, the number sits in the follow-up box, and the manager owns the call-back.
Before anyone reads the slips as the whole picture, the owner reads them beside the same fortnight's inbox. Gazebo set-up appears there too, with 12 contacts, so two sources agree. The evening return slot does not appear in the inbox. It is a lead from the counter alone, which may mean customers raise it only face to face, or may mean that customers who were caught out do not write. The owner also lists who is missing: customers whose equipment arrived by van and who did not visit the counter, and customers who did not come back.
The owner puts a printed set-up sheet in each gazebo bag and adds the return time to the booking confirmation, then tells the staff which slips led to each change. In a similar fortnight afterwards the slips on those two reasons number 2 and 1. The owner takes that as a pointer only, since the counts are small.
Common mistakes
- Putting requests for help in the notes. A request is a contact and belongs in the contact record under the shared reason list; in the notes it stays out of the record that gets counted.
- Writing a summary instead of the words. A tidied remark is the team's view and not the customer's, and it is weaker evidence to code or to reuse for copy later.
- Starting a second reason list for the counter. The notes then cannot be read beside help desk contacts, and nobody can say whether the two sources agree.
- Leaving a complaint in the notes until the shared read. The customer waits for an answer and the complaints log undercounts.
- Recording names and numbers by default. The remark needs the words and the reason; a follow-up needs the customer's agreement first.
- Letting paper wait. Notes typed up later lose the wording and the moment.
- Setting a target for the number of notes. The count then measures the effort to hit it, and the notes may grow thin.
- Ranking counters or phone lines by notes. A place with more notes may simply have more people writing, and the counts are small.
- Reading the notes as the whole picture. They leave out customers who did not speak to staff, customers who left and remarks nobody wrote down.
- Collecting the notes and telling nobody what changed. Staff may stop writing, as customers stop giving feedback that changes nothing.
The measurement hub places this tutorial beside the surveys, the churn measures and the service metrics that together show how customers experience the business.
