# Why collections are paused

- HTML page: https://www.billabex.com/en/help/troubleshooting/why-collections-paused/
- Language: en
- Version française: https://www.billabex.com/fr/aide/depannage/recouvrement-en-pause.md
- Updated: 2026-07-01
- Site index: https://www.billabex.com/llms.txt

<section class="help-summary" aria-labelledby="in-short"><h2 id="in-short">In short</h2><p>A pause protects the account when an automatic action would be inappropriate. It may be manual or linked to a payment promise, insolvency proceeding, invalid contact, or task waiting for your answer. Review the reason and history before resuming: removing the signal without resolving its cause can trigger an unsuitable follow-up.</p></section>

## Expected result

The pause reason is understood and collections resume only after its corresponding blocker is gone.

## Before you start

- Open the affected account with its recent history.
- Check visible tasks, promises, contacts, and legal alerts.

## Procedure

1. Locate collection state and the date it was suspended.
2. Read recent exchanges and find the task or event associated with that date.
3. Resolve the cause: provide an answer, correct a contact, wait for a promise, or verify legal status.
4. Resume collections only when the case can safely receive another communication.
5. Check the next action proposed by the agent after resuming.

## What Billabex does

A pause blocks new collection actions without deleting account history. On resume, the agent reassesses current context instead of blindly replaying an outdated communication.

## If the result is not what you expected

- If resuming seems ineffective, look for another active blocker.
- Do not resume an account flagged for insolvency proceedings without appropriate validation.
- An overdue promise may require recalculation before the next communication appears.