Capability 01 — Agent Desk
Onboard
Onboarding is where a program stops being a document and starts being a workflow. The institution writes the requirements; every submission, from every channel, arrives assembled against them.
Customer intake
One structured entry point, with the program's requirement set loaded before anything is collected.
Identity verification
Entity, beneficial owners and control person, with the provider and version that produced each result.
Document processing
Documents parsed, bound to the item or entity they describe, and tracked to their expiry.
Risk profiling
The file assembled against the institution's criteria. It produces no score and no recommendation.
Onboarding completion
A complete file routed to the bank or processor the program names, with correspondence kept on it.
Requirements come from the program, not the agent
Selecting a program loads its requirement set. A channel cannot shorten the list to close a deal faster, and an agent cannot submit around a document that has not been supplied. The requirement list is a property of the institution's policy version, which means changing it is a policy change with an approval record rather than a conversation.
This is the difference between a standard and a guideline. A guideline is what a submission is measured against after it arrives. A standard is what it cannot be submitted without.
What a submission actually carries
The file an institution receives is complete in the same way every time, which is what makes reviewing forty of them a process rather than forty separate investigations.
Routing follows the program
Which bank and which processor a submission reaches is determined by the program it was opened under, not by an agent's preference or an operator's economics. A merchant that fits two programs is a decision someone records, not a routing accident.
Correspondence lives on the file
Underwriting questions and the answers to them are part of the record. A condition raised in week one and satisfied in week three is visible on the file rather than in somebody's inbox, which matters most on the files that go badly — those are the ones where the sequence of what was asked and when gets disputed.
What onboard does not do
A control layer is only useful to an institution if its limits are as clear as its capabilities.
The institution underwrites and decides. SentryFox assembles the file against the rules and routes it.
Returned names an unmet requirement. It carries no judgement about the applicant and produces no reportable event.
There is no risk score, no likelihood of approval and no ranking. Producing one would be making the decision quietly.
See it running
Onboard runs in the control plane alongside the other three capabilities, on representative data.
Or start a pilot conversationThirty-three screens. Nothing in it is a real merchant or a real transaction.