A role based email is an address tied to a job, department or function rather than to one named person, such as info@, sales@, support@ or office@. Several people may read it, nobody may read it, and whoever does read it usually did not ask to hear from you.
That is the whole definition. The useful part is what it means when these addresses show up on your lead list.
Why it matters for outreach
When you scrape or buy a list of local businesses, a lot of the emails you find will be role based. Small businesses often publish only an info@ or contact@ address on their website. So you cannot simply delete them all, but you should treat them differently from a named address.
A few reasons:
- Nobody owns the message. A shared mailbox is read by whoever has time. Your pitch may be forwarded, ignored, or archived by a receptionist who has no say in buying. If you want to understand how these inboxes work from the other side, see shared inbox.
- Complaints are easier to make. The person reading did not give you the address personally, and clicking "report spam" costs them nothing. Complaints hurt your sender reputation, so keep an eye on your spam complaint rate.
- Personalization lands flat. "Hi {{params.firstname}}" breaks when there is no first name, and "Hi there" to info@ reads like a mass mailing.
- Some providers and verifiers flag them. Many email verification tools mark role addresses as a separate category or as risky, because they tend to bounce or complain more. Treat that as a signal, not a ban.
A concrete example
Say you run a web design agency and you pull 200 dental clinics in one city. For a typical clinic, you might end up with:
- reception@smiledental.com (role based, listed on the contact page)
- dr.patel@smiledental.com (named, found on the team page)
If you email reception@, the front desk sees a message about website redesign, has no budget, and may delete it. If you email Dr. Patel, the owner reads a note about her own site.
If reception@ is the only address you have, it is still worth sending, but write for the gatekeeper. Something like:
Subject: Quick question for whoever handles the website at Smile Dental
Hi, I noticed the booking page on smiledental.com does not load on mobile. Could you pass this to whoever looks after the site? Happy to send a short screenshot showing the issue.
That message gives the reader an easy job (forward it) and a reason to do it. It uses {{params.name}} and {{params.website}} details naturally instead of a fake first name.
Common mistakes
Treating role addresses like named contacts
The same template with "Hi {{params.firstname}}" goes to everyone, and the role addresses get "Hi ," or a wrong name. Split your list first. Our page on merge tags covers fallbacks so a missing field does not break the greeting.
Deleting every role address
For a small local business, info@ may be read by the owner. A plumber or a cleaning company often has one inbox and one person. Removing them shrinks your list for no reason.
Sending long sequences to shared inboxes
Five follow-ups to support@ is how complaints happen. Keep role-address sequences shorter, and stop when someone asks.
Skipping the unsubscribe link
The person reading a shared inbox is not the person who would have opted in to anything. A clear way out reduces complaints. See unsubscribe links in cold email. Rules on commercial email differ by country, so check what applies to you; this is not legal advice.
Using role addresses for account-based targeting
If you are scoring leads, a named decision maker should rank higher than a generic inbox. Factor this into your lead scoring.
How to handle role addresses on your list
- Look for a named contact first. Check the team or about page, the owner's name on the Google profile, or social profiles.
- Verify before sending. Run verification and decide how you treat the role category instead of letting it decide for you.
- Segment. Put named contacts and role addresses into separate folders or campaigns with different copy.
- Write for a forwarder. Short, specific, with one clear ask: pass this to the right person.
- Watch your numbers by segment. If role addresses drag down your reply rate and push complaints up, cut that segment's volume.
Where GetClient fits
GetClient's Google Maps scraper returns emails found for each business, plus the owner's name and title with a confidence score where that is public. That makes it easier to pair a role address with a real person. You can verify the list, save named and role leads into separate folders in My Leads, and run different campaigns for each from your own Gmail, Outlook or SMTP mailboxes. New accounts get 100 free credits; see plans and credits.
For the bigger picture on building the list in the first place, read how to build a lead list.