Abandoned checkout follow-up
When someone starts paying for a plan or an order and doesn't finish, they get a friendly reminder a few hours later and one softer note the next day, with a button that takes them straight back.
The problem this solves
Most people who reach checkout and leave were genuinely interested; something interrupted them. A short "did you mean to finish this?" brings a real share of them back, but only if it arrives while they still remember why they came.
What you end up with
Every couple of hours, people who started checkout two to twenty-four hours ago and never finished get an email showing what they picked, with one button back. A second, gentler note follows after two days. Anyone who pays, or after a week, stops hearing from you.
How it works
- Every two hours, the follow-up starts on its own.
- It finds checkouts that began two to twenty-four hours ago and weren't finished.
- Each person gets an email with what they picked, the total, and a button that reopens their checkout.
- Two days later, anyone still unfinished gets one softer note.
- People who paid, cancelled, or started over a week ago are left alone.
Build this in your app
Insight asks a few questions first, so it fits your app.
Built from
Scheduled jobs (cron)
Scheduled jobsMake something happen on a schedule: every hour, every Monday morning, the first of the month. Pick when in your own time, say what should happen in plain words, and DontCode writes and runs it for you.
Card payments
PaymentsYour customers can pay by card right in your app's checkout, once or on a subscription that renews on its own. Price in won or US dollars, and add an international connection to take cards from abroad. The money goes straight to your own account.
KakaoPay
PaymentsKakaoPay is built into your app's checkout, next to card, NaverPay and Toss Pay. Connect your own PortOne account on Payments, and your customers can pay with it once your contract includes it; the money goes straight to you, and DontCode takes no fee. There's no payment code to write.
Transactional email
Email & pushEmail just works. Your app already sends sign-up codes, password resets and payment receipts, and any email your features need, like an order confirmation or a weekly summary, is added for you. There is no mail server to set up, and if your app speaks more than one language, each customer gets their emails in theirs. The Emails page shows what was sent and lets you put your brand on customer emails. If an address bounces, your app stops emailing it, marks that person on the Users page, and lets you send to them again once they fix it. Your app emails people, never typed-in addresses: you, whoever is signed in, your customers, or an outside inbox you keep on the Emails page, like your lawyer. A contact form reaches your own account's email by itself, even if the app changes hands. To stop anyone from using your app to send spam, a page can only email you, the person signed in, or an inbox you saved; emails to your customers, like an order update, are sent by your app behind the scenes, and Insight sets that up. The button in an email always opens your app.
Related recipes
Win back people who cancel
When someone cancels or their plan ends, ask why with one tap and give them a reason to stay. One gentle follow-up later, then nothing. Your app already sends the renewal and payment emails; this picks up where those stop.
Welcome emails for new sign-ups
A short series of emails that starts the moment someone signs up: a welcome, then the next useful step on day 1, a key feature on day 3, and an invite to share on day 7.
Upgrade nudge at the plan limit
When someone on the free plan reaches its limit (projects, uploads, messages), they see what the next plan gives them, with an upgrade button right there, and get one email about it, not ten.