Client Escalations
"How we assign contact points, run calls, and document resolutions during client crises."
Haider NadeemWhy this exists
Escalations happen when clients feel ignored, not just when systems fail. The correct response is clear communication and a plan, not defensiveness. This process ensures engineers don't have to invent a crisis response under pressure.
Operational Flow
Identify escalations: Treat direct complaints or indirect signs (like copying their CFO on emails or tagging multiple stakeholders in Slack) as escalations.
Assign a lead: Name a senior engineer or project lead to own the issue and notify the client within two hours.
Schedule a call: Book a sync within 24 hours. Acknowledge the problem, explain current work, and set the next update time.
Avoid defensiveness: Read drafts aloud before sending. Focus on facts and next steps, not excuses.
Write a resolution summary: Send the client a summary explaining what broke, how we fixed it, and how we will prevent it.
Log the incident: Create a Linear ticket tagged 'escalation' to record the timeline and root cause.
What good looks like
- An angry email at 4pm receives a response by 5pm naming the owner and proposing a meeting for the morning.
- The escalation call lasts under 30 minutes, and the client receives a written resolution summary by 5pm.
- Quarterly reviews identify communication patterns in escalations, leading to better status update routines.
What NOT to do
- Don't send escalations to a shared inbox. Name a single person responsible for the client.
- Don't explain why a failure happened before acknowledging the client's frustration.
- Don't skip the written summary because the call seemed to go well. Verbal agreements fade.
- Don't invite the entire engineering team to the call. Having more than two representatives looks disorganized.
Escalations measure the gap between expectation and reality. When a client gets angry, the impulse is to explain the technical details. That is a mistake. They aren’t angry because they don’t understand the system. They are angry because they feel no one is managing the problem. Your priority is to put a named person in control.
The resolution summary is the most critical step. A client who gets a clear explanation of what we changed can move on. A client who only gets a call will worry about whether we fixed the root issue. Write the summary, keep it short, and send it before the end of the day.