Distil a long escalation thread for one stated reader, tie claims to the messages they came from, name who said what, and report what was dropped — then hand it to the escalation lead.
An escalation opens across several parties, and the thread is read as one record, not as its latest message.
02
A reader is named before a word is written, so the summary is compressed for that reader and says which one.
Reason
03
A claim enters the summary carrying the message it came from, so the original opens in one step.
04
A speaker stays attached to the words, because who said a thing in an escalation often outweighs what was said.
05
A customer sentence is carried across in the words it was written in, and not smoothed on the way up.
Decide
06
A summary is drafted, and what it left out is listed beneath it rather than left to be discovered.
07
A thread is still moving when it is summarised, and the summary says so instead of reading as final.
Out
08
A second escalation on the same account is summarised apart, and the two are not folded into one.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Summarising, attribution and the omission list belong to the agent. Severity, remedy and sending belong to a named escalation lead, who owns the summary once it leaves.
2Reader and window fixedWho the summary is for, the messages inside the window and the account the thread belongs to
3Summary drafted with sourcesThe claims, the speaker behind each one, the confidence and the omission list
4Controls appliedAttribution checks, quotation-fidelity checks, thread-boundary checks and summary confidence
No human action required
Stages 1 to 4 run unaided, and nothing is sent at any of them — the agent is summarising, and the lead lane opens at the fidelity gate.
5DecisionSplits at the fidelity gate
Fidelity within tolerance
Goes to the escalation lead to send.
Anything thin
Adds a senior support read first.
Escalation lead review
The summary is held with its omission list, its attributions and the thread it was drawn from.
Send · Restore detail · Send to lead review
Sent — by the escalation lead▼
6Ticketing and paging records updatedOnly where write access and records policy allow it
7Outcome evaluatedAttribution accuracy, restored detail, lead corrections and what review found
Corrections
Each escalation lead correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Setting the severity an escalation is worked at.
Judging whether the customer is in the right.
Committing the company to a remedy or a credit.
Releasing a summary to an executive.
Automation boundaryAgent acts unaided
✓Summarise the thread for the one stated reader.
✓Carry each claim forward beside its original message in the thread.
✓Name the person behind each claim, and quote them as they wrote it.
✓List what the summary left out, beneath the summary.
Nothing reaches an executive except by the escalation lead, inside the agreed boundaries.
Deciding an escalation is closed.
Telling an executive the account is safe.
Choosing which promise gets honoured first.
Changes to the readers, the rules or the thresholds.
Example output
One escalation summary, annotated
This serves a customer success team who may have to explain months later why one line never made it upward; below is one summary exactly as the agent leaves it.
Summary output · single escalationIllustrative example
Escalation
Summary says
Written for
Thread of record
Confidence
Held for
Delivery slip, enterprise account
Two dates missed and one promise repeated
An executive reader
Ticket thread, 6 August 2026
Held unsent
The escalation lead, by name
As receivedDrawn from the thread on file and the notes attached to it, and it claims nothing the thread does not.
What was left outRepeated status notesDuplicated repliesAn internal aside
Why nothing was sentSending a summary upward is a judgement the escalation lead makes.
ActionSendRestore detailSend to lead review
What the score decidesBelow the configured threshold a summary gets a senior read before the lead sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every escalationFrom the thread it lives in
03Thread
Where the thread is used
The agent does not rate how serious an escalation is, only what the thread says, who said it, and what the summary had to leave behind.
01Approved path
A summary drops something
Change the reader, the window or which messages count, and the same thread yields a different summary, with nobody having lied.
02Human review
What this page is not
A customer escalation is not a security incident: the operations incident-response agent keeps the company record of when it knew, while this reads what the customer wrote and says what the summary left behind.
04Build an evidence trail
The summary, the thread it was drawn from and the lead who sent it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Ticketing and supportZendesk · Salesforce Service Freshdesk · Jira Service Desk
Conversation channelsSlack · Teams · email threads Bridge calls and call notes
Account recordsSalesforce · HubSpot · Gainsight Account history and contract terms
Agent
Escalation summarisation
Reads the thread Writes the summary Holds for the lead
Paging and incident toolsPagerDuty · Opsgenie · Statuspage Incident timelines and pages sent
A severity-level fidelity figure can read clean while multi-party bridge threads carry most of the detail put back by hand. Nestack reports the restore rate by thread type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-party bridge threads
9.1%
3.7×
Review
Threads spanning weeks
6.5%
2.6×
Review
Reopened escalations
4.0%
1.6×
Watch
Single-team threads
1.8%
0.7×
Normal
Bar: restore-rate lift vs. single-team baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a dropped sentence costs
The loop closes when the detail dropped from a summary is a standing case. That suite is what the next summary sent is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Restore rate rises on multi-party bridge threads.
02Diagnose
The summary that reached the executive with the one sentence the customer cared about missing is worked backwards until one cause is left standing.
03Improve
The change leaves numbered, and the summaries that caused it ride with it.
04Verify
Nothing ships while one summary case is still failing.
05Learn
One case joins the suite, one line joins the summary rules.
Learn → DetectThe return edge. The next summary is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, summary drafting, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Escalation-summarisation and audience-boundary work.
02Ticketing, chat and paging sources.
03Escalation-attribution and audience-rule mapping.
04Escalation thread ingestion.
05Reader, claim and speaker binding.
06Fidelity scoring and review routing.
07Escalation lead release workflow.
08Ticketing and paging integration.
09Fidelity and omission cases.
10Guardrails and fidelity controls.
11Summary-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne account, one escalationProductionProduction escalation workflowAdvancedMultiple regions / products
Introduced at Pilot
Summarising to your stated readers✓✓✓
Escalation lead release✓✓✓
Escalation-history baseline✓✓✓
Introduced at Production
Reporting by severity—✓✓
Lead review workflow in your systems—✓✓
Approved write-back—✓✓
Ticketing-and-paging integration—✓✓
Introduced at Advanced
Multi-thread reconciliation——✓
Cross-region summary packs——✓
High escalation volume——✓
Multi-thread summary controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, escalation volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live escalation paths and who each summary is written for→Reader capture and attribution bindingWeek 1
02Representative escalation threads, closed and still open→Thread ingestion, claim binding and the summary baselineWeek 2
03Your escalation policy and the leads it names→Reader mapping, attribution binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Ticketing, chat and paging source assessment, then integration setupWeek 2
05Summaries you would not want compared→Omission cases and the evaluation runWeek 4
06What no summary may replace→Fidelity scoring, review routing, guardrails and release controlsWeek 3
07A named escalation lead who sends the summary→Release to the escalation lead, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Nothing here was rounded to the column edge; the overlap in week five is an overlap in the work.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Escalation discovery, reader mapping and the automation boundaryW2Source integration and the escalation-history baselineW3Summary drafting, fidelity logic and release controlsW4Evaluation suite, omission cases and failure-mode testingW5Ticketing and paging integration, pilot threads and targeted correctionsW6One escalation month run under the escalation lead, then Agent Care handover
Reading the bandA bar spans the weeks its own work is named in, and week five carries two by design.
At the end of W6When the summary record validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Customer Success AI agent
Build an escalation summarisation agent around the sentence your last summary left out.
Show us one escalation you had to summarise upward, and the summary that went. Who was it written for — because where no reader is stated, the summary serves whoever the model imagined, and the sentence that mattered goes without anyone choosing to drop it.
