Plan: Pro and above (pairs with promises).
A broken promise is simply: the date arrived, the balance is still open, and the commitment was not met.
What the product aims to do
- Detect when a promise date (plus any grace the product applies) passes unpaid.
- Surface that event so it does not disappear into a generic overdue list.
- Allow chasing to step forward again on the sequence — not with invented threat wording, but along the tones you already configured (Friendly → Standard → Firm → Final).
What you should do
- Open the invoice and read the promise note and amount.
- Check whether a payment landed late (sync delay is normal — accounting can take a day or two).
- Decide: new promise, payment plan, manual pause, or resume the ladder.
- If Firm or Final steps are next, they still wait in Activity → Approvals when approval is on (default on every plan).
What not to do
- Do not free-type legal threats into a message. Wording that names court, enforcement, or similar is held for extra confirmation and logging.
- Do not treat a missed date as permission to harass. One clear follow-up beats a stack of heated messages.
If the customer needs structure instead of a single new date, move them to a payment plan rather than stacking broken one-off promises.