Switching on WhatsApp onboarding is the easy part. A number, a verified business profile, a conversation flow — that work is measured in days, not months.
What takes longer is deciding what the conversation is supposed to produce. A chat that collects an ID photo and a phone number is a chat. A chat that produces a complete, consented, verifiable customer file is onboarding. The difference is not technology. It is the thinking you do before anyone writes the first message.
Here is the order that works, based on what actually stalls these projects.
Rolling out WhatsApp onboarding, in order
Define the complete file first
Work backwards from what a regulator expects to see.
Start business verification on day one
It is the long pole, and it is out of your hands.
Connect it to the loan book you already run
Re-keying applications cancels out the whole exercise.
Give the assistant a name
Customers answer a person, not a system message.
Train officers on exceptions, not software
The flow handles the ordinary cases by design.
Define the complete file first
Most onboarding flows are designed forwards, from the greeting. That is why they end up collecting a friendly set of details that still leaves a compliance officer with follow-up calls to make.
Design it backwards instead. Write down what a complete file looks like for each of your products — identity, proof of income, address, next of kin, consent to process, whatever your licence and your credit policy require — and then build the conversation that produces exactly that. If a question does not contribute to the file, it does not belong in the flow. If something belongs in the file and no question produces it, you have found a gap that would otherwise show up months later during an inspection.
Start business verification on day one
This is the step that surprises people. The software configuration is quick. Getting a WhatsApp Business account verified is a process with a third party, and it depends on your business documentation being in order and matching what is already registered.
Begin it before you have finished designing anything else. Teams that leave it until the flow is signed off lose weeks waiting on something they could have started immediately, and they spend those weeks explaining a delay that was avoidable.
Connect it to the loan book you already run
An onboarding channel that ends with a staff member copying details into your loan management system has moved the manual work rather than removed it. Worse, it introduces a second version of the truth, because the chat record and the LMS record can now disagree.
Decide early how a completed application reaches your existing system, and who is accountable when it does not arrive. This rarely requires replacing the LMS. It requires agreeing on the handoff and testing it with real files before go-live.
Give the assistant a name
A small thing with a disproportionate effect. An onboarding assistant with a name and a profile picture gets treated as a member of staff. An unnamed one gets treated as an advert, and people stop replying halfway through.
Choose a name that fits your institution and use it consistently across the profile, the greeting and the handoff message, so that when a human officer takes over the conversation, the customer understands who they are now speaking to.
Train officers on exceptions, not software
Training tends to be built around the interface. That is the wrong emphasis. The routine applications are handled by the flow without anyone watching, which is the entire point of having it.
The system is not the difficult thing to learn. Knowing when to step into the conversation is.
What officers need is judgement about the edges. A blurred ID. A customer who abandons the chat two questions from the end. An applicant whose documents do not match the name on the account. Those cases need a person, and the handover from assistant to officer should feel unremarkable to the customer on the other side.
What to watch in the first month
Resist the urge to judge the rollout on volume alone. Early numbers reflect how many customers knew the channel existed, not how well it works.
The more useful questions are where conversations stop, how many arriving files are complete without a follow-up call, and how long a file sits between the customer finishing and an officer picking it up. Each of those points at something you can change. Total applications does not.
Bankify handles the onboarding layer — the conversation, the checks and the handoff — on WhatsApp, mobile, Messenger and web chat.
