AI Agent
AI agent is a software component that perceives input (an email, a PDF, a CRM record), reasons over it using a large language model, and executes a bounded action such as updating a ticket or drafting a reply. Unlike a simple classifier, an agent can chain multiple steps: read a shipment-delay email, query the logistics API, and post a status update to the customer via Google Workspace. For a 200-person German insurer, an agent might handle 60% of routine status inquiries without human intervention, reducing the cost per support ticket from EUR 10 to EUR 3. The EU AI Act requires that users be informed they are interacting with an AI system, and that any action affecting policyholder rights be subject to human review.
Before/After Baseline
Before/after baseline is a measured comparison of key operational metrics (cycle time, error rate, cost per ticket) captured before and after an AI automation deployment. In a two-week integration sprint, the baseline is recorded during the first three days of the process audit, then the automation is deployed, and the after-metrics are measured over the remaining ten days. For a German insurer automating document extraction, the baseline might show 12 minutes per document with a 4% error rate; the after-metrics might show 90 seconds per document with a 1.2% error rate. The baseline is the contractual deliverable of the pilot: it proves the automation delivers measurable value before the client commits to a full rollout.
Cost Per Support Ticket
Cost per support ticket is the total cost (labor, tools, overhead) divided by the number of tickets resolved in a given period. For a 201-500 employee German insurer, the baseline cost per ticket for manual handling is typically EUR 8-15, depending on complexity and the number of system lookups required. By deploying an AI agent for routine inquiries—status updates, document requests, first-response drafting—the cost for automated cases drops to EUR 2-4 per ticket. Complex cases (disputes, claims decisions) remain at the manual rate. The overall blended cost per ticket decreases by 30-50% as the automation rate increases. The metric is tracked weekly during the pilot and monthly during managed operation to ensure the savings are sustained.
Document Extraction
Document extraction is the process of converting unstructured or semi-structured documents (invoices, policy PDFs, shipping manifests) into structured data fields. In insurance, this typically means pulling claim details, premium amounts, or shipment tracking numbers from incoming documents. Using an LLM-based extraction pipeline, a 201-500 employee insurer can reduce manual data entry from 12 minutes per document to under 90 seconds. The workflow is human-in-the-loop by default: the model extracts and classifies the fields, and a person approves any field that touches money, health data, or a contract. The extraction accuracy is measured against a labeled test set during the pilot, with a target of 95%+ field-level accuracy before the system is considered production-ready.
EU AI Act
EU AI Act is the European Union’s regulatory framework for artificial intelligence, effective in phases from 2025. It classifies AI systems into risk tiers: prohibited, high-risk, limited-risk, and minimal-risk. Customer-support chatbots and document-extraction tools generally fall under ‘limited risk,’ requiring transparency (users must know they are interacting with AI) and data-governance measures. If the AI influences underwriting or claims decisions, it may be ‘high risk,’ triggering conformity assessments. For a German insurer using OpenAI API for ticket triage, the primary obligations are to disclose AI involvement to customers, maintain a log of AI decisions, and ensure human oversight for any action affecting policyholder rights. Non-compliance can result in fines up to 7% of global annual turnover.
Google Workspace Integration
Google Workspace integration means connecting AI agents to Gmail, Google Drive, and Google Calendar via the Google Workspace API. For a 201-500 employee insurer, this allows AI agents to read incoming customer emails, draft replies in Gmail, attach extracted documents from Drive, and schedule follow-up tasks in Calendar. The integration is non-invasive: it does not replace the existing email or document management system but adds an AI layer that operates within the tools the team already uses daily. The API calls are authenticated via OAuth 2.0, and all data access is logged for compliance. The integration is typically completed within the first week of a two-week sprint, allowing the second week to focus on tuning the agent’s behavior and measuring the before/after baseline.
Human-in-the-Loop
Human-in-the-loop (HITL) is a design pattern where an AI system performs the initial processing (classification, drafting, extraction) but a human must approve any action that touches money, health data, or contractual obligations. For a German insurer, this means the AI agent can triage a ticket and draft a response, but a human must click ‘approve’ before the response is sent if it involves a refund, a policy change, or a claim decision. HITL is the default delivery model for Forfis engagements because it satisfies EU AI Act oversight requirements while still capturing 70-80% of the automation benefit. The approval step adds 15-30 seconds to the cycle time but is non-negotiable for regulated workflows. The human reviewer’s decisions are logged and used to fine-tune the model over time.
Leave a Reply