Applications Abandoned at KYC
Everything typed up to the ID step, then the tab closed. Nobody asks why.
Sales persuasion, from the first signal to the next sale.
Inside the Persuasion ModelSee how the next response is chosen.A sales journey for the decisions your customers make.
For Fintech and Banking Onboarding Teams
It finishes applications, brings applicants back to verification and gets accounts funded over WhatsApp, iMessage and SMS. It answers the objection, follows up for weeks, and activates the account in your name.
Trained on over 3.5M real sales conversations, including how each one ended.
In Good Company
The Status Quo
Everything typed up to the ID step, then the tab closed. Nobody asks why.
Approved, card issued, balance zero. The first transfer needs a conversation nobody has time for.
No card swipe, no direct deposit, no second transfer. It goes dormant.
The Model
Sellence's edge is sales psychology. The model reads the hesitation, the timing and the real objection. Then it answers like the best person on your onboarding team.
Now you can talk to every applicant, personally, and close.
Behind Every Reply to an Applicant
The rational one comparing numbers. The worried one who needs reassurance. The busy one who wants the bottom line. Each gets its own technique.
Empathy, authority, proof from reviews, objection handling, closing. The model picks the one that fits the moment.
Trained on all of them, including how each one ended: deal or no deal.
How It Works
Co-pilot puts the best answer in front of every teammate. Autopilot runs the follow-up alone. You set the pace.
The model drafts the reply to every applicant message. Your team approves or edits, and sends.
The model runs the thread end to end, for weeks. Fraud flags and complaints go to your team.
One thread carries across all of them.
No IT project. The model sits beside your core and your KYC provider.
Application started, KYC abandoned, approved, balance still zero. Your stack sends the event, the model opens the conversation.
Your onboarding stack, Alloy or Plaid, your core, as examples. Our engineers connect them.
Every thread, status and funded event writes back. You decide how much.
The Results
Every pilot runs against a control group on your own applicant flow. Half get the model, half keep your current push and email.
Applications that reach verified.
Verified accounts that make a first transfer.
Funded accounts that get used: a card swipe, a direct deposit, a second transfer.
One completion event, agreed before launch, reported beside the control group.
Every Scenario
Start with the step where most applicants leave. The same brain then learns the rest of the flow.
Brings the applicant back to the exact screen they left.
Explains why the ID is needed, in your approved wording, then sends the secure link.
Approved and still empty? The model asks what is holding the first transfer.
0 scenarios connected
Gets the card used, the direct deposit switched, the second transfer made.
Reaches closed or idle accounts with a real reason to return.
Replies within minutes of the application starting.
Start with application completion. Add the rest of the flow on the same brain.
Use Cases and Proof
The application that stops at KYC, and the account that never funds. One brain runs both.
Left at the ID step. The model brings them back to that screen, politely.
The model opens in your name, with the step they left and a deep link back to it.
It explains how the ID and SSN are used, in your approved privacy wording, then sends the secure link.
No answer? It comes back a few days later, in the applicant's local time. Never spam.
The application submits. Your KYC provider reviews as usual. Status written back to your core.
Open and empty. The model opens the conversation and stays until the first transfer.
The model asks what is holding the first deposit, with the plan they chose in hand.
It answers with features and fees from your approved wording, on their own use case.
Transfer link and confirmation, the funded event written back. Nobody on your team touched the thread.
Real conversation. Names and details changed for privacy.
Security and Privacy
Your applicants' data stays with you. The model never makes a verification or credit decision. Every thread is documented.


Full details, controls and the SOC 2 report: trust.sellence.com
Only applicants with consent on file. STOP holds on every channel. Quiet hours run in the applicant's local time.
Every fee and feature claim comes from wording your compliance team approved.
Verification, eligibility and credit stay with your KYC provider, your core and your sponsor bank. Never an outcome.
Every message, opt-out and consent status logged with a timestamp. The applicant only sees you.
Build or Buy
Every serious onboarding lead asks. Row by row.
| Question | What lands on you if you build | The persuasion model |
|---|---|---|
| How many applications get worked | Whoever your team reaches, in office hours. | Every unfinished application within minutes, 24/7. Follow-up for weeks. |
| Who gets the account funded | One push notification, one email, then silence. | Closes on its own, trained on 3.5M+ conversations. Handles “is my money safe”. |
| Your onboarding team | The system bypasses the team, or the team ignores it. | Team and model, one squad. Autopilot earned step by step. |
| Time to a measured result | A first version after a year, with no proof it funds. | Live in weeks, measured from day one. Control group built in. |
| So it never promises an approval | One wrong “you're approved”, and the project is buried. | No message leaves without passing your rules. Never a decision. |
| TCPA, UDAAP and security | Every script goes back to compliance and the sponsor bank. | SOC 2 Type II from day one. PII masked before the model. |
| Carrier registration and channels | Templates and every connection maintained by you. | WhatsApp, iMessage, SMS, phone and web chat, maintained by us. |
Common Questions
No. Those stay with your KYC provider, your core and your sponsor bank. The model answers questions and returns the applicant to your process.
It asks what they want to check first, explains how the ID is used, then sends the secure link.
Recorded consent only, quiet hours honored. STOP ends the thread and writes back. Every fee claim is approved wording.
With you. Direct identifiers become tokens before anything reaches the reasoning model.
Yes. It runs off the events your app already emits: application started, KYC abandoned, approved. Write-back is yours to configure.
With a control group on your own applicant flow, on the completion event agreed before launch. 2 months, then a 12-month term.
The Next Step
A 30-minute call. We walk your funnel, application to funded account, and pick the first scenario.
Consent stays yours. Opt-out on every message. Every thread logged.