A role-based address represents a function or team rather than one named person. Familiar examples include info@, sales@, support@, billing@ and admin@. These addresses are not automatically invalid; many are important, actively monitored business inboxes.
Why teams classify role accounts
Ownership can change, several people may read the mailbox and consent or personalization assumptions can differ from a named contact. An outreach workflow may review them separately, while a customer-support or invoicing workflow may consider them ideal.
Separate classification from deliverability
“Role-based” describes the mailbox type. “Deliverable” describes the technical result. Keep those ideas separate so your product can accept a working support inbox while still recognizing it is not a personal address.
Recommended handling
- Do not delete role accounts by default.
- Define a policy for each use case.
- Avoid personalizing a shared mailbox as though it were an individual.
- Track engagement and complaints independently.
- Honor opt-outs and suppressions regardless of mailbox type.
Start with a representative sample
Create an account, use the included credits and review the classifications before committing a larger database.