Contact Info
Unit 9, 17 Power Ave
Alexandria, NSW 2015
info@hexflow.com.au
+61 (2) 8529 4085
Follow Us
Blog list image - Sixteen Checks Before an AI Agent Touches Client Data

Sixteen Checks Before an AI Agent Touches Client Data

Before an AI agent touches client data, someone in the firm should be able to answer sixteen questions. Not because a regulator demands it, but because the answers are what separate a controlled deployment from an expensive experiment.

This is the list we run with practices. It is deliberately blunt.

Where the data goes

  • Does client data leave the firm’s own environment at any point?
  • If it does, which country is it processed in?
  • Is the data retained, and for how long?
  • Is any of it used to train a model?
  • Can you delete a client’s data on request, completely?

Who can reach it

  • Which individuals hold credentials to the agent?
  • Do those credentials expire?
  • Is every action logged against a named user?
  • Can a revoked staff member lose access immediately?

What it is allowed to do

  • Can it write to the system of record, or only draft?
  • Is there a value threshold above which a human must approve?
  • What happens when it is uncertain β€” refuse, guess, or flag?

What happens when it is wrong

  • Can a single item be traced back to the document it came from?
  • Can a batch be reversed without unwinding later work?
  • Is there a named person accountable for review?

Sixteen questions, and most deployments fail at four, eleven and fifteen. The thresholds, the uncertainty behaviour and the rollback are the ones vendors skip.

Why the honest answer is slower

A system that processes everything inside the firm’s own environment is harder to set up than one that sends documents to a public endpoint. It is also the only version we will recommend for client files in legal, medical or NDIS work.

That position costs us deployments. It is still the position. The detail is on the automation overview and across the twenty specialised agents, each of which documents what it is permitted to touch.

The test that catches most problems

Take one client file and one real document from last week. Ask the vendor to process it in front of you and show you the log afterwards: what was read, what was written, what was sent where.

If that demonstration cannot be given live, the answers to the sixteen questions are theoretical. Theoretical is not good enough for a trust account or a patient record.

What we build

We build automation and digital employees for Australian practices and will answer all sixteen of these questions in writing before a pilot starts. Ask us for the answers.

Start with one process

Tell us where the hours actually go and we will map it against what an agent can and cannot take. One process, measured before it is trusted. The first conversation is free and usually short.

Talk to Hex Flow

Articles on AI automation for Australian practices by Shahadat Hossain, automation specialist at Hex Flow in Sydney.

Post a Comment