Campaign paused for reputation and suspended sending

4 min read71
Copy for AI:

A campaign that generates too many spam complaints or bounces does not only hurt itself: it drags down the reputation of the domain and the sender, and the next campaigns start landing in spam. That is why WiseData Mail follows each campaign while provider responses come in and acts in steps, before the damage becomes hard to undo. Each step's limits are the ones shown on the Spam complaints and Bounces cards in Results › Deliverability.

The three steps

  • Warning — the campaign went past the recommended level. Nothing stops; the account owner gets an e-mail to review the list before the next send.
  • Paused campaign — the campaign stops midway and shows as Paused (reputation). The rest of the account keeps sending.
  • Account sending suspended — no campaign goes out, and everything that was going out is paused.

At each step the account owner gets an e-mail, even when someone else on the team, or Agência Norte, sent the campaign. The numbers are each campaign's own, not the account average: a bad campaign can be paused while the Deliverability cards are still green.

Paused campaign

Say the 2026 harvest launch campaign, sent to the Store customers list, was paused midway. Deliverability shows a warning at the top, and the campaign keeps the reason, with the rates that led to the pause. What was already delivered is not sent again; what was left waits.

Before resuming, find out where the complaints came from. Old lists, contacts who never asked to receive and addresses imported from another source are the usual causes. If the list is the problem, resuming just sends the rest of the campaign to the same people who are complaining.

In the campaign, Resume sending picks up where it stopped. Resuming means taking on the risk: who resumed is logged, and it can only be done once per campaign. If it crosses the limit again, it stays stopped until our team reviews it. Resuming also does not work while account sending is suspended.

Account sending suspended

When the suspension happens, a warning banner shows up in Deliverability, on the campaign screens and in Setup › Sending, with the reason and the date. While it lasts:

  • no campaign goes out, and those that were going out are paused;
  • sending through the API is refused too — the pedido-confirmado transactional e-mail does not go out;
  • turning Sending enabled off and on does not fix it: the switch is yours, the suspension is not.

Only our team lifts the suspension, after reviewing the account. Contact support and, meanwhile, do the review you will be asked for: remove from your lists anyone who did not ask to receive and anyone who never opens. After the release, the campaign that caused the suspension does not restart on its own.

How to avoid getting here

  • Send to people who asked to receive. For Casa Moura, people who bought at the store and agreed to get e-mails — not a third-party list.
  • Prefer engaged audiences, such as the Bought in the last 90 days segment, over sending to the whole base at once.
  • Open Deliverability after each large send and act on the warning that rates went past the recommended level, which comes before the pause.

Where to go next

  • Understand the deliverability indicators — what each number measures.
  • Blocked — who complained or bounced and no longer receives.
  • Campaigns — where Resume sending lives.

In short: past the recommended level the owner is warned, past the limit the campaign is paused and can be resumed only once, and when the account is suspended nothing goes out, not even through the API, until our team releases it — in every case, the fix is to review the list before sending again.

Was this article helpful?