For payfacs, ISOs & acquirers
Every acquisition hands you a book of fallout: merchants stalled between signed and first transaction, chased today by a room full of people. Thread runs the chase per merchant, collect, verify, push, confirm, and done means the record is in your CRM, present and correct. Never "the merchant emailed something over."
done = the record, present and correct
Illustrative book. Every rung is a code-observed fact. Transacting is earned by the processing data, never by a promise on a call.
The gap
The fallout number. A share of every acquired book stalls before first transaction. Those merchants cost real money to acquire, and until they transact, they're a line item, not a portfolio.
Days-to-first-transaction. Every stalled day is interchange you don't earn. The chase today is manual: calls, spreadsheets, and follow-ups that depend on who's at their desk.
"Sent" isn't "landed." A merchant emailing a voided check isn't data onboarding. Done means the record is in the CRM, field by field, format-checked and verified.
How the motion runs
The acquired book loads with each merchant's specific gaps, missing banking, unsigned docs, dead contact info. Consent attested before the first touch.
The guide texts the owner for exactly what's missing, secure links, one item at a time, format checked on receipt. After a quiet week it calls. It doesn't lose the thread at item three.
Every collected field is pushed and re-read from your CRM, present and correct. "The merchant sent it over" doesn't close anything.
First transaction confirmed in processing data, record complete in the CRM. Your ops team audits the log, not the inbox.
Native to your world
Merchant onboarding stalls in the gap between approved and processing. The guide walks each merchant through KYB, banking, and the terminal, and only calls it done when the first charge settles.
More of your world
The same motion runs on the messy middle of a processor’s book: records that never landed, and terminals that went quiet. Done is always the record, not the reply.
What you're buying
Guides, long-lived resident agents, one per account, each with its own memory and a single goal it pursues across text, email, and voice.
Motions, the harness over the lifecycle: it holds the goal, the context, and the exit criteria at every stage, and reads your systems to close outcomes.
Voice Studio, design the voice agent beside the guide: persona, guardrails, knowledge, a phone number that answers as your brand.
Workflow builder, routing and segmentation: reads each account's state and engages the right guide at the right moment.
See it in detail, Motions, the full feature set, or call the live guide: the product answers the phone.
The floor
You're texting thousands of small-business owners under your name. The floor is enforced in the runtime, consent, quiet hours, STOP, logging, on every guide, every channel, every wake.
Add your own rules on top. The floor never comes off.
Proof
A 190,000-merchant payments processor runs this motion on merchant data onboarding.
anonymized · done means the record landed, present and correct
A national point-of-sale platform runs the same motion on merchant activation.
anonymized · same runtime, same verification discipline
Start here