after we build · part seven
The Ongoing Relationship
Support levels, escalation paths, helpdesk metrics. SLAs as operational contracts that bind the chain to reality. Client cadence. Where the chain meets the people who pay for it — and where meaning's gaps cost real trust.
CS standup — daily or weekly, tickets reviewed, patterns surfaced to PO. Escalation happens in real time when a ticket crosses a level boundary. Weekly PO review of CS-origin bugs for pattern detection.
Support is a signal collection system for reality
Volume IV handed CS a briefing before the release. That was the beginning, not the end. Support is not a service layer. It is the team's closest ear to the person's actual experience — the reality that the prediction was built to change.
Three levels of support
Not every ticket needs the same response. Support is structured in levels — each with a different responder, a different resolution scope, and a different escalation trigger.
L1 · First contact
- Who: CS team.
- Resolves: known questions from the CS handoff, account issues, password resets, "how do I" guidance.
- Escalates when: the answer is not in the handoff, the ticket describes unexpected behaviour, or the user reports data that looks wrong.
- SLA target: first response within 1 hour during business hours.
L2 · Investigation
- Who: QA or a developer with domain context.
- Resolves: bugs that can be reproduced, configuration issues, workarounds for known limitations.
- Escalates when: the issue affects multiple users, involves data integrity, or requires a code change.
- SLA target: investigation started within 4 hours, resolution or escalation within 1 business day.
L3 · Engineering
- Who: the development team.
- Resolves: code fixes, schema issues, integration failures. Follows the bug taxonomy and the hotfix path from Volume IV.
- SLA target: P0 triggers incident process immediately; P1 same day; P2 enters normal backlog.
The support-to-bug pipeline
When L1 encounters a ticket not answered by the handoff, it becomes a JIRA bug with the full taxonomy — severity, impact, area. CS doesn't diagnose chain levels — they file what they see.
The PO reviews CS-origin bugs weekly and looks for patterns. Three tickets about the same confusion is not three bugs. It is one observation-mismatch the brief didn't anticipate. That pattern feeds the model update.