A hard bounce is a verified statement about the world. The mail server on the receiving end has confirmed that the address does not exist, which in a corporate domain almost always means the person who held it has gone. That confirmation arrives free, within seconds of a send, and in most organisations it travels no further than a suppression list.
Marketing platforms handle bounces the way they were designed to handle them, which is as a deliverability problem. The address is flagged, future sends are blocked, and sender reputation is protected. All of that is correct and none of it changes the contact record sitting in the CRM, where the same person still works at the same firm, still appears in the territory count, and still gets counted in the coverage report that goes to the board.
Hard, soft, and the ones that never bounce at all
A hard bounce is permanent. The mailbox does not exist, the domain does not resolve, or the server has rejected the address outright. A soft bounce is temporary by definition, a full mailbox or a server having a bad morning, and platforms retry accordingly.
The category that causes the most trouble is the soft bounce that repeats. An address failing quietly across four consecutive sends over three months is not experiencing four bad mornings. Most platforms will keep trying, because each individual failure looks recoverable, and the record stays clean while the person behind it has been unreachable since autumn.
Catch-all domains complicate the picture from the other direction. A server configured to accept mail addressed to anything at the domain will never bounce, no matter who has left. The mail is accepted and discarded. Silence from a catch-all domain is not evidence that anyone is still there, which means bounce data is reliable when it arrives and proves nothing by its absence.
A bounce is the only piece of research a marketing platform performs without being asked.
What the pattern says that the individual record does not
One bounce describes a person. Several bounces from the same domain inside a short window describe an organisation. A firm that has migrated to a new email convention, merged with another business, or gone through a restructure produces a cluster, and a cluster is visible in the send report weeks before any of it reaches an account record through the usual channels.
Reading that requires someone to look, and the looking is the part that rarely gets scheduled. Bounce reports are treated as a post-send hygiene task, reviewed for the rate rather than the contents, cleared, and closed. The rate is the least informative number in the report.
Getting the fact back into the record
The gap is procedural. A bounce updates the marketing platform because the marketing platform generated it. Moving it into the CRM as a business fact, a contact flagged for verification, an account flagged for a coverage conversation, requires a rule that somebody has to write and an owner who has to act on the queue it creates.
Firms that do this well keep the two states separate. Unmailable is a sending status. Departed is a business fact. Collapsing the first into the second automatically will eventually retire a contact who was on parental leave with a suspended mailbox, and treating them as unrelated leaves the CRM describing a distribution network that stopped existing some time last year.
Every organisation runs on records that were true when they were written. The systems that generate corrections tend to be the ones nobody thinks to ask.
Q: Should a hard bounce automatically update the contact record in the CRM?
An automatic flag for review is safer than an automatic status change. A hard bounce reliably proves the mailbox has gone, which usually but not always means the person has left. Routing the bounce to a verification queue captures the fact without a system silently retiring contacts who are still employed.
Q: How many soft bounces should be treated as a hard bounce?
Three consecutive failures across separate sends is a common threshold, and the interval matters more than the count. Three soft bounces in one week is likely a server issue. Three across three months, with successful sends to the same domain in between, indicates the individual address is gone.
Q: Does removing bounced contacts distort year on year campaign reporting?
It changes the denominator, so comparisons need a note against them. The alternative is worse. A list padded with unreachable addresses reports a lower open rate every cycle, and the decline gets attributed to content or timing rather than to a list that has quietly stopped describing anyone.
Q: Why do some domains never produce bounces even after people leave?
Catch-all configurations accept mail sent to any address at the domain and discard what has no recipient. Nothing is returned to the sender, so the campaign reports a successful delivery. Engagement data becomes the only remaining signal, and a long run of silence from a previously active contact is worth checking manually.