Inspect the reason first
Check the original address input, vendor reason and observation date. A structural input error calls for a different response from a documented mailbox rejection. Do not invent a corrected address or substitute a guessed domain to make the row pass.
Retain necessary history
The next action may be exclusion from a specific workflow, review with the record owner, or a correction supported by legitimate evidence. Permanent deletion can remove information needed for suppression or audit. Follow the source system’s rules and the organisation’s retention requirements.
A practical exception note
Record the batch, original reason, proposed action and approval owner. If a correction is supplied, treat it as a new documented value rather than overwriting the old observation invisibly. The result should remain traceable without keeping unnecessary personal data indefinitely.
Put it into practice
A fictional result identifies an address as unfavourable because the supplied input is malformed. Before changing the business record, compare the prepared input with the controlled source. If the export introduced the error, repair the transformation rather than blaming the original contact or guessing a replacement address. If the source itself contains an error, obtain a correction through an appropriate authorised process. Keep the old observation associated with the value that was actually checked. A corrected value should not inherit an old technical result automatically. Separately decide what must remain for exclusion, history or incident review. Removing a row from a proposed sending file may be appropriate while deleting the entire customer record is not. Record the action taken and the evidence supporting it, and leave unresolved cases visible instead of forcing every unfavourable result into one irreversible cleanup operation.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Bouncer result FAQ — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27