> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useboom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Message balance

> How your prepaid message balance pays for WhatsApp, what Boom shows when it runs low or below zero, and how to add funds.

If your workspace pays its WhatsApp messaging costs from a prepaid balance,
that balance is your **message balance**. Every WhatsApp message you send
draws on it. You add funds to it with the card on file, and Boom tells you in
the app when it needs attention.

Workspaces billed monthly don't have a message balance: their messaging costs
are on the monthly bill, and none of this page applies to them.

## Where to see it

Go to **Settings › Billing › Plan and usage**. The **Message balance** card
shows what you have left, your last top-up and your payment method. **View
activity** lists every message and top-up.

## Add funds

1. On the **Message balance** card, click **Add funds**.
2. Enter an amount and confirm. It's charged to your card right away, and the
   balance updates as soon as the payment clears.

You need the billing permission that lets you buy (the same one as buying
credits). Members without it still see when sending is paused, but not the
button: ask an admin of your workspace to add funds.

## What Boom shows, and when

| What you see | What it means | What still sends |
| - | - | - |
| **Low balance** or **No balance** | Your balance is running low, or it's at \$0.00. A notice you can dismiss appears at the top of the app, except right after you move from monthly billing to a prepaid balance, before you've spent anything. | Everything |
| **Below zero** | You've spent more than your balance. New messages add to what you owe. Add funds to cover your WhatsApp messages. | Everything, for now |
| **Inbox paused** | WhatsApp replies and templates your team sends from the inbox aren't going out until you add funds. Everyone in the workspace sees a notice at the top of the app and above the WhatsApp composer. | Campaigns, journeys, AI replies, verification codes, and inbox messages on other channels |
| **Sending paused** | Boom has paused WhatsApp sending on your account: campaigns, journeys, AI replies on WhatsApp, and rewards. Your team can still reply from the inbox, and those messages are charged as usual; the notice above the WhatsApp composer reminds them the AI isn't answering. Adding funds doesn't resume it: contact us at [support@useboom.ai](mailto:support@useboom.ai) and we'll help you. | On WhatsApp, verification codes and your team's replies from the inbox. Email and other channels keep sending |

When your balance is below zero or the inbox is paused, you have two buttons:

* **Add funds** opens the top-up with a suggested amount you can change.
* **Pay what you owe** opens the same top-up, starting at what you owe (or at
  the minimum top-up, if you owe less). Nothing is charged until you confirm.

> [!NOTE]
>
> A message that couldn't be sent while the inbox was paused stays in the
> conversation, marked as not sent, with **Add funds**. Once funds are added,
> you can send it again.

## Message balance and credit packs

Credits and your message balance pay for different things. **Credits** run
your AI conversations; **WhatsApp messages** are paid from your message
balance. Buying a credit pack doesn't add to your message balance, and it
doesn't resume sending that is paused or below zero (see the table above).

On **Settings › Billing › Buy credits** you see the credit packs for your plan:
5,000, 15,000 and 50,000 credits, priced from your plan (Basic, Growth or Pro).
Packs last 12 months. If your plan has no packs yet, the page says so and gives
you the address to write to, and we add the credits for you. If you change
plans while automatic top-up is on, Boom turns it off and asks you to choose a
package from your new plan's packs.

## If your workspace belongs to a partner

Some workspaces get their credits from a partner. Your message balance is
still your own: you pay it with your own card, and everything on this page
works the same way.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.