The customer asks the same question again. The problem may not be the answer
Follow a recurring request across channels and distinguish a closed contact from a customer's completed task.
Article language: English

In this article
A customer asks how to add another person to a training session. They receive a polite answer with a link. The next day they call. Support sends the same link again, this time with a friendly “as stated in our previous message”. That afternoon the customer asks a third time. The system contains three efficiently handled contacts. The customer's colleague still has no place on the course.
It is easy to see this as the recipient being absent-minded. First, follow their path. Perhaps the form allows a new course to be purchased but cannot add a participant to an existing order. The answer is grammatically correct and impossible to use in this situation. A fourth link will not give the form a missing function.
Returning to a conversation can reveal something about the service
In an original interview with John Seddon, the originator of the Vanguard method explains failure demand: contact arising because an organisation did not do something for a customer or did it incorrectly. This is a particular concept in service analysis; another message alone is not enough to classify a specific case.
A customer may return because they changed their mind, expanded an order or want to discuss a new need. They may also need clarification despite receiving useful information. When collecting cases, retain the reason for the return. “Another contact” is a good start for observation but a weak end to diagnosis.
In our fictional training example the request remains the same: add a participant to the booked date. It is not a request to buy another service. If someone returns after following the recommended step, their experience identifies a place to investigate. Perhaps the company sends instructions for another type of purchase. Perhaps the right option exists but is hard to find.
Before expanding the FAQ on a service page (in Polish), check whether the answer helps the person perform the task. A longer FAQ may explain a missing condition. It may also carefully describe a route that still leads to a closed door. Readers should not need an interpreter for instructions about instructions.
Follow the need across channels
Select a few recent cases in which a customer returned about the same matter. Within the rules governing access to information, reconstruct the order: question, answer, customer action, next contact. Do not start by judging the adviser's style. First see what the customer was trying to achieve and what they could do after receiving the message.
For the course, the first email might reach orders, the phone call reception and the third message a form. Each team sees its own fragment. Separately the answers all look reasonable. Connecting them shows that the customer is moving between buying a new course and changing an existing booking.
Write the customer's words beside the company's term. The customer says “add my colleague”, the system handles “change participant count” and the employee searches for “new order”. These are three entries into a similar-sounding matter. The review should establish which corresponds to the action required, not make the customer learn an internal classification.
A service map connecting the front and back office (in Polish) helps when a correct answer at the front depends on an unseen action behind it. You need not map the whole company. Mark where the request changes channel, who can perform it and what the customer knows after each transition.
Retain the connection between contacts when reconstructing the history. Three messages may belong to one need even if the system assigned three numbers. Conversely, one long thread may contain both adding a participant and a new question about another date. Counting case numbers alone makes it harder to see whether a fix addresses the same problem. Explain how cases were joined or separated in the trial.
If you do not know what the recipient did after the answer, record that gap. No further message might mean the task was completed, abandoned or resolved through another route. Do not decide by guesswork. You can select a few cases for conversation and ask what happened next, keeping a confirmed result distinct from missing information.
A closed contact and an achieved goal are different results
The GOV.UK guide to measuring transaction completion distinguishes completing a task in a service from the final outcome of the case. Filing an application can complete the transaction without deciding the application. This public-service example helps define what is being counted.
In the training business, sending a reply, closing a ticket and confirming a participant's place also mean different things. If the company wants to examine the addition journey, the number of emails sent will not answer that question. It needs a visible point after which the customer can consider their goal achieved.
This does not mean contacting someone after every short answer. Choose a check suited to the problem. In a few cases, see whether the indicated step produced a correct request, whether the recipient received confirmation and whether they understood the next action. Only that picture allows the chosen route to be assessed.
Also examine how contact is closed. A “case resolved” message sent merely after passing a question to another department may create a false sense of completion. One employee made their move, but the whole request still waits. The customer sees an ending and then has to call to find out whether anyone is handling the next step.

Ask whether the answer is useful for that person's situation. Someone coordinating a team's participation may need confirmation to pass to the participant. Merely displaying a form does not give them that material. In another case, the participant needs to know whether they can book travel. Two contacts about adding a person may therefore require the same back-office action but different information at the end.
Agree what the recipient would consider sufficient confirmation. It will not always be a new document. A message with the correct date and an unambiguous statement that the change was accepted may suffice. If the company only sends an automatic “thank you for contacting us”, the coordinator may reasonably ask again. The review should then concern the meaning of the confirmation rather than another explanation of the form.
Three similar questions may need three different fixes
First possibility: the answer did not arrive or the customer did not recognise it. Check the channel, message identification and information after submission. This is a delivery or discoverability problem. Adding content will not help if the recipient still does not know where to look.
Second: the answer arrived, but cannot be used to perform the task. In our example the link leads to a purchase that cannot change an existing booking. The correct action route and a clear explanation are needed. Another contact and the required information may suffice. Not every gap requires a new application feature.
Third: the company promised to return to the matter but did not do so at the agreed time. The customer asks “is there any news?” because they lack information to plan their own action. This leads naturally to a delay message without a new date (in Polish). Repeating the earlier answer does not replace a status update.
Do not assume every contact in a selected group has the same cause. Delivery and execution problems may arise in the same week. The label “customers do not read”, applied too early, ends the investigation. The overly broad label “poor service” does much the same from the other side of the desk.
Avoid a fix that reduces messages by making contact harder. Hiding a form may reduce visible returns while leaving the customer with an unresolved task. When reviewing the new route, also look at whether the person can obtain help and reach the intended outcome. A lower count alone does not reveal why people stopped writing.
Check an exception that simplified information does not handle. In our training example adding a person may be possible only after checking an available place. The page should identify the request and explain that confirmation must be awaited, rather than pretending it is automatic. The customer understands the next step and the company can check a condition a form alone cannot decide.
The website can point to the right entry
In the fictional example, improvement starts by separating a new booking from a change to an existing order. For a group booking, distinguish the person registering, participants, confirmed places and waiting-list places (in Polish), so a request to add someone is not confused with a confirmed place. A person adding a participant should recognise their situation without knowing departmental structure. They then need to know which information to prepare and how to tell whether the change was received for checking or completed.
In a B2B contact form (in Polish), check the purpose of fields and the answer after submission. A booking number may connect the request to the right case. A generic “describe the problem” field may lead to another round of questions. Every field still needs a reason in the subsequent action; collecting data just in case is not the same as good service.
Aeneia Design can help organise website information and the contact journey. Useful material includes specific places where a customer returns to the same question: the service description, form selection, confirmation or lack of a clear next step. The change can then address an identified obstacle.
If AI participates in responses, check controls on answers to complaints (in Polish) too. A tool may consistently refer people to unsuitable material if that is the basis it receives. Correct grammar and a quick message do not establish that the recipient received workable help.
Before making a change, retain the previous answer and an example of the screen it referenced. Afterwards the team can see what actually changed: the entry name, information scope or subsequent action. This helps distinguish new wording from removal of the obstacle. If several things changed at once, do not attribute the entire later outcome to one selected change without further evidence.
Test new content on an ordinary customer question. Show someone outside the project the scenario of adding a participant and ask them to identify the next step. Observe their understanding of names and the confirmation after submission. Their answer does not replace reviewing real cases, but can reveal an obvious ambiguity before changing the whole site.
Assess the fix through what happens next
After the change, examine a few new requests of the same kind. Does the customer find the right entry? Can the employee perform the next step without collecting the same information again? Does the confirmation match what was actually done? Retain cases that still return, together with their reason. They are material for further investigation, not awkward exceptions to erase from a chart.
If the company previously sent someone the wrong way, changing the page alone may not suffice for that case. Repairing the relationship after a service error (in Polish) requires explaining the particular obstacle and bringing the person to a possible next action. The fix should fit what they actually encountered.
Insights from contacts may also help explain lost B2B proposals (in Polish) when similar ambiguities appear before purchase. Do not, however, turn every returning request into evidence of lost sales. First establish the need the customer was trying to resolve. In our example, a good outcome is a properly added participant who receives the right course information. Victory for the email department would be considerably less useful.











