Scope and Conventions
The following terms are defined in the context of a UK professional services firm with 501 to 2,000 employees that is deploying an AI ticket triage and routing system. The firm uses the OpenAI API for classification, integrates with Google Workspace for internal notifications, and operates under ISO 27001. Each entry gives a concise definition and a one- or two-sentence example drawn from the firm’s specific use case. The glossary is alphabetized and covers the full delivery cycle from process audit through managed operation.
A through D
Before/After Baseline is the measured comparison of cycle time and error rate before and after the AI layer goes live. In the firm’s pilot, the baseline is a 200-ticket sample scored for misrouting and a 10-business-day window tracking median time from ticket creation to first human action. The delta between the two measurements is the primary metric the firm uses to justify rollout to additional departments.
Data Enrichment and Cleanup refers to the automated step where the AI model fills in missing fields on a ticket, such as client name, service line, or urgency level, by extracting them from the ticket body and cross-referencing the CRM. In the firm’s workflow, this step reduces the time a senior associate spends re-keying information from a client email into the helpdesk, freeing roughly 12 minutes per ticket for higher-value work.
Dedicated AI Team is a fixed group of engineers and a product owner assigned to the firm for the duration of the engagement. The team handles the process audit, builds the pipeline, runs the pilot, and manages the system after go-live. The firm’s internal IT team retains ownership of the helpdesk and Google Workspace configurations, so the AI team’s role is additive rather than replacing existing staff.
Document and Data Extraction Pipelines are the automated workflows that pull structured data from unstructured inputs such as client emails, PDFs, and ticket bodies. In the firm’s case, the pipeline extracts the client’s name, the service requested, and the deadline from a free-text ticket, then writes those fields into the helpdesk record. The pipeline runs on every new ticket and takes under 2 seconds to complete.
H through O
Human-in-the-Loop is the default operating mode where the model drafts or classifies, and a person approves anything that touches money, health data, or a contract. In the firm’s triage system, tickets flagged as billing disputes, regulatory inquiries, or contract amendments are held for human review before routing. The approval step is a single click in a Google Workspace notification, and the model’s confidence score is displayed so the reviewer can decide in under 30 seconds.
ISO 27001 is the international standard for information security management systems. For the firm’s AI triage system, the standard requires that the data flow through the OpenAI API be documented in the risk assessment, that access to ticket content be logged, and that any PII in tickets be handled per the firm’s data protection policy. The system itself does not need certification, but the firm’s ISMS must account for the new processing path. A dedicated AI team typically maps the triage workflow to the relevant Annex A controls before go-live.
Model-Agnostic Architecture means the triage layer calls the OpenAI API for classification and extraction, but the surrounding orchestration is built on standard APIs. If the firm later needs to move to an open-weight model on its own hardware for data residency reasons, the prompt templates and routing logic transfer without rewriting the integration layer. The dedicated AI team designs the abstraction so that swapping the model provider is a configuration change, not a re-architecture.
OpenAI API is the hosted interface to OpenAI’s language models, used here for classification and extraction. The firm’s ticket content is sent over HTTPS, and the response is processed locally. No training data is retained by OpenAI under the standard API terms, but the firm should confirm the data processing agreement covers its specific use case. The API is chosen for its strong performance on English-language text and low latency, typically under 800 milliseconds for a classification call.
P through T
Process Audit is the first step in the engagement, where the AI team reviews the firm’s existing ticket workflow to identify which categories have the highest volume and the most inconsistent routing. The audit produces a one-page report listing the top three candidates for automation, with a projected time saving per ticket. In the firm’s case, the audit identified billing inquiries, project status requests, and contract amendments as the three highest-volume categories, with billing inquiries showing the most variance in routing decisions across different shifts.
Scaling Across Departments means extending the triage logic from one department to others by parameterizing the classification rules per department. The marketing team’s tickets and the legal team’s tickets use different classification rules but the same underlying model and integration layer. The firm’s 501 to 2,000 employee size means there are typically four to six departments that generate tickets, and the rollout plan sequences them by volume so the highest-impact departments are automated first.
Ticket Triage and Routing is the automated step where the AI model classifies the ticket’s intent, urgency, and department, then routes it to the correct queue or agent. The model does not draft the customer reply in the triage stage; it only determines where the ticket goes and what metadata to attach. This keeps the first-response SLA intact while freeing senior staff from the sorting step. In the firm’s workflow, the routing decision is written back to the helpdesk API, and a Google Workspace notification is generated if human review is required.
4-Week Pilot is the fixed-scope engagement that delivers a working triage system on one ticket category. Week 1 covers the process audit and baseline measurement. Week 2 builds the extraction and classification pipeline against the OpenAI API. Week 3 runs the model in shadow mode on live tickets, comparing its routing decisions to human ones. Week 4 measures the before/after delta and documents the handoff to managed operation. The timeline assumes the firm’s helpdesk API is accessible and that a named business owner is available for daily check-ins.
Leave a Reply