Service standards

From an unclear process to a measurable, reviewable system

This page describes the stages we typically follow when delivering a service. Final scope, timeline, and deliverables are defined in the proposal or agreement for each project.

Last updated: 16 July 2026
01

1. Process discovery

We document how the process works today, the systems and channels involved, failure points, authority owners, and exceptions that cannot be ignored.

  • Current-state map
  • Data sources and integrations
  • Baseline and success measures
  • Risks and sensitive decisions
02

2. Scope and control design

We define where the process starts and ends, what the agent executes, what requires confirmation, and what remains with an employee. Failure, pause, and escalation paths are also defined.

  • Clear and bounded scope
  • Permission matrix
  • Human handoff rules
  • Acceptance criteria
03

3. Build and test

We build integrations, instructions, and business rules, then test normal, missing, and conflicting data. The solution does not move to real use before passing agreed acceptance scenarios.

  • Test environment appropriate to scope
  • Core and exceptional scenario testing
  • Language and message review
  • Known limitation documentation
04

4. Launch and monitor

Launch starts gradually where the process allows, with monitoring of failures, result quality, and human handoff rates. Findings are prioritized according to operational impact.

  • Limited or phased launch
  • Dashboard or reporting as agreed
  • Post-launch review
  • Improvement or expansion plan
05

Client responsibilities

Delivery quality depends on accurate information, available decision owners, suitable integration permissions, and approved policies that can be converted into rules.

  • Provide authorized access and data
  • Approve policies and messages
  • Assign decision and escalation owners
  • Inform Falaq when systems or rules change