·6 min read·by ByeBouncer

Role-based emails: when to keep shared inboxes

Role-based email addresses like info@ and sales@ are shared inboxes, not invalid ones. What you can check, what you can't, and how to decide whether to keep them.

emailrole-basedlists

Role-based email addresses such as info@, sales@ or support@ are shared inboxes: they belong to a function, not a person. Being shared doesn't make them invalid or low-intent. For a small business, info@ may be the only real channel. What changes is what you can send them and under which permission. This article separates the technical data from your commercial policy so you decide what to do with each one.

What a role-based address is (and why it shows up in your lists)

A role-based address is tied to a position or team: info@, contact@, sales@, admin@, billing@. Several people read the same inbox, or the message is forwarded to a group. They end up in your lists because people type them when they don't want to share a personal address, or because sales copied them from a website.

Examples here are fictional: sales@example-company.com doesn't belong to anyone real.

Why sending platforms are wary of them

Email platforms don't all treat these addresses alike. According to its help documentation, Mailjet warns that marketing to role addresses can hurt your sender reputation if they make up a large part of your list, and advises using them only with clear, provable consent. Pipedrive doesn't allow campaigns to them at all. Constant Contact, by contrast, sends to most and blocks a specific list of roles. So there is no universal rule, only each platform's policy.

The logic is simple. When several people see the same message, one spam report is enough to count as a complaint. And permission for marketing comes from a person, not an inbox. A caveat: these sources are software vendors with a commercial interest. Read them as platform policy, not law.

laura@example-company.cominfo@example-company.comvs
The same domain can have a personal inbox and a shared one, with different risks and uses.

What you can check about a shared address

An email validation lets you separate three things: whether the format is correct, whether the domain can receive mail (MX records), and how the server responds when the mailbox is queried. The result can also flag attributes such as being a role account. That describes the address; it says nothing about the intent of whoever reads it.

What no validation can tell you: that anyone will read the message, that they care about your offer, or that you have permission to send marketing. A server accepting the message doesn't guarantee inbox placement either. And an «undetermined» result doesn't mean invalid: many domains accept everything and don't allow mailbox checks.

How to decide based on your process

ByeBouncer returns the data separately and doesn't decide for you: there is no overall score and no delete order. You set the policy, based on what each address is used for.

Validate the listFlag role accountsSegment by useDecide per segment
A policy decision, not an automatic filter: data first, then your rule.

An example with a small list

Picture a fictional list of 200 contacts from a small supplies business. Among them are 18 addresses like info@, sales@ and contact@. Delete them all and you may lose the only channel to ten customers who never gave a personal address. Send all of them the newsletter and some platforms will halt your campaign, and complaints from a shared inbox count like any other.

The middle path is to validate the whole list, flag the role accounts and move them to their own segment. That segment gets service notices, and for marketing you wait for consent or for a reply that gives you a named contact. The decision is then documented and reviewable instead of a deletion nobody remembers.

What ByeBouncer does not do with these accounts

To avoid overpromising: validation can't know who reads a shared inbox, doesn't measure interest or commercial intent, and doesn't certify that consent exists. It also doesn't block or delete anything by itself. It returns format, domain, mailbox response and attributes such as role account; your system applies the criteria.

Questions before excluding a contact

  1. What will I use this address for: service notices or marketing?
  2. Do I have recorded consent, and from whom?
  3. Is there a named contact at the same domain?
  4. Does my sending platform block this kind of address?
  5. Would excluding it mean losing the only channel to that customer?

In short: a shared address isn't a bad address, it's an address with a different use. First validate that it exists and receives mail, flag which ones are role-based, and apply a different policy per type of send. Excluding blindly loses legitimate contacts; sending blindly hurts your reputation.

See how email validation works →

Create an account and validate your first list →

Sources reviewed

Related guides