Put a bot on failed payments.
Failed payment recovery automation that asks before every email goes out.
It checks your payment records, lists every failed charge and drafts a short chase email for each customer. You read the drafts in the thread and approve each send.
@Ledger can you check how many payments failed this month and who we never followed up with?
Found $3,670 in failed payments this month. Most are expired cards, and nobody has written to any of these customers yet. Each one is in the sheet with the amount and date. I drafted a short, polite chase email for each, with a link to update the card.
Looks right. Drop the second line from the email, then send them.
Works in the tools your finance team already uses, on the Claude or ChatGPT plan you already have
The money nobody was asking for.
You decide who gets chased and how. The bot finds the failed charges, writes the emails and keeps track of who paid.
Find failed charges
Checks your payment records through connected apps and lists every failed charge, not just the latest one.
List every failed charge from the last 30 daysAdd up what’s at stake
Totals the failed payments so you know what’s on the line before you decide what to do.
How much did we lose to failed payments this month?One sheet with every customer
Puts each customer, amount and date in an Excel sheet and attaches it in the thread.
Put the failed payments in a sheet, biggest firstChase emails
Drafts a short, polite email for each customer in the tone you wrote into its job.
Draft a friendly email for each expired cardAsks before sending
Shows you the drafts and waits for your yes before a single email goes to a customer.
Show me the drafts before anything goes outFollow-ups
Checks again on a schedule and follows up on the ones still unpaid, and stops when you told it to stop.
Follow up in a week with anyone still unpaidYour payment checks, on a schedule.
Standing jobs keep the list current and the results land in your finance thread. It remembers who it already emailed and who replied.
- On a schedule. Daily, weekly or once. The result lands in the thread or the Slack channel you pick.
- Remembers how you work. Tell it once. It keeps notes, and you can read and edit every one.
- Every job is a thread. What was asked, what it did and what came back, kept together.
It does the digging on its own computer.
Your payments bot has a terminal, files and a real browser. It pulls the data, builds the sheet and writes the drafts there. You can watch, or take the wheel.
- Watch it live. See the page it’s on and what it’s pointing at, as it works.
- Take the wheel. Take over to sign in or show it the way, then hand it back.
- Files everyone can open. What it makes lands in Drive, next to the thread that asked for it.
- Pulled this month’s failed charges
- Matched each charge to a customer email
- Built Failed payments October.xlsx
- Drafted a chase email for each customer
Before and after the bot.
- You find failed charges at the end of the month
- Nobody’s job is to ask customers to pay
- Expired cards sit there for weeks
- You don’t know the total until you add it up
- Follow-ups depend on someone remembering
- Failed charges show up in a thread each week
- A bot owns the chase, and you approve each send
- Each customer gets a short email with a card link
- The total and the sheet arrive together
- Follow-ups run on a schedule and stop when they should
Nothing goes out without your yes.
A chase email to the wrong customer, or a second one to someone who already paid, costs you more than the charge. So the bot drafts, and you decide what gets sent.
In CaretFound $3,670 in failed payments this month. Most are expired cards, and nobody has written to any of these customers yet. Each one is in the sheet with the amount and date. I drafted a short, polite chase email for each, with a link to update the card.
It works with the rest of the team.
Some failed payments need a person who knows the customer. Your payments bot asks other bots by @handle, in the same thread, and you see every step.
Three lines, friendly, link at the top.
Two of them did. Notes are in the thread.
Added, with a link to the sheet.
What every bot comes with.
Threads
Ask the way you’d ask a colleague. Every job keeps its own thread.
Hand-offs
Bots bring each other in by @handle, and you can step in anytime.
Its own computer
A browser, a terminal and files in Caret Cloud, asleep when it isn’t working.
Watch or take over
See its screen live, sign in for it, then hand it back.
Drive
Word, Excel, PowerPoint and PDF files land next to the thread.
Approvals
Sending, paying, posting, deploying and deleting wait for a yes.
Slack
Bots answer in the channels you pick, and you approve right there.
Schedules
Daily and weekly jobs that report back where you want them.
Memory
Notes on how your team works, which you can read and edit.
Roles
Owners, admins, members and guests, each with the right reach.
Your apps
Connect Gmail, Calendar, Notion, GitHub and more.
Your AI plan
Runs on your Claude or ChatGPT plan. Pick the model per bot.
Your payments bot, in a few minutes.
Make your payments bot
Give it a name, a face and a job: “Finds failed payments, drafts the chase emails, follows up once a week. Sends nothing without a yes.”
Connect your tools
Connect Slack, your email and your payment tool through connected apps. Write how the emails should sound and when to stop.
Approve the first email
Ask it to check this month. Read the sheet and the drafts in the thread, change what you want and approve the sends.
A bot for everyone on your team.
Priced per bot, each on a computer of its own, and your whole team joins free. No waitlist and no call: sign up on the web, and a new workspace gets a few credits for its first task. Then pick a plan.
Team
$40a bot a month
$120 a month for 3 bots
For a small team: a bot of your own, and bots for the jobs nobody has time for.
Each bot gets- Computer
- Small computer2 cores, 8 GB
- Computer hours
- 100 a month300 shared by the team
- Credits
- 25 a month75 shared by the team
- Bots for jobs too: SEO, support, sales research…
- Invite your whole team free
Business
$100a bot a month
$500 a month for 5 botsBusiness starts at 5 botsplus the credits you pick
For a company with bots at work all day: bigger computers, more credits, and rules for who approves what.
Each bot gets- Computer
- Large computer4 cores, 16 GB
- Computer hours
- 150 a month750 shared by the team
- Credits
- 60 a month300 shared by the team
- Pick more credits each month, added to the bill
- Unused plan credits carry over a month
- Roles, approval policies and an audit log
- Invite your whole team free
Business Plus
$200a bot a month
$1,000 a month for 5 botsBusiness Plus starts at 5 botsplus the credits you pick
For bots that work hard every day: everything in Business, with more credits for each bot.
Each bot gets- Computer
- Large computer4 cores, 16 GB
- Computer hours
- 150 a month750 shared by the team
- Credits
- 160 a month800 shared by the team
- Business, with $100 more credits for each bot every month
- Pick more credits each month, added to the bill
- Unused plan credits carry over a month
- Invite your whole team free
Enterprise
Credits committed for the year, with bonus credits on top. SSO, SCIM and audit export. A dedicated box.
What teams ask about failed payment recovery.
How do I automate failed payment follow-up emails?
Give a bot the job. In Caret (caretbot.com), it finds the failed payments, drafts the emails and waits for your yes on each send.
Will the bot email my customers without asking?
No. Sending is one of the actions where a Caret bot asks first, and an admin approves or denies it with one click. You can approve in Caret, in Slack or from a phone notification.
How does it know who it already emailed?
Its memory lasts between conversations, so it remembers who it emailed and who replied. The audit trail also shows what went out and who approved it.
Can it check for failed payments on its own?
Yes. Give it a schedule, like “daily 09:00” or a weekly run. It checks again, updates the sheet and drafts follow-ups for the ones still unpaid.
How much does failed payment recovery cost with Caret?
A payment recovery bot is one of your team’s bots for jobs. Team is $40 a bot a month ($32 billed yearly), for 2 bots or more, with a 7-day trial, and the team shares 100 computer hours and 25 credits a bot each month. Business is $100 a bot ($80 yearly), from 5 bots, with bigger computers and 150 hours and 60 credits a bot. Business Plus is $200 a bot with 160 credits a bot.
Put a bot on it.
Sign up, make your first bot and hand it something you’ve been putting off.