---
id: KB-CD-003
url: https://app.codecontract.io/help/credits-and-billing/keeping-credit-spend-under-control
idioma: en
categoria: creditos
audiencia: administrador
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CD-001, KB-CD-002, KB-CD-017, KB-CD-019]
citadoPor: [KB-CD-007, KB-CD-008, KB-CD-010, KB-CD-013, KB-CD-018, KB-CD-004, KB-CD-006]
enLaApp: https://app.codecontract.io/credits
---

# Keeping spend under control

_Know where it goes, cap it, and avoid running dry mid-send._

**Responde a:** see what credits are spent on · cap a team's spend · alert when credits run low · monthly consumption report

Spend usually goes out of control for one reason: someone launches a large batch without looking, or SMS is used by default where email would have done. Both show up in the breakdown.

## Where it goes in practice

| Item | Typical weight | How to reduce it |
| --- | --- | --- |
| Signature sends | The bulk | Little to do: it is the work itself |
| SMS and WhatsApp | The one that surprises people | Use only for people who do not read email |
| Document reading | Steady | Turn it off for types that yield no useful data |

## Three measures that avoid surprises

1. **Low-balance alert** — Set so it arrives with room to top up, not once it is gone.
2. **Check the breakdown monthly** — Ten minutes. It is where you spot SMS left on by default in a three-hundred-person process.
3. **Do the sum before a large batch** — Four hundred sends are four hundred. Checking the balance first avoids stopping halfway.

> [!WARNING]
> Running out mid-batch breaks nothing, but it splits the work in two and forces you to reselect whatever was left.

> [!NOTE]
> Before cutting, check whether the spend is saving you something. A signature send costs less than the time to print, courier and file the paper.

**Can I see spend per team?**

Yes, in the breakdown.

**Can I cap an individual?**

It is controlled by permissions: someone who cannot launch large batches cannot spend in bulk.

**Am I warned before an expensive batch?**

The total is shown before you confirm.

## Ejemplos

**Spend spikes one month for no obvious reason.**

- Looks at the breakdown
- Finds a 300-participant process had SMS on by default
- Restricts it to people without email

→ The following month returns to normal without anyone missing their notices.

**Spend is discovered at month end.**

- Checks consumption during the month

→ The correction arrives in time.

**An automated process consumes more than expected.**

- Reviews which activities it generates

→ Spend that runs on its own gets controlled.

**Nobody knows which department consumes what.**

- Checks consumption by department

→ The conversation happens with data.

**You want to set a limit and do not know where.**

- Estimates from previous months' consumption

→ The limit is set on a basis.

**The balance runs out mid-campaign.**

- Warns before reaching the threshold

→ The campaign is not interrupted.