The Problem: Slow First-Response Times in Professional Services
Professional services firms in the UK, particularly those with 501-2000 employees, face a persistent challenge: slow first-response times on client tickets. This delay erodes client trust and increases operational costs. The root cause is often manual triage, where staff spend hours classifying and routing tickets, a process that is both time-consuming and error-prone. Forfis addresses this by integrating AI automation into existing systems, starting with a process audit to identify workflows worth automating. The focus is on ticket triage and routing, using predictive scoring to assign urgency and complexity scores to incoming tickets. This approach aims to cut first-response time by automating the initial classification and routing steps, allowing staff to focus on higher-value tasks. The pilot is fixed-scope, ensuring measurable outcomes within a six-month timeline, and integrates with existing tools like Slack or Microsoft Teams to minimize disruption.
Mechanism: How the AI Layer Works
The system operates on a model-agnostic architecture, using Anthropic Claude API for tasks requiring high quality and nuance, such as drafting responses or classifying complex tickets. For regulated data that cannot leave the client’s premises, open-weight models run on the client’s own hardware. The pipeline begins with document and data extraction, pulling ticket data from existing CRMs and helpdesks. This data is then fed into a predictive scoring model, which assigns a probability score to each ticket based on its content and metadata. The score indicates urgency, complexity, or the likelihood of requiring escalation. The system then routes the ticket to the appropriate team or individual, with a human-in-the-loop approval for any action that touches money, health data, or contracts. The architecture plugs into existing systems through APIs, ensuring minimal disruption and leveraging existing workflows.
Trade-offs: Model Selection and Human-in-the-Loop
The choice between using Anthropic Claude API and open-weight models involves trade-offs. Claude API offers superior quality and nuance, making it ideal for tasks like drafting responses or classifying complex tickets. However, it requires sending data to a third-party server, which may not be acceptable for regulated data. Open-weight models, running on client hardware, ensure data stays within the building, meeting compliance requirements like ISO 27001. However, they may lack the quality of proprietary models, requiring more tuning and maintenance. The human-in-the-loop approach adds a layer of safety but also introduces latency, as a person must approve certain actions. This trade-off is acceptable in professional services, where accuracy and accountability are paramount. The fixed-scope pilot model also involves trade-offs, as it limits the scope of the engagement but ensures measurable outcomes and reduces risk for both parties.
Recommendation: A Fixed-Scope Pilot for Ticket Triage
For professional services firms in the UK, the recommendation is to start with a fixed-scope pilot focused on ticket triage and routing. The pilot should include a clear process audit to identify the most impactful workflows, a defined before-and-after baseline on cycle time and error rate, and integration with existing tools like Slack or Microsoft Teams. The architecture should be model-agnostic, using Anthropic Claude API for high-quality tasks and open-weight models for regulated data. Compliance with ISO 27001 should be integrated into the architecture from the start, ensuring that the AI layer respects existing security controls. The pilot should run for 8-12 weeks, with continuous feedback loops to refine the model and address user concerns. This approach ensures a measurable outcome within the six-month timeline, reducing risk and building trust for a broader rollout.
Leave a Reply