Payments
Verified by Toolspoke

Dunning watcher

By Toolspoke

Lists Chargebee customers with failed payments or invoices in dunning each weekday and posts who is at risk to Slack.

Needs a Toolspoke account. You choose which project it installs into.

An illustration with made-up examples. It is not a recording.
Chargebee + Slack
Required integrations
Runs on a schedule
Weekdays at 9am by default
Post one message
What its last step does
Some actions can delete
3 of 34 actions in its tools
On this page
  1. The short version
  2. What it will never do
  3. What Dunning watcher does
  4. How it works
  5. What a weekday message looks like
  6. Who uses Dunning watcher
  7. What it connects to
  8. When it runs
  9. How to set it up
  10. Make Dunning watcher fit your business
  11. Compared with other options
  12. Questions
  13. Related agents

The short version

What it is
A ready-made Toolspoke agent that tells your team each weekday which Chargebee customers are failing to pay.
What it reads
Invoices Chargebee is still retrying, invoices whose retries have run out, failed payments from the last 24 hours, and the subscription behind each.
Where it posts
One Slack channel, chosen when you set it up.
How it sorts
At risk now, being retried, and first failures, each with amount owed, days in dunning and attempts so far.
How often
Weekdays at 9am once you switch it on. If nothing is in dunning it posts nothing.
What it never does
Cancel or change a subscription, refund an invoice, or contact a customer.
What you need
A Toolspoke account, a Chargebee API key and a Slack workspace.

What Dunning watcher will never do

Dunning watcher is told never to cancel a subscription, refund an invoice or contact a customer. A failed payment is a reason for a conversation, and the conversation belongs to a person.

Dunning watcher will never

  • Cancel, pause or change a subscription.
  • Refund an invoice, or create or change a customer.
  • Email, message or otherwise contact a customer.
  • Post a card number, a full email address or a billing address to Slack.

Why it never cancels

A failed card is usually an expired card, not a customer who wants to leave. Cancelling ends their access and has to be undone by hand. Chargebee's own dunning settings decide when that happens, not this agent.

What it keeps out of Slack

A revenue channel is read by more people than Chargebee is. The agent names the customer and the amount, and leaves the rest in Chargebee.

A message that leaksLumen Analytics, card ending 4242, billing contact [email protected], 18 Mill Street.
What this agent writes insteadLumen Analytics, 1,188.00 USD, 31 days in dunning, 4 attempts.

How to make it a lock

Connect a Read-only: All API key. The agent works the same, and cancelling or refunding is no longer possible through this connection.

These are written into Dunning watcher's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.

Dunning watcher reads Chargebee and reports who is failing to pay. Every call to a customer, cancellation and refund is a person's.

What Dunning watcher does

Dunning watcher is an AI agent that reads Chargebee every weekday morning, finds the customers whose payments are failing, and posts one Slack message listing who is at risk of cancelling, how much they owe and for how long.

A subscription that fails to renew rarely announces itself. The card is declined, Chargebee retries on its schedule, and a few weeks later the customer is cancelled without anyone having looked.

Dunning watcher looks every weekday. It reads the invoices still being retried and the ones whose retries have run out, checks the subscription behind each, and adds any payment that failed overnight.

It never acts on what it finds. A failed payment is a reason to talk to a customer, and that conversation belongs to a person who knows them. The agent is told never to cancel, refund or contact anyone.

In practice, on a weekday morning you get one message, or nothing:

  • Customers at risk now, with the amount owed and days in dunning
  • Everyone still being retried, oldest first
  • Payments that failed for the first time overnight
  • The total at risk per currency, and the change since yesterday

How it works

Dunning watcher works in four steps each weekday: it reads the unpaid invoices, reads the night's failed payments, checks each subscription and posts one message. All of it comes from the agent's written instructions, which you can read and edit after you install it.

  1. Step 1: Read unpaid invoices

    Invoices still being retried, and ones whose retries ran out.

  2. Step 2: Read failed payments

    Payments that failed in the last 24 hours.

  3. Step 3: Check each subscription

    Its status, plan and how long it has been unpaid.

  4. Step 4: Post one message

    At risk first, then retries, then first failures.

Drawn from this agent's own tools and instructions. It is not a recording of a run.

It reads both kinds of unpaid invoice

It calls list_invoices with status payment_due, where Chargebee is still retrying, and not_paid, where the retries have run out. The second kind is the one that turns into a cancellation.

It catches the first failure

It reads list_transactions for failed payments in the last 24 hours. A customer whose card failed for the first time is listed before an invoice is even in dunning.

It sorts by risk, not by amount

A customer is at risk now when retries have run out on a subscription that is still active, or when an invoice has been in dunning for 21 days or more. Everyone else is listed oldest first.

It keeps card details out of Slack

It names the customer by name, company or Chargebee customer id. It never posts card numbers, full email addresses or billing addresses. The limits are listed under what it will never do.

What a weekday message looks like

A message from Dunning watcher is a single Slack post. The customers most likely to cancel come first, then everyone still being retried, then the night's first failures.

Lumen

Channels

  • # revenue
  • # customer-success
  • # finance
  • # general

# revenue

Dunning watcherAPP9:00 AM

Tuesday. 2,964 USD in dunning across 9 customers, up 49 since yesterday.

At risk now (2)

  • Lumen Analytics, 1,188.00 USD, 31 days in dunning, 4 attempts, retries run out. Annual Growth plan, still active.
  • Orchard Health, 490.00 USD, 23 days in dunning, 3 attempts. Team plan, monthly.

Being retried (5)

  • Fieldnote Studio, 79.00 USD, 9 days, 2 attempts.
  • Hollis & Grey, 299.00 USD, 6 days, 2 attempts.
  • And 3 more, 810.00 USD in all.

First failures overnight (2)

Bramble Coffee, 49.00 USD. Tidemark Labs, 49.00 USD.

One message, posted on Tuesday at 9:00 AM. The customers and amounts are made up.
At risk now

Retries run out on a subscription that is still running, or three weeks or more in dunning. These are the ones to call today.

Being retried

Everyone else Chargebee is still retrying, oldest first, with how many attempts so far.

First failures

Cards that failed for the first time overnight. Most recover on the next retry, but a pattern is worth seeing.

Why it sometimes says nothing

If no invoice is in dunning and no payment failed, Dunning watcher posts nothing. A daily all clear teaches people to skip the channel.

A failed run is different. If Chargebee cannot be read, it posts that once, because a silent morning looks the same as a clean one.

Who uses Dunning watcher

Dunning watcher suits any subscription business that bills through Chargebee and would rather save a customer than find out they cancelled. The examples use made-up names.

A customer success lead

Hannah Brooks calls accounts before they lapse. The at risk group tells her who to ring first, and how long they have been failing.

In their messageNeeds youLumen Analytics, 1,188.00 USD, 31 days in dunning, retries run out.

A founder watching revenue

Kwame Asante checks the total at risk each morning. When it climbs two days running, he asks why.

In their messageWorth knowing2,964 USD in dunning across 9 customers, up 49 since yesterday.

A finance lead closing the month

Elena Petrova needs to know which revenue is unlikely to arrive. The days in dunning column gives her that without a report.

In their messageWorth knowingOrchard Health, 490.00 USD, 23 days in dunning, 3 attempts.

A support team spotting card problems

Jun Watanabe's team sees first failures before customers write in, so the reply is ready when they do.

In their messageEverything elseFirst failures overnight: Bramble Coffee, 49.00 USD.

What Dunning watcher connects to

Dunning watcher connects to two tools: it reads Chargebee and posts to Slack. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.

  • Chargebee

    Required

    Read and manage customers, subscriptions, invoices, transactions and the product catalog.

    Authentication: API key

    View integration for Chargebee

  • Slack

    Required

    Search conversations and send messages to your workspace.

    Authentication: Bot token

    View integration for Slack

What Dunning watcher does and cannot do in each connected tool
ToolWhat Dunning watcher doesWhat it cannot do
ChargebeeReads invoices, failed payments, subscriptions and customers (list_invoices, get_invoice, list_transactions, get_subscription, get_customer).Email a customer: the connector has no action for it. It can cancel a subscription, refund an invoice and change a customer, and this agent's instructions forbid all three.
SlackPosts one message with send_message, and reads yesterday's post with read_channel_history.Delete messages: the connector has no delete action.

The Chargebee connection can cancel and refund if the key allows it. Dunning watcher is told never to, and that is an instruction. To make it a lock, connect a Read-only: All API key: every action this agent uses is a read, and cancelling, refunding and editing a customer need a Full-Access key.

You can also switch Chargebee's write and destructive actions off for this agent in your project. The access control guide explains how.

The activity log records each call, but Chargebee reads that name a customer keep only that the call happened. The message posted to Slack is stored.

When Dunning watcher runs

Dunning watcher runs every weekday at 9am, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.

  • Each run reads every invoice in dunning and the night's failed payments.
  • When nothing is in dunning, it posts nothing.
  • Customers whose retries have run out always come first.
  • If Chargebee cannot be read, it posts that once.

Each run uses model credit from your workspace balance, even when nothing is posted, so it makes five runs a week. The Chargebee and Slack calls themselves are free.

Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the days and time and edit its instructions. The agent's page lists recent runs and their cost.

How to set up Dunning watcher

To hear about failing payments every weekday, add Dunning watcher to a Toolspoke project, connect Chargebee and Slack, choose the channel and switch on the schedule. It takes a few minutes, and nothing runs until the last step.

  1. Step 1: Create a Toolspoke account or sign in

    Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.

  2. Step 2: Add it to a project

    Pick the project it should live in. You get your own editable copy, and you can see the two tools it brings before anything connects.

  3. Step 3: Connect Chargebee

    In Chargebee, add a Read-only: All API key, then paste your site name and the key. It is stored encrypted and the agent never sees it.

  4. Step 4: Connect Slack

    Choose Sign in with Slack and approve the Toolspoke app. For a private channel, add the Toolspoke bot to it first.

  5. Step 5: Choose the channel

    Name the channel in the instructions, and a minimum amount if small invoices are not worth a line.

  6. Step 6: Switch on the schedule

    The schedule arrives switched off. Run it once to see a message, then switch it on.

Make Dunning watcher fit your business

Dunning watcher's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.

Paste any sentence below into the builder chat, or say the same thing in your own words.

Leave out small invoices
Do not list an invoice under 50.
Tag the account owner
Mention @hannah on every customer in the at risk group.
Change what counts as at risk
Treat 14 or more days in dunning as at risk, not 21.
Highlight annual plans
Put annual plans first within each group, because they are worth the most.
Run once a week instead
Run on Mondays at 9am only.

This changes when the agent wakes up, so the builder edits its schedule, not the instructions.

None of these edits needs more access or touches the Never rules. They change what Dunning watcher is told, not what the connections allow.

How it compares to other options

Dunning watcher beats the alternatives when you want a person to see who is failing to pay before Chargebee cancels them, and loses to them when you want recovery emails sent automatically.

Dunning watcher compared with Chargebee's dunning emails, A recovery tool, Checking Chargebee yourself
Compared onDunning watcherChargebee's dunning emailsA recovery toolChecking Chargebee yourself
Tells your team, not only the customerYes, in SlackNo, emails the customerUsually a dashboardIf you look
Sorts by risk of cancellingYesNoOftenIf you sort it
Days in dunning and attemptsYesNot to youYesYes
Contacts the customerNo, a person doesYesYesIf you do
Can cancel or refundTold not to; use a read-only keyCancels when retries endDepends on the toolUp to you
Setup effortConnect two accountsA few settingsA subscription and setupEvery morning

Chargebee's own dunning emails are still worth keeping on. They ask the customer to update their card. Dunning watcher tells your team who has not, so a person can step in.

A dedicated recovery tool is better when failed payments are a large share of revenue and you want automated retries and emails tuned for it. Dunning watcher suits a team that wants to see the list and act itself.

Frequently asked questions

Can Dunning watcher cancel a subscription?

It is told never to. The Chargebee connection can cancel with a Full-Access key, so connect a Read-only: All key if you want that enforced (how access works).

Does it email customers about their failed payment?

No. Neither connection can send email, and it is told never to contact a customer. Chargebee's own dunning emails still go out as you have set them.

What does days in dunning mean?

The days since the unpaid invoice fell due. It is shown with the number of retry attempts Chargebee has made.

What counts as at risk?

Retries run out on a subscription that is still active or non-renewing, or 21 or more days in dunning. You can change both.

Does it post card details to Slack?

No. It names the customer and the amount, and never posts card numbers, full email addresses or billing addresses.

Why did it post nothing today?

No invoice was in dunning and no payment failed in the last 24 hours. If Chargebee could not be read, it would have said so.

Is Dunning watcher free?

It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.

See who is failing to pay before they cancel

Connect Chargebee with a read-only key and Slack, choose the channel and switch on the schedule. Your first message lands on the next weekday at 9am.