1. Start with a Process Audit, Not a Model
Before writing a single line of code, Forfis runs a process audit across the firm’s back-office workflows. For a 201-500 person professional services company in the UAE, this means mapping every step in order intake, shipment tracking, and client communication. The audit measures baseline cycle time and error rate for each workflow — not estimates, but logged timestamps from the existing Zendesk or Intercom queue. The output is a prioritized roadmap: which workflows to automate first, which to defer, and what the success metrics will be. This step takes roughly five working days and costs a fixed fee. It prevents the most common failure mode in AI projects: building a solution for a workflow nobody actually uses.
2. Scope the Pilot to One Workflow
The pilot targets order and shipment status updates — the highest-volume, lowest-complexity workflow in most professional services firms. A voice agent, built on LangChain and LangGraph, answers inbound calls and chat messages with real-time status pulled from the firm’s ERP or logistics API. LangGraph handles the stateful logic: if the shipment is delayed, the agent escalates to a human; if it’s on time, it responds directly. The integration plugs into Zendesk or Intercom through their native APIs, so existing ticket queues and SLA reporting stay intact. The pilot runs for four weeks with a fixed scope: one workflow, one channel, one success metric. No scope creep, no open-ended discovery.
3. Build the Compliance Boundary First
The UAE’s Federal Decree-Law No. 45 of 2021 on personal data protection aligns closely with GDPR in its core obligations: lawful basis for processing, purpose limitation, and data subject rights. For a professional services firm handling client names, addresses, and contract references, the practical constraint is that data cannot leave the jurisdiction without explicit consent and a data processing agreement. Forfis addresses this two ways: where data can flow through cloud APIs, it uses OpenAI or Anthropic endpoints with contractual data-processing addenda; where it cannot, it deploys open-weight models on the client’s own hardware. The architecture is model-agnostic by design, so the compliance boundary determines the model, not the other way around.
4. Keep a Human in the Loop by Default
The voice agent drafts responses; a human approves anything that touches a contract, a refund, or a client’s legal standing. This is not a technical limitation — it is a deliberate design choice that satisfies GDPR Article 22 (right not to be subject to automated decision-making with legal effects) and the UAE’s equivalent provisions. In practice, the agent handles 70-80% of routine status queries autonomously. The remaining 20-30% — delayed shipments, disputed invoices, contract amendments — route to a human queue with full context attached. The firm’s existing support team in customer support reviews and approves these within the same Zendesk or Intercom interface they already use. No new tooling, no new training cycle.
5. Measure Error Rate, Not Just Speed
The pilot ships with a measured before/after baseline: cycle time per interaction, error rate on data entry, and cost per resolved ticket. For a firm processing 400-600 status inquiries per week, the typical result is a 35-50% reduction in average handling time and a measurable drop in transcription and data-entry errors. The four-week timeline is fixed: Week 1 is audit and baseline, Week 2 is integration build, Week 3 is model tuning and internal testing, Week 4 is soft launch with live traffic. If the pilot hits its success metric, the firm moves to rollout across additional workflows. If it does not, the fixed-scope structure means the firm has lost a bounded amount of time and money, not an open-ended engagement.
6. Plan for Managed Operations from Day One
A pilot that ends with a demo is a pilot that fails. Forfis delivers the system as a managed AI operations engagement: the firm gets a monthly performance report with cycle time, error rate, and cost per interaction; Forfis monitors prompt drift, manages API costs, and updates the system as business rules change. The voice agent’s response templates are versioned and auditable. Model selection is revisited quarterly — if a new open-weight model outperforms the current one on the firm’s specific task, the swap happens without re-architecting the integration. The firm’s IT team retains full visibility into the system through standard API logs and access controls. This is the difference between a one-time build-and-handover and a system that keeps performing as the firm’s volume and rules evolve.
Leave a Reply