Definition
A role-based email address is tied to a job or department rather than a named person. Common examples are info@, sales@, support@, admin@, billing@, hr@, office@, contact@ and noreply@. Messages to these addresses often land in a shared inbox, a ticketing system or a distribution list that forwards to several people.
Why it matters
Role addresses usually exist and accept mail, so they rarely hard-bounce. The trouble shows up later.
Nobody signed up as "sales@". Whoever reads that inbox did not ask for your email, so they are more likely to ignore it or mark it as spam. On a distribution list, one complaint can come from any of several readers. For cold outreach, a pitch to info@ also tends to get forwarded nowhere.
Some email platforms restrict role addresses on import or warn about them, because of the complaint risk.
Context changes the answer. At a five-person company, info@ may be the owner's main inbox and a perfectly good contact. For a supplier you already work with, accounts@ is exactly where invoices should go. For a cold sequence to a large company, a named person is almost always better.
How SimpleCold handles it
SimpleCold flags role-based addresses during verification. They come back Risky with the status role_address and the reason "This is a shared role address, like info@ or sales@, not a person." Risky here does not mean the mailbox is fake. It means a person may not be on the other end, so you should decide on purpose. Many teams keep role addresses for existing customers and suppliers, and drop them from cold campaigns.