Keep the invoice going to accounts@

A customer asks you to send invoices to [email protected]. Your verifier flags it as a role address. Keep it: the customer has told you where the invoice belongs.

Addresses such as accounts@, support@ and hello@ suggest a function rather than a named person. They may reach a team, one owner or a forwarding rule. The name alone doesn't tell you who reads them.

The useful question is how the address got onto your list.

If someone deliberately subscribed a shared inbox to service updates, keep that preference. If the address came from an unexplained import, investigate its source. Apply the same care you'd use for a named person's address.

Finding info@ on a website doesn't establish that its owner wants your newsletter. Equally, a role address on a consumer mailing list doesn't prove it was scraped. People choose unusual addresses for perfectly ordinary reasons.

Avoid promoting to mailboxes intended for abuse reports, security incidents or technical administration. Use them for the purpose they're published for.

Don't replace a requested role address with a named contact just because both exist in your CRM. The individual may buy the product while the shared inbox handles the bill. You need to preserve that distinction.