part seven · the ongoing relationship
The Ongoing Relationship
Support levels and escalation. The SLA as operational contract. Helpdesk metrics. Client cadence. Where the chain meets the people who pay for it.
Support runs continuously, three levels. Weekly client update every Friday — same time, same shape, written. Bi-weekly sync every other week — signal readings, decisions, scope changes. Quarterly portfolio review — SLA performance, VRI trends, root-cause patterns.
A feature shipped is not a relationship. A relationship is what happens between cycles, every week, around the work. This part of the volume is about the parts of the chain that have no kickoff and no end — the cadence that holds when the project room is empty.
Three levels of support
Support is layered so that the chain stays clear about who handles what — and so that signals from the field reach the team that can do something about them.
| Level | Who | Resolves | Escalates when |
|---|---|---|---|
| L1 | CS Lead, frontline | Configuration, account, how-to, known-issue lookup | Issue is reproducible and not in the known-issues doc |
| L2 | QA + on-call developer | Reproducible defects, environment issues, data corrections | Fix requires code or schema change, or is a P0/P1 incident |
| L3 | Tech Lead + PO | Code-level defects, structural issues, scope decisions | Repeated pattern triggers a chain-level review |
The escalation path is in the runbook. CS does not page L3 directly. L3 hears about L1 patterns through L2's weekly summary.
Support-to-bug pipeline
Every L1 ticket is candidate evidence for the bug taxonomy. The PO reviews CS volumes weekly, asking three questions:
- Is this a single occurrence or a pattern? Patterns escalate to L2 immediately.
- What chain level does this trace to? Disproportionate weight in any one level is a structural signal.
- Is the help text the bug? A common L1 question often means the content design — not the code — is the gap.
The output is a small number of new bugs filed each week, classified by chain level. CS volume that isn't producing bugs is a sign of an over-staffed or under-listened-to support team.
SLA — the operational contract
The SLA is what the team has promised the client and is willing to be measured against. Four dimensions, every contract:
- Availability — uptime, with the maintenance window written.
- Response time — how long until L1 acknowledges. By severity.
- Resolution time — how long until L1 resolves, or escalates with a target. By severity.
- Data integrity — the team's promise about the data the client trusts to it.
The SLA is not a marketing document. It is the threshold past which someone is paged, and the conversation that opens with the client when it is breached.
The breach protocol
The SLA is breached the moment a threshold is crossed, not the moment someone notices. The protocol:
- Early warning — the dashboard shows the threshold approaching. A communicator (PO or CS Lead) reaches out before breach. We are seeing X. We are doing Y. We will tell you Z by W.
- Contain — same containment levers as Volume V Part 4. Flag, deploy rollback, migration rollback, data correction.
- Communicate — every 30 minutes minimum during a P0/P1 SLA breach. Status page is updated.
- Resolve — the breach is over when the SLO is back inside threshold and the client has been told it is over.
- Postmortem — same week. SLA breaches are always P-level enough to warrant the structural-fix discipline.
The SLA review
Quarterly, with the client. Three questions:
- Did we meet the SLA? Numbers, not impressions.
- Where did we approach without breaching? Leading indicators.
- Are the categories still right? The thresholds were written against a model of the world that may have moved.
An SLA reviewed quarterly stays a contract. An SLA never reviewed becomes a souvenir.
Helpdesk metrics
Tracked monthly. Reviewed in the bi-weekly sync.
| Metric | What it tells you | What "wrong" looks like |
|---|---|---|
| First Response Time (FRT) | Whether L1 is keeping pace | FRT trending up — L1 is overloaded or under-tooled |
| Resolution time | Whether problems are getting fixed or routed | Resolution >> FRT — L1 is queueing instead of solving |
| Escalation rate | Whether the right work is reaching L2/L3 | Very low — L1 is over-resolving and missing patterns. Very high — known-issues doc is stale |
| Categories | Where pain concentrates | One category >40% — that's the next slice |
| Ticket-to-bug conversion | How well the support pipeline feeds the chain | Zero in 30 days — the pipeline is closed |
| Satisfaction (CSAT) | The relationship at the ticket level | Low CSAT with good resolution time — tone, not speed, is the gap |
Client cadence
The cadence is part of the work, not extra to it. The cadence is what makes the work answerable.
Weekly client update — written
Every Friday. Same time, same shape. Three sections: what shipped, what is in progress, what is blocked. Written by the PO, before the team's Friday wrap, in under 200 words. The discipline is consistency, not eloquence. A client who reads ten weekly updates that look the same has a model of the team. A client who reads ten weekly updates that look different has anxiety.
Bi-weekly sync — spoken
Forty-five minutes. Signal readings (any from the last two weeks), roadmap (any changes), scope decisions (any), CS patterns (any). The PO drives. The Tech Lead is present. The client speaks last.
The agenda is fixed. The sync that becomes a discussion of feature requests is a sync that has lost its job. Feature requests go into the backlog through the backlog process. The sync is for state.
Quarterly portfolio review
The longer view. The PO and the Tech Lead sit with leadership and (where the relationship supports it) the client. Three artifacts on the table:
- SLA performance — did we meet, where did we approach, are categories right.
- VRI trends — value-to-rework. Is the chain producing more of what was paid for, or less?
- Root-cause patterns — chain-level distribution of bugs and incidents. What level keeps producing the misses?
The review's output is a portfolio decision — fund, continue, or kill, and what to invest in chain repair.
Enough to know the relationship is held.
Three support levels are staffed and routing. SLA is current and reviewed within the last 90 days. Weekly update has been sent on schedule. Bi-weekly sync has run. CS-to-bug pipeline produced at least one bug last month.