Cutting First-Response Time by 55%: AI Ticket Triage for a 30-Person UK Insurer

The Problem: 18-Minute First Responses and a 30-Person Team

A 30-person UK insurer handling 200 support tickets a day faces a familiar problem: first-response time sits at 18 minutes on average, and the cost per ticket is climbing as agent turnover rises. The tickets are not complex — most are policy status checks, document requests, or routine claim updates — but they consume the same agent time as a disputed claim. The insurer has already automated one process: invoice processing. The next target is the support queue, where the volume is highest and the margin for error is lowest.

The constraint is not technical. The insurer runs a standard helpdesk, a CRM, and a Confluence workspace with 400 pages of policy documentation. The constraint is compliance: UK GDPR, specifically Article 22, requires that no decision with legal or similarly significant effect be made solely by automated processing. A ticket that triggers a claim denial, a premium adjustment, or a policy cancellation cannot be resolved by an AI without human review. The architecture must reflect that boundary from day one.

The engagement is scoped as a 3-month integration sprint: a two-week process audit, a six-week pilot on ticket triage and routing, and a four-week rollout with measured before/after baselines. The AI layer sits on top of the existing helpdesk and CRM, not in place of them. It reads tickets, classifies them, retrieves context from Confluence, drafts a response, and routes the ticket to the right queue. A human approves anything that touches money, health data, or a contract. The model is Anthropic Claude, called via API, because the insurer’s data can leave the building under a standard data processing agreement, and the quality of the drafting and classification is the priority.

How the Pipeline Works: From Webhook to Human Review

The pipeline has five stages, each mapped to a specific API call or internal function:

1. Ingestion. The helpdesk webhook fires on every new ticket. The payload includes the ticket ID, subject, body, policy number, and customer ID. The system parses this and normalizes the fields.

2. Classification. The ticket body and subject are sent to the Anthropic Claude API with a system prompt that defines the taxonomy: claim, policy change, document request, billing, other. The model returns a JSON object with the category, a confidence score, and a suggested urgency level. The taxonomy is fixed; the model does not invent categories.

3. Retrieval. The policy number and issue type are used to query the Confluence workspace via its REST API. The relevant pages are pulled, chunked, and embedded. A vector search returns the top three passages. This step runs in under 400 ms.

4. Drafting. The ticket body, the classification, and the retrieved passages are sent to Claude with a second prompt that instructs it to draft a first response in the insurer’s tone. The draft includes a reference to the specific policy clause or FAQ article that supports the answer.

5. Routing and Review. The ticket is routed to the correct queue based on the classification. If the category is claim, billing, or policy change, the ticket is flagged for human review. The human sees the AI’s draft, the classification, the retrieved context, and a one-click approve/edit/reject interface. The audit log records the ticket ID, the model version, the prompt hash, the human’s action, and the timestamp.

The whole pipeline, from webhook to human review screen, takes under 3 seconds. The human review step adds 2-5 minutes for routine tickets and 10-15 minutes for flagged ones.

Trade-offs: Model Choice, Human-in-the-Loop, and Integration Depth

Three architectural choices drive the cost and compliance profile of this system.

Model choice. Anthropic Claude is used for the classification and drafting steps because the quality of the natural-language output matters. The insurer’s data is not regulated to the point where it cannot leave the building under a standard DPA. If the data had been health records or financial data subject to FCA rules, the architecture would have shifted to an open-weight model on the insurer’s own hardware, which would have added 4-6 weeks to the timeline for GPU provisioning and model fine-tuning.

Human-in-the-loop boundary. The AI drafts and classifies; a human approves anything that touches money, health data, or a contract. This is not a soft guideline. The system is built so that the approve button is the only path to sending a response for flagged tickets. The audit log is immutable and exportable for ICO inspection. This design satisfies GDPR Article 22 and gives the insurer a defensible position if a customer challenges a decision.

Integration depth. The AI plugs into the existing helpdesk, CRM, and Confluence via their APIs. It does not replace any of them. The insurer keeps its current tooling, its current data model, and its current access controls. The AI is a layer, not a platform. This keeps the integration sprint to 3 months instead of the 9-12 months a full platform replacement would require. The trade-off is that the AI is limited by the quality of the data in the existing systems. If the Confluence documentation is stale or inconsistent, the retrieval step degrades, and the drafting step produces lower-quality responses.

Recommendation: What to Do in the First 30 Days After the Pilot

The pilot measured three metrics over two weeks before and two weeks after the AI went live: first-response time, error rate, and cost per ticket. The baseline was 18 minutes for first-response time, a 7% misclassification rate, and a cost per ticket of £4.20. After the pilot, first-response time dropped to 8 minutes, the misclassification rate fell to 3%, and the cost per ticket dropped to £2.90. The 55% reduction in first-response time came from the AI handling the first 70% of tickets end-to-end, with the human only reviewing the draft. The 40% reduction in cost per ticket came from reduced agent time on routine tickets.

The rollout plan is straightforward. The AI is enabled for all new tickets in the support queue. The human review step remains for flagged tickets. The audit log is reviewed weekly by the compliance team. The Confluence documentation is updated quarterly to keep the retrieval step accurate. The model is re-evaluated every six months against a test set of 500 historical tickets to catch drift.

The key lesson is that the AI does not replace the agent. It changes the agent’s job from drafting every response to reviewing and approving AI-drafted responses. The agent’s skill set shifts from writing to judgment. The insurer should plan for retraining, not for headcount reduction. The 3-month sprint is a starting point, not a finish line. The next phase is to extend the same architecture to the claims queue, where the volume is lower but the complexity is higher, and the human-in-the-loop boundary is more critical.