ZapBounce and Help Scout
Help Scout replies come from a shared mailbox on your own domain. Bounces from that mailbox attach to a domain your entire support function depends on.
Unlike a marketing domain, there is no version of this where the damage is contained to a campaign.
A shared support mailbox has one reputation
Every agent replies from the same address. Bounces generated by bad customer addresses accumulate against that one identity.
When the reputation degrades, support replies to good customers start landing in spam folders, which produces more tickets from people who think they were ignored.
That loop is self-reinforcing: more tickets, more replies, more sends from a degraded domain.
How the data moves
Verify customer addresses on creation
Help Scout creates customers from incoming mail and from agent entry. Both need checking.
Store the verdict as a customer property
Visible in the conversation sidebar, so an agent knows before replying.
Verify addresses agents type
An agent adding a customer from a phone call is the highest-risk entry point, because nobody hears an address correctly every time.
Monitor bounces from the shared mailbox
A rising bounce rate on a support mailbox is an early signal worth an alert.
Setting it up
- Create a customer property for the verdict and one for the check date.
- Verify addresses through the Help Scout API when customers are created.
- Show the verdict in the conversation sidebar through a custom app.
- Add a verification step wherever agents create customers manually.
- Batch-verify existing customers once.
- Alert on the bounce rate from the shared mailbox rather than reviewing it monthly.
Help Scout: common questions
Why is a support mailbox riskier than a marketing one?
Because there is no containment. Every agent replies from it, and a degraded reputation reaches every customer.
Where do the worst addresses come from?
Agents typing them from phone calls. Nobody hears an address correctly every time, and there is no feedback.
Should the verdict be visible to agents?
Yes, in the sidebar. An agent who sees an unconfirmed address will confirm it before promising a follow-up.
An address taken down over the phone
Say a customer calls about a refund and the agent creates the record while they talk. The customer says "j dot meyer at brightwell dot co" and the agent types j.meyer@brightwell.com. Two outcomes are possible, and they need different handling.
If brightwell.com has no mailbox for j.meyer, a check at creation comes back invalid while the customer is still on the line. The agent reads the address back, catches the extra letter, and the refund confirmation goes where it should. That's the case verification fixes.
If brightwell.com is a real company with a J. Meyer on staff, the address verifies as valid and the refund details go to a stranger. No verifier can catch that, because the mailbox exists. Reading the address back before hanging up is the only control, and it belongs in the call script for that reason. Our did_you_mean suggestion covers the gmial.com kind of slip, where the domain is one edit from a common provider. It won't cover this one.
What an agent should do with each result
A verdict in the sidebar only helps if agents know what to do with it, so write the rule down. Valid needs no action. Invalid means stop and confirm the address with the customer, through whichever channel they used to reach you, before promising an emailed follow-up.
Catch-all deserves a lighter touch. Many company domains accept every address, so the label will show up on a large share of business customers and it doesn't mean anything is wrong. Treat it as unconfirmed: reply as normal, and if the conversation matters (a refund, a contract, a password reset) ask the customer to confirm they received it.
Unknown means the receiving server wouldn't answer, which happens a lot with Microsoft-hosted domains. Re-check it later. Agents who see a warning on every third customer learn to ignore the field entirely, and then the invalid label stops working too.
Check a Help Scout export today
100 free checks a month, no card. Unknown results and duplicates are never billed.