Skip to main content

Service Recovery and Public Response

Use this runbook when a client reports a consequential problem, a complaint becomes public, or the team is unsure whether a project issue needs a public response. It is not a crisis-performance script and it does not replace the contract, warranty, insurer, counsel, or a qualified safety professional.

1. Triage the consequence​

First contain urgent harm. Identify whether the issue touches safety, active property damage, code, contract, warranty, insurance, privacy, harassment, or another matter that needs an authorized professional path.

Pause scheduled promotion about the affected work when continuing would be misleading or insensitive. Preserve records. Do not remove legitimate criticism, coach a false account, promise compensation, admit fault, or publish project details before the authorized fact path is clear. Threats, harassment, personal information, spam, or potentially unlawful content follow an approved moderation or legal path after the evidence is preserved.

2. Separate the evidence states​

Record these separately:

  • what the client or public post alleges;
  • what the team has directly observed;
  • what remains unknown;
  • what decision has been made;
  • what action is underway; and
  • what resolution has been verified.

An acknowledgment is not a factual conclusion. Calm language can validate the person's experience without declaring facts the team has not established.

3. Assign the owners​

Name the project owner, relationship owner, executive or professional escalation, and communication approver. One person should coordinate the response so the client does not receive conflicting messages.

The first useful private response should:

  1. acknowledge the concern;
  2. state the known facts without speculation;
  3. identify what must be checked;
  4. name the owner and next update; and
  5. provide a direct path for the client to continue the conversation.

Do not force every event into a universal response-time promise. Set a specific next update that matches the actual risk and investigation.

4. Decide whether a public response is needed​

Private recovery and public communication are separate decisions. A public response may be useful when an issue is already public, materially affects others, or silence would leave a consequential false impression. It is not automatically useful because the team wants to defend itself.

If responding publicly:

  • reveal no private household, project, financial, contract, personnel, or safety detail;
  • avoid arguing about evidence in a review thread;
  • state only what is known and approved;
  • invite a private continuation without using it to suppress public feedback; and
  • correct the public record later only when the resolution is verified and appropriate to share.

Never route only happy clients to public review sites or make removal/change of a review a condition of service recovery.

5. Accept the recovery and capture learning​

Recovery is not complete because a reply was sent. Accept it only when:

  • the client received the plan and knew the owner and next update;
  • promised actions were completed or formally transferred to the authorized path;
  • the team verified the resolution it claims;
  • public language, if any, exposed no private project detail;
  • unresolved items and future commitments remain visible; and
  • the operating lesson reached the responsible process owner.

The learning may change an SOP, expectation, qualification rule, brief, training item, or client-communication practice. It does not need to become public content.

Use this with Client Experience, Feedback, and Referral. Keep the recovery record in the client system, not in the public playbook.