A role-based email address represents a job function or department instead of an individual. Common examples include info@, sales@, support@, admin@, and hello@. Multiple people usually monitor these inboxes, and no single named person owns the address.
For cold outreach and marketing, role-based addresses are problematic. They tend to have higher spam-complaint and unsubscribe behavior because messages arrive without a personal relationship, and mailbox providers sometimes weigh complaints from them heavily. Personalized selling is nearly impossible when you do not know who is reading.
Detection is straightforward because the signal lives in the local part of the address. Matching the portion before the @ against a list of known role keywords flags these addresses reliably, which is why role detection is a standard step in list cleaning and lead qualification.
That said, role-based addresses are not universally bad. For support inquiries, partnership requests, or reaching small businesses that publish only a general address, they can be the right and only channel. The key is to segment them, set expectations accordingly, and avoid treating them like a named prospect in a personalized sequence.