Onboarding takes a client from the first message to an active account without the file ever leaving the system. Documents are read as they arrive, the regulatory form comes pre-filled, identity is checked against both the document and the face, and what a person does is confirm — not retype. Eight domains, thirty-two modules, one file.
An onboarding is not a form: it is a file that has to end up complete. It moves through the stages and at each one something gets closed — read off a document, matched against a face, or confirmed by a person. What matters is which of those need somebody and which do not.
The client sends a photo of their ID and somebody types the name, the number and the date into a form. It is minutes per document, it is where the typos come from, and it is the step that decides how long the whole thing takes — because there is a queue in front of it. And when a field is wrong, nobody finds out until the file comes back rejected.
The document arrives and comes back written: the fields filled in, each one with how confident the reading was, and the two or three that need a look flagged. A person confirms in seconds instead of typing for minutes — and what they confirm is what ends up in the regulatory form, with a record of who confirmed it.
A client can start on WhatsApp and finish at a branch. That is not two processes with a copy-paste in the middle: it is one file that several doors write into, with the same stages and the same requirements behind all of them.
The channel decides who talks to the client, not what the process asks for. A file opened on the web and one opened by an executive at a branch close with the same requirements — and both are visible on the same board.
Eight domains, thirty-two modules. Nobody buys an onboarding form; what gets bought is everything around it — who can see what, where the catalogues come from, what happens when a document expires.
Leads and clients, from the public portal or from any channel, in a pipeline with scoring and origin. So nobody gets lost between the first message and the file.
Who gets in and what they can do: SSO, OAuth 2.0 and a permission matrix per module. It is what lets a supervisor and an executive open the same file and not see the same things.
Categories, products and requirements with dynamic attributes. Changing which documents a product asks for is configuration, not a development.
The engine: a drag-and-drop flow editor, the stage pipeline, assignable tasks with SLAs, and the board where every file in flight is visible.
Where the file fills itself in: Cyntia OCR reads, face match and liveness verify, forensic analysis rules out what is not genuine, and the regulatory form comes out as a signed PDF.
OpenAPI, REST and webhooks against public registries, the tax authority and the core. A piece of data that already exists somewhere else does not get asked for twice.
The operational dashboard and each file's own timeline: what is open, how long it has been, who has it and what is missing. Traceability milestone by milestone.
Tickets, internal messaging, notifications by email, SMS and push, and a survey when it closes. The client asks through whichever door, and the answer comes out of the same file.
Eight domains is the summary; this is the list. Thirty-two modules, each one a screen somebody actually works in, and the ten capabilities that run underneath them. The list is here because a system this size cannot be described in eight cards without sounding smaller than it is.
From the first message to the active account, counting the days it spends waiting. That number is the one we go after — and we will tell you which part of it is the process and which part is the paperwork.
Talk to us