An onboarding team reviews two things: the applications the agent holds, and the accounts it opened alone. Train for both. Teach how it verifies and risk-rates, calibrate on real held applications, shadow live onboarding with every decision checked, and sign off analysts who are accurate on risk and quick on clean cases. Sample auto-opened accounts every week, without exception.
What does the onboarding team review?
Customer onboarding is the process of taking someone from application to an open, usable account. An onboarding agent typically collects application data, verifies identity documents and liveness, checks addresses, screens names, assigns an initial risk rating, opens low-risk accounts within bounds at depth 3, and holds the rest: higher risk ratings, screening matches, document inconsistencies, business customers with complex ownership, and anything the customer declared that the agent could not verify.
That creates two review streams with opposite failure modes. Held applications fail when analysts approve too readily under queue pressure. Auto-opened accounts fail when nobody looks, because they look finished. A good programme trains for both, and adds a third concern: customers abandoning applications that sit in a queue too long. Speed on clean cases is part of the job.
The head of onboarding owns the programme. Financial crime approves the sign-off standard for risk decisions. Customer experience shares ownership of the speed measures.
What does the programme look like, step by step?
- Learning, week 1: analysts complete lessons on how the agent verifies and rates, which bounds decide auto-opening, and what each hold reason means.
- Agent, depth 1: builds a practice set of past held applications and auto-opened accounts, including some later found to be problematic.
- Calibration, week 2: analysts decide alone, then compare. Include clean cases, so analysts learn when not to hold things up.
- Shadow, weeks 3 and 4: analysts decide live held applications and sample auto-opened accounts; a senior analyst checks every decision.
- Agent, depth 3 in live work: opens low-risk accounts within bounds; holds the rest.
- Sign-off: head of onboarding and financial crime assess shadow decisions on risk accuracy and timeliness.
- Ongoing: weekly sampling of auto-opened accounts, monthly calibration.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Lessons | Nothing | none | Analysts |
| Practice set | Lists held and auto-opened cases | 1 | Trainer anonymises |
| Calibration | Nothing | none | Analysts, financial crime |
| Shadow | Opens low risk; holds others | 3 | Analyst decides; senior checks |
| Weekly sample | Lists auto-opened accounts | 1 | Analysts |
| Sign-off | Nothing | none | Head of onboarding, financial crime |
What must analysts learn to check?
Why the application was held. The hold reason names the bound. A screening match needs a different review from a document inconsistency or an address that would not verify.
Screening matches. Is the match the customer? Compare full name, date of birth, nationality and any other identifiers. Record the reasoning either way.
Document consistency. The agent compares what documents show with what the customer declared and with the text it extracted. Analysts review mismatches and decide whether to ask for more.
Business ownership. For business customers, who owns and controls the company, checked against registry extracts, not only the customer's chart.
Auto-opened accounts. In samples, check that the risk rating was right and the evidence supported it. Look for patterns: several accounts opened with the same device, address or employer details.
Clean cases. A held application with a minor, explainable issue should move quickly. Over-holding loses good customers.
An illustrative sample finding shows why the weekly sample matters. Reviewing twenty auto-opened accounts, an analyst notices four opened within a day using different names but the same employer, the same mobile handset model and addresses on one short street. Each passed every check on its own. The analyst refers the pattern to financial crime and reports it to the agent's owner, who adds a bound that holds clusters like this for review.
Which controls leave evidence?
- Lessons before shadow. Evidence: completion dates.
- Every shadow decision checked. Evidence: senior analyst's name.
- Screening decisions reasoned. Evidence: the identifiers compared and the conclusion.
- Auto-opened accounts sampled weekly. Evidence: sample log and findings.
- Sign-off by onboarding and financial crime. Evidence: both names.
What should you measure?
- Shadow accuracy per analyst.
- Auto-opened accounts later restricted or closed for risk reasons.
- Time to decision on held applications, and abandonment while held.
- Screening match decisions overturned in quality assurance.
- Patterns found in samples and passed to the agent's owner.
Where does it usually go wrong?
Auto-opened accounts are never sampled. Organised fraud often passes simple checks in volume. Sampling finds the pattern.
Analysts over-hold. Fear of mistakes makes every minor issue a request for more documents. Calibrate on clean cases too.
Queue pressure. Backlogs push analysts to approve without reading. Watch decision times.
IT and onboarding train separately. Access and system changes affect what the agent can see. The reviewer onboarding checklist for the IT team is worth a look for the onboarding lead.
New analysts use the reviewer onboarding checklist for the onboarding team. Operations and support teams run the same four stages on different work; see how to train the operations team to review AI agent decisions and how to train the support team to review AI agent decisions. The full programme is in training teams for AI agents.
Where the Academy fits
Pryme Intelligence Academy's Operator track teaches analysts how a governed agent decides, how to review held work and how to run the rhythm of daily sampling, with module tests set in the learner's own industry and role. Certified Pryme Operator status is valid for 12 months; renewal is an update module and a short quiz, which suits teams whose agent bounds change over time.
Questions people ask
Should the agent open accounts for business customers?
Usually not at first. Complex ownership needs a person. Simple sole-trader accounts may be suitable later, with evidence.
How many auto-opened accounts should be sampled?
Enough to cover every product and channel each week, weighted toward newer channels. Increase sampling when a pattern appears.
What if customers complain about delays?
Look at why they were held. If clean cases are being held, recalibrate; if risk cases are slow, add capacity rather than lowering the bar.