Role-Based Email Detection
A role-based email address is one addressed to a function rather than a person — admin@, support@, sales@, billing@, hr@ — rather than an individual mailbox. Detection matches the local part of the address (before the @, and before any plus-addressing suffix like +billing) against a maintained list of known role prefixes. It's not inherently fraudulent — most role addresses are completely legitimate — but it changes what the address can tell you: nobody is individually accountable for it, it's often monitored by multiple people or a ticketing system, and it's a weak signal for identifying a specific person behind a B2B lead or CRM record.
What counts as a role-based address
The local part — everything before the @ — is checked against a maintained list of known role prefixes: admin, administrator, info, contact, support, sales, hello, help, billing, accounts, office, enquiries, marketing, webmaster, security, privacy, careers, jobs, hr, and finance are the current defaults. Any of these, at any domain, is treated as role-based: support@yourcompany.com and support@acmecorp.com both match, since the signal is about the function the address represents, not which organization it belongs to.
How plus-addressing is handled
The match happens against the local part before any plus-addressing suffix, so support+billing@example.com and support+urgent@example.com both still match support. This matters because plus-addressing is commonly used specifically on role accounts to route or tag incoming mail (a ticketing system tagging the department, a person appending a category to their own role inbox) — stripping the suffix before matching means those variants aren't accidentally treated as individual, non-role addresses just because of a routing tag.
A role-based address is not inherently a bad sign
This is worth stating plainly: support@ and sales@ addresses are completely normal, and a large share of legitimate B2B correspondence goes through them deliberately. Role-based detection isn't a fraud signal in the way a disposable domain is — it's a different kind of fact about the address, and what it should mean depends entirely on context.
Why context changes how much it matters
| Context | What a role-based address usually means |
|---|---|
| Consumer signup | Unusual — most individual signups use a personal mailbox, so a role address here is a mild anomaly worth weighing alongside other signals |
| B2B lead / CRM import | Weak signal quality — you can't attribute the lead to a specific person, and it's often shared across a team, which matters if the goal is finding a real decision-maker |
| Marketplace listing | Depends on the marketplace — a business seller using sales@ is normal; an individual seller using it is more unusual |
| Payment / checkout | A weaker signal than in lead generation — plenty of legitimate purchases go through a company billing@ or accounts@ inbox |
This is exactly why context-aware weighting exists: the same role_based: true fact is worth a meaningfully different amount depending on whether context was set to signup, b2b_lead, marketplace, or payment when the check was made. See Email Risk Scoring Explained for how context weighting works across all signals, not just this one.
Keeping the prefix list current
Role prefixes are maintained as a managed list rather than hardcoded — new prefixes can be added, or existing ones deactivated, without a deployment. That matters because what counts as a common role address shifts slowly over time and varies somewhat by industry, and a static list would eventually drift out of date.
FAQ
No — role_based is one signal among several that feed into the overall risk score, weighted by context. It's not treated as disqualifying on its own, since role addresses are frequently legitimate.
The current defaults include admin, administrator, info, contact, support, sales, hello, help, billing, accounts, office, enquiries, marketing, webmaster, security, privacy, careers, jobs, hr, and finance — matched at any domain.
Not in the default prefix list — noreply addresses are typically outbound-only sending addresses rather than a role a real person or team monitors, which is a different concept from the shared-inbox role addresses this check targets.
A B2B lead's value often depends on identifying a specific, reachable decision-maker — a role address makes that harder, since you can't tell who's actually behind it or whether it's monitored at all. See How to Detect Fake Leads Using Email Data for the broader picture of lead-quality signals.