Skip to content
Interface language: English
Imperium / Signal

After a service error, resolve the client's problem before repairing the company's reputation

Respond to a service error by addressing the client’s need, checking the remedy and reconstructing the workflow.

Article language: English

A stack of paper tied with a dark ribbon and a gold-coloured seal rests beside a pen.
In this article

The client received an apology, a discount code and assurance that their satisfaction is a priority. They still do not have the right file. Before polishing the tone of a message, establish what the person needs now and what the company can actually do.

Repairing a case includes the concrete effect, communication with the client and changes intended to reduce recurrence. These can proceed in parallel but do not replace one another. An internal cause analysis does not deliver the correct material; a new file does not automatically tell the client whether they can still use it in time.

An error affects someone else's plans

Imagine a fictional studio editing a company podcast. The client approved corrections, but the studio delivered a version missing one agreed change. Publication was planned for the next morning, and the company learns of the error from the client. This ordinary service example does not decide legal claims or the financial settlement of a real order.

Confirm what happened and what the client has. Is it the wrong file, or the right file with the wrong name? Has it already been used? Which change is missing? “A problem with the final version” is too vague to safely send another attachment.

The UK Parliamentary and Health Service Ombudsman's principles distinguish explanation, apology and remedial action, including changes to material or service. They concern public bodies within its remit. A service business can use them to organise questions, not to decide a client's legal case.

A new export may work if publication has not happened and the client has time to check it. If the material was already used, find out what can still be changed and what help is useful. Repeating the original action does not restore the original conditions.

An apology should name the event

The Local Government and Social Care Ombudsman's remedies guidance discusses acknowledging a mistake and its effect and apologising in one's own words; it criticises formulas expressing regret only that a complaint was made. This public-sector standard is an example of specific communication, not a universal legal ruling for the studio.

“We are sorry the file did not meet expectations” is unclear when an agreed correction was omitted. A more useful message names the fact and next step: “We delivered the version without the approved change. I am checking the correct material and will return at 14:00 with confirmation of what we can deliver.” Promise that update only when it can be arranged.

Do not present a blamed employee as the solution. The client needs a contact able to move the case forward. Investigate internally using facts. The Polish guide to reporting errors in a team (in Polish) concerns the internal route; communication with the client also needs a clear scope. If a consultant cannot approve a remedy, provide a quick route to the right authority and pass on the state, agreements and expected time so the client need not repeat the story.

Distinguish a confirmed error from its still-unknown reach. The studio can acknowledge the wrong version of one episode while checking the rest of the series. It need not delay the necessary fix until the whole review is complete, but must not prematurely close the question of other files.

Say who will return with information and where the client can report a changed situation, such as a rescheduled publication or a file already sent to a partner. That may alter the usefulness of a remedy; the original schedule alone may no longer describe the client's situation.

Check whether a proposed remedy is useful

A company may be able to repeat the work but not know what the client now needs. Ask which moment or action depends on the correction: publication, delivery to a partner or an internal listening copy may require different agreements.

Offer something feasible. If a corrected segment can be prepared quickly but the complete export and listening check need more time, explain this. The client can judge whether a partial result helps. Do not call it a full remedy before its scope is understood and the result checked.

Avoid creating another round of work for the client. An ambiguously named file requires comparison; a corrected segment without its location makes review harder. A fast export matters only if the recipient can use it.

If a completion date is not known, the Polish guide to communicating a delay (in Polish) discusses stating the confirmed position and the time of the next update. Follow up even if the result remains incomplete. Waiting silently for good news increases the recipient's work.

Aeneia conceptual photography

The original result may have lost its use. A corrected episode cannot turn back time after the related event has finished. Agree what action still makes sense rather than forcing acceptance of the technical correction as the only way to close the discussion. Settlement and existing obligations need separate, appropriate consideration.

Separate what the firm can confirm itself from what another party must do. The studio can prepare a file, while replacement on someone else's channel may depend on its operator. Explain whether the client receives a finished result or a proposal requiring further confirmation; do not promise on behalf of a third party.

If the client rejects a proposed option, ask about the specific obstacle: missing information, a different format or an action the company cannot perform. Repeating the same offer more warmly will not explain why it fails to fit the current situation.

One person leads the case; several may fix it

An editor checks the material, an account contact speaks to the client and someone else listens to the new version. Identify who collects the information and confirms the next action. Otherwise every part can look complete while nobody has the full picture of readiness.

The Polish guide to a process owner's responsibilities (in Polish) distinguishes maintaining a way of working from leading one case. In a small firm the same person may do both. It should still be clear who is helping the client now and who will later improve version control.

Check the correction against the actual agreement. A successful export is not enough: confirm that the approved podcast change is present and identify the version being delivered. The necessary check depends on the service and error, not a universal checklist.

Record whether the previous material has been replaced. A recipient with several copies needs to recognise which one to use. The Polish article on correcting published company information (in Polish) discusses making a change visible where it is used; for a privately sent file, a clear message and version label serve a related purpose.

When delivering the correction, say what changed and what was actually checked. Do not claim a check that nobody performed. If another difference appears during review, reassess its reach instead of hiding it as an insignificant change in a new attachment. Establish the fact and available option before explaining its real effect to the client.

Reconstruct AI's part in the workflow

Suppose the studio uses AI to prepare a list of corrections from a conversation. If the model omitted an agreement, examine what it received, the result it generated and where a person was supposed to check it. “Automation was at fault” does not explain whether the gap was in the input, checking or handover.

The Polish guide to control of AI in complaints handling (in Polish) addresses a related use. A draft message can help organise communication, but should not independently confirm an unsettled remedy. A polished promise still needs a real basis.

AI's presence does not establish the cause. It may have received incomplete input or produced a correct list from which a person used an old version. Preserve the sequence and distinguish the tool's output from later action. Then consider changes to the source, handover or check based on evidence and alternative explanations, not merely the technology's name.

Close against the need the client brought

After delivery, check what was accepted as done and what remains open. Acknowledging receipt of a file does not necessarily confirm the scope of the correction. Do not treat every “thank you” as confirmation of every aspect; record important agreements unambiguously.

If a client returns with the same question, review the repair path. They may have received the right file without instructions for using it, or the contact may have been closed while the case was passing to another person. This is a reason to inspect a specific point, not automatic proof that the client is difficult.

Try a changed check on a later similar case. In the studio, version checking before delivery should work in the real workflow, including when someone is covering for a colleague. A “checked” field alone does not prove quality; the reviewer needs the basis and scope of the check.

Once the situation is stable, a Polish guide to turning a retrospective into practice (in Polish) can help connect a change to the identified cause: version visibility, receipt of the corrections list or confirmation after execution. Tell the client what actually changed. One repair cannot support a guarantee that the same error will never recur.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear