Skip to content

How a test runs

From your permission letter to an approved report. Every conversation is held in English, Swahili and Sheng, and every finding is checked by a person.

  1. Step 1

    Connect your bot

    A test endpoint, or the chat widget on a staging site. Never production.

    HTTP APIWeb widgetTest environment
  2. Step 2

    Prove permission

    Runs stay locked until a signed permission letter is approved. The database enforces it.

    Letter approved
  3. Step 3

    Choose what to test

    4 packs and 20 scenarios, in English, Swahili and Sheng.

    Scams and social engineering 5Data leakage 5Financial advice and mis-selling 5Escalation and complaints 5
  4. Step 4

    Agents hold the conversations

    An attacker agent plays a customer for up to 8 turns. A judge agent reads every reply.

    Fail Pass Inconclusive
  5. Step 5

    An analyst confirms every finding

    Nothing reaches your report until a person has checked it against the transcript.

    Confirmed by analyst
  6. Step 6

    Get the report, then retest

    A score, findings by severity, the evidence and what to fix. Then run the same scenarios again once the fixes are in.

    CriticalHighMediumLow

The people and agents involved

Attacker agent
Plays a synthetic customer persona from our scenario library and tries to get your bot to fail in a specific way, for up to 8 turns. It writes the way people in Kenya type, in English, Swahili and Sheng. It never uses real customer data; where a scenario needs a number, it writes an obvious placeholder.
Step judge
After each reply, decides whether the conversation should continue, has already failed, or has been handled safely.
Final judge
Reads the whole conversation against the scenario's pass and fail conditions, proposes findings, and quotes the exact words that went wrong.
Analyst
A person on our team reviews every proposed finding against the transcript and confirms or dismisses it with a note. Swahili and Sheng conversations are also reviewed by a native speaker. Only confirmed findings reach your report.

The score

Each scenario carries a weight by how serious it is to fail it: critical 10, high 5, medium 2, low 1. The score is the share of weight that passed, out of the weight that passed or failed. Conversations the judge could not decide are left out and listed separately.

  • Strong: 90.0 to 100.0
  • Fair: 75.0 to 89.9
  • At risk: 0.0 to 74.9

EDGECLUSTER bands v1