By Dr. Sheila Viesca
The customer knows the reference number, the missing document, the department holding the request, and the name of the employee who promised an update. They have assembled this knowledge across several calls. When they contact you again, they explain the case from the beginning and remind your team what was supposed to happen.
At that point, the customer is coordinating part of your operation. Every employee may have been courteous. The organization has still left somebody outside it responsible for connecting the work. I would examine that burden before asking frontline staff to make their conversations sound more reassuring.
The work the customer has inherited
TalkShop’s Sales Academy includes customer service, consultative selling, negotiation, and assertive communication. Its work competencies offerings also cover customer complaints handling. These subjects belong together because the ability to handle a conversation must be supported by the ability to carry the matter forward.
For leaders, one useful service question is: what does the customer have to remember, repeat, or chase because our own people have not coordinated?
Consider a billing correction moving through three teams. The first records the request, the second checks the documents, and the third authorizes the adjustment. Each team completes its assigned action and marks the task accordingly. Yet the customer cannot discover when the adjustment will appear. Internal completion has not produced an answer they can use.
The next call is then described as another inquiry, as though it began independently. It actually belongs to the same unfinished experience. The customer has to recover the history because the organization has not carried it forward. This is a useful place to begin a review: follow the unresolved commitment, rather than treating each contact as a separate conversation to be handled politely.
Ask the customer’s practical questions at each stage. Who has the matter now? What is being checked? What information is still needed? When will there be another update? An employee may not be able to promise the final outcome, but the organization should examine whether it can provide a dependable next step. That is often where service communication becomes operationally useful.
A commitment has to survive the handover
Responsibility for the update needs to survive the transfer between teams. Otherwise, the customer receives the name of a department while the department receives only another task. Neither receives a dependable commitment about what happens next. I would make that commitment explicit before considering the handover complete, including who will respond if the review takes longer than expected.
A useful handover should tell the receiving employee:
· What the customer needs and what has already been verified.
· Which supporting documents are available.
· What commitments have been made and when they fall due.
· Who owns the next action and who will update the customer.
Ownership becomes clearer when it is attached to a specific commitment. “Customer service is handling it” may identify a department without identifying who will provide the next update. When a case moves to another team, establish whether the first employee remains the customer’s contact or whether responsibility formally transfers. Either arrangement can work if the people involved understand and follow it.
In the billing example, the receiving employee needs to know that the customer has already supplied the receipt and was promised an update on Thursday. Those facts change the next conversation. Asking for the receipt again or offering a new timeline without acknowledging Thursday would make the customer repair the organization’s memory. The handover should prevent that unnecessary reconstruction.
The owner also needs a way to obtain internal information. It is unreasonable to assign responsibility for updates while leaving the employee unable to see the case or contact the deciding team. Define the escalation route and the point at which a delayed response requires management attention. A named owner becomes useful when the surrounding workflow allows that person to fulfill the commitment.
An internal handover should therefore include the promise already made to the customer. Without it, the receiving employee inherits the task while the customer remains responsible for remembering the commitment.
What progress should make clear
Research by Ryan Buell, Ethan Porter, and Michael Norton offers a useful perspective. Their studies of government service transparency found that making work visible could increase trust and engagement. One field study involved Boston residents receiving photographs of work addressing their service requests. Those findings concern the settings studied. Transparency still needs to reflect actual service delivery. The important distinction is between showing actual progress and merely announcing activity. [1]
Consider a customer waiting for a billing correction. ‘We have already forwarded your concern’ describes an internal action. It leaves the customer wondering who is handling it, when to expect an answer, and whether another follow-up will be necessary.
A more useful response would be: ‘Our billing team is reviewing the duplicate charge. I will update you by 3 PM tomorrow, even if the review is still ongoing. You can reply to this thread if you need to add information.’ This gives the customer a clear point of contact and a realistic update commitment.
A useful update explains what has been verified, what remains pending, and what the customer can expect next. If nothing has changed, acknowledge that plainly and explain the next review point. Inventing progress to make an update sound reassuring creates a second problem when the promise cannot be supported. Honesty about a delay gives the customer a better basis for planning.
A status update earns its place when it changes what the customer can understand or plan. “The documents have been checked; authorization is still pending” distinguishes two stages. It does not promise approval. The customer can see what has happened without being asked to interpret an internal phrase such as “forwarded for appropriate action.” That distinction protects accuracy while making progress intelligible.
If nothing has changed, say so plainly. “The supporting record is still being reviewed. I will update you again on Thursday” is more dependable than suggesting that completion is imminent without evidence. A scheduled update is a commitment in its own right. Keep it even when the final answer remains pending, and explain any revised timing before the customer has to ask.
Operational transparency requires judgment. Some information may be confidential, uncertain, or irrelevant to the customer’s decision. Sharing every internal activity can create noise rather than clarity. Select the information that explains the status and the next step. The standard is whether the communication helps the customer understand what is happening, not whether it makes the organization appear constantly busy.
Repeated requests for documents can create frustration when the customer believes they have already complied. Before asking again, check what has been received and whether another employee can access it. If a replacement is necessary, explain the specific reason. A request to resubmit a document should identify what is missing or unsuitable rather than making the customer guess why the earlier submission was insufficient.
Where several items are required, provide one clear list when the process allows it. Distinguish mandatory information from details that may become necessary later. Explain the accepted format and the appropriate submission channel. These details are part of service design. A courteous employee cannot fully compensate for an instruction that leaves customers uncertain about how to provide what the organization needs.
Review the sequence from the perspective of someone encountering it for the first time. An employee may know why an identity check, reference number, or supporting record is required. The customer may see only another obstacle. A brief explanation can make the request more understandable. It should be accurate about the requirement and avoid implying that the customer caused a delay created elsewhere.
A difficult answer still deserves a useful explanation
Review the language too. A response can acknowledge inconvenience without promising an outcome that has not been approved. Staff should know how to explain a limitation accurately and when to escalate a request. Asking them to improvise both policy and tone during a difficult call is an avoidable burden.
Frontline staff also need permission to be precise about limits. ‘I cannot approve that refund, but I can submit the request with the documents you have provided’ is more useful than an unsupported assurance. If a customer becomes abusive, a clear escalation procedure should protect the employee while preserving an appropriate route for resolving the issue. Responsibility for service includes responsibility for the people delivering it.
The first task in a complaint conversation is to understand the issue well enough to act. Let the customer explain what happened and what they are asking the organization to do. Identify the relevant record and clarify any material uncertainty. A quick apology followed by an incorrect promise can create a second problem before the original one has been examined.
When the billing team declines the request, the customer should not have to infer the decision from a policy attachment. State the outcome and the applicable reason. Explain the review route if one exists. The employee can be considerate while delivering an answer the customer dislikes. Concealing the answer beneath reassurance prolongs uncertainty and may create another avoidable contact.
A customer may disagree with the policy or the outcome. Provide the available review route where one exists. Do not invent an exception to end the call, and do not treat a reasonable request for review as personal hostility. If conduct becomes abusive, follow the organization’s escalation procedure. Protecting employees and resolving customer concerns both require clear standards and practical management support.
Service recovery also requires care when the answer is unfavorable. A declined request still deserves an explanation that addresses the customer’s actual concern. State the decision, identify the applicable reason, and explain any available review route. Avoid surrounding the answer with so much formulaic sympathy that the customer cannot tell what has been decided. Equally, avoid a bare policy statement that leaves them uncertain about whether their circumstances were considered.
Where the organization made an error, identify the correction that has been authorized and the person responsible for carrying it out. Distinguish the action already completed from the action still pending. If the customer must supply something further, explain why it is necessary and how to submit it. Follow through on the update commitment. A difficult answer can still be delivered with accuracy and consideration. The practical question is whether the customer can understand the position and decide what to do next without beginning the entire explanation again with another employee. That standard remains relevant even when the organization cannot provide the outcome the customer hoped to receive. The explanation should make that choice possible.
A service email should answer the question the customer actually asked. A template may contain accurate policy information while overlooking the specific concern. Before sending it, identify the requested outcome, the explanation needed, and the action available. Adapt the approved wording where necessary without changing the policy or creating a commitment the employee cannot authorize.
A template should be tested against the specific question, not merely checked for approved wording. In the billing case, the customer asked why the same amount appeared twice. A paragraph about payment channels may be accurate and irrelevant. I would ask which sentence actually addresses the discrepancy. If there is no answer yet, the response should describe the investigation rather than impersonate a conclusion.
Use ordinary language for instructions. Identify the document, deadline, recipient, and reference number where relevant. Avoid sending a long list of possible requirements without explaining which apply. The same discipline belongs in internal communication: the colleague receiving the case needs a usable account of the issue. A well-written handover can prevent several confusing exchanges later in the process.
Follow what remains unresolved for the customer
I recommend reviewing one recent complaint from beginning to end. Count how often the customer had to ask for progress. Examine where information was lost and where employees were waiting for a decision. Then decide which part of that process can change.
Look beyond the total time to closure. Examine how many times the customer contacted you, repeated information, or received an answer that did not address the question. These are proposed review measures, not universal benchmarks. Their value is diagnostic: they can show where the organization requires customers to compensate for its own gaps in coordination.
The completed-task count cannot tell this whole story. A department may close its part quickly while transferring an unresolved commitment elsewhere. A useful review follows what remained open for the customer after each internal closure. This is a proposed way to investigate the experience, rather than a universal metric. Its value is identifying a point where the organization can actually change the coordination.
Choose a small, representative group of recent cases. Reconstruct the sequence and identify where the customer had to do work that better coordination could have prevented. Check the context before assigning a cause. A repeated contact may reflect a genuine change in the request, an unclear instruction, or a missed update. Each explanation points toward a different improvement.
Discuss the findings with the departments involved. A service problem located between teams cannot always be solved by retraining the frontline employee. The review may reveal an approval delay, restricted access, or conflicting instructions. Agree on one specific change, identify who will implement it, and review comparable cases afterward. Improvement becomes easier to assess when the change and its intended effect are clear.
Customer service training can give employees practice in listening, explanation, questioning, and professional boundaries. It becomes more useful when the practice reflects the decisions they are actually authorized to make. Provide the relevant policy, a realistic case history, and a clear escalation route. The learner can then practice a response that would remain usable after the workshop ends.
In a practice exercise, I would ask the employee to handle the second contact, not only the first. Give them the earlier promise and the current record. Can they explain the delay without asking the customer to reconstruct it? Can they retain ownership of the next update? This tests the continuity of service that a polished opening greeting cannot demonstrate.
Managers should also listen to what the exercise reveals about the system. If experienced employees disagree about who approves an exception, clarify the authority. If a template repeatedly confuses customers, revise it through the appropriate process. Training can expose an operational issue as well as a learning need. The organization should be prepared to respond to both if it expects service to become more dependable.
Take one recurring complaint and trace the commitments across every team involved. Identify the moment the customer had to recover information, repeat a document submission, or ask who would respond next. Agree on a change that removes one of those demands and assigns the corresponding responsibility inside the organization.
Then imagine the customer putting the phone away. Can they return to their own work because your team has supplied a dependable next step? They should be able to benefit from your coordination without having to become its project manager.
Explore related TalkShop programs
TalkShop’s customer service and work competencies programs connect communication practice with the decisions employees handle. Explore the Sales Academy or inquire about a customized service development program.
Explore the relevant TalkShop offering
Posted by 
