Maqetin messages new customers who stall before their first transfer.
New customers of digital banks, wallets and lenders stop at the ID check, leave the account empty, or never send a transfer. Maqetin sees each step in your app's events, sends the nudge by email and keeps your codes and receipts on the same record as your marketing. WhatsApp, push and SMS are planned.
Sample workspace: Harbour Money, a digital bank in London.
Each stage where customers stall will have a journey template.
The templates will start from events your app already sends, such as kyc.started and transfer.completed.
| Stage | Where people stall | Journey that answers |
|---|---|---|
| Onboarding | Signed up, never opened the app again | Welcome series: email |
| KYC | Started verification, didn’t finish | KYC nudge: email after 24 hours |
| First deposit | Verified, account still empty | First deposit: email after verification |
| First transfer | Money in, nothing sent | First transfer: email |
| Growth | Heavy user on a basic tier | Upgrade nudge: email |
Planned report, drawn with sample figures.
Codes and receipts follow their own rules.
A transactional email addressed by user id goes through the same platform and lands on the same profile as your marketing. A profile marked no for marketing still gets a code or a receipt, and a suppressed address gets nothing.
- Codes and alerts by SMS, fraud checks on WhatsApp and loan offers by push are planned: SMS with your registered sender ID, WhatsApp with reply buttons that block the card in one tap, push with Accept and View buttons on the notification itself.
Hi Mary,
Your loan of £1,500 is approved. Accept it today and the money lands in your account.
Accept loanYou will track KYC completion, first transfers and dormant accounts.
Each number will sit beside the journeys that moved it.
Planned report, drawn with sample figures.
Data rules, and ad rules that are planned.
A marketing-email flag on every profile
Your app sets it when it identifies the person, and an unsubscribe, a complaint or a hard bounce turns it off.
Ad rules for financial products
Planned: no lookalikes where Meta forbids them, and no audience names that hint at income or credit.
Every staff access on the record
Support can view your workspace only with a stated reason, under a visible banner, logged.
Residency and SSO
Planned: data residency, dedicated infrastructure and single sign-on for your team.
Get more of your sign-ups to their first transaction.
Book a demo and we'll show you Maqetin on KYC and first-transaction journeys like yours.