Role-Based Email Addresses: What They Are and When to Use
Role-based email addresses such as info@ and sales@ go to a team. Here is how to spot them, when they are worth using, and how to find a real person instead.

Role-based email addresses are mailboxes named after a job or a function, such as info@, sales@ or support@, instead of a person. Mail sent to them usually lands with several people at once. That one fact changes how they behave in cold outreach, in list cleaning and in deliverability. This guide explains what they are, how to spot them and when you should still use them.
TL;DR#
- A role-based address belongs to a function, so more than one person reads it.
- They are common, easy to find and a weak fit for personal cold email.
- Treat them as a fallback. Look for a named contact first.
- Verify them before you send, like any other address.
What are role-based email addresses?#
A role-based address identifies a function inside an organization. It does not identify one human. Think of billing@example.com or careers@example.com. Whoever holds that job today reads the mailbox, and so might their colleagues.
The idea is old. RFC 2142 set out standard mailbox names for common services. It lists business names such as info, marketing, sales and support, and network names such as abuse, noc and security. Mail systems and spam filters still treat these names as special.
Common examples of role-based email addresses#
You will meet the same local parts again and again:
- Business functions:
info@,contact@,hello@,sales@,marketing@,support@,billing@ - People and hiring:
jobs@,careers@,hr@ - Press and partners:
press@,media@,partnerships@ - Technical and admin:
admin@,webmaster@,postmaster@,abuse@,security@ - No-reply senders:
noreply@,no-reply@,donotreply@
The last group is different. A no-reply address is not read at all, so there is no point in writing to it.
How to tell a role-based address from a personal one#
Look at the part before the @. If it names a function, treat it as role-based. If it holds a first name, a last name or initials, it is probably personal.
A simple check works for most lists:
- Export the local part of each address.
- Compare it to a list of common role names.
- Flag exact matches and obvious variants, like
sales-team@orinfo.uk@.
A role list will miss odd cases. A founder at a small company may use hello@ as their own inbox. So flag the address, then decide by context, not by a hard rule.
Why role-based addresses matter for deliverability#
Many senders and verification tools label these addresses as higher risk. The reason is practical:
- Shared inboxes get more mail. A team mailbox can receive a lot of messages, so people tend to skim it.
- Complaints come from more people. If one team member marks your message as spam, the whole domain may notice.
- Some forwarding is automatic. Mail to a role address often fans out to a group, which makes replies harder to attribute.
None of this makes the address invalid. It means the address deserves a second look before it enters a campaign.
When you should email a role-based address#
Role-based addresses are the right choice in some cases:
- The request fits the function. A press pitch to
press@, a partnership idea topartnerships@, or a support question tosupport@. - You have no named contact yet. An
info@mailbox can be a way to reach a small company and ask who owns the topic. - The company asks you to use it. Some websites publish one contact address and nothing else.
Keep the message short and ask one clear question. A line such as "Who handles vendor security reviews at your company?" gives the reader an easy way to forward you on.
When you should avoid them#
Skip role-based addresses when you want a one-to-one conversation. A personalized email to sales@ reads like a mass email, because the reader cannot tell whether it was meant for them. Replies are also slower, since nobody owns the thread.
For outbound prospecting, name the decision maker. That means finding a person, a title and a verified address.
How to find a named contact instead#
Start from the company domain and work toward a person:
- Use domain search to list the addresses a company has made public, and separate the personal ones from the role-based ones.
- Use the email finder with a first name, last name and domain when you already know who you want to reach.
- Check the company's team or about page for names and titles.
- Confirm the address works before you send.
The company email pattern checker helps when you know the person but not the address format.
How to handle role-based email addresses in your list#
Decide on a policy for role-based email addresses once and apply it everywhere:
- Cold outreach: remove them, or send them to a separate low-volume sequence.
- Newsletters and product updates: keep them only if the owner of the mailbox opted in.
- Transactional mail: these are fine, because the mailbox is the right recipient.
- Support and billing contacts: keep them in your CRM, tagged as role-based, so nobody sends sales mail by mistake.
Tagging beats deleting. A role address you hold today can help later, for example when a named contact leaves.
Verify before you send#
Role-based email addresses can be valid or dead like any other. Run it through an email verifier before you send. Verification checks the syntax, the domain and whether the mail server accepts the mailbox. It cannot tell you whether anyone reads it.
If you have a large list, the bulk tool lets you check many addresses at once, so you can remove bad ones before they hurt your sender reputation.
Frequently asked questions#
Are role-based email addresses bad?#
No. They are normal and often valid. They are just a poor fit for one-to-one outreach, because several people may read them and nobody owns the reply.
Is info@ a role-based address?#
Yes. info@ is among the standard names listed in RFC 2142 and is one of the most common role-based addresses.
Can I send cold email to role-based addresses?#
You can, but results are usually weaker than a named contact. If you do, keep the message relevant to the function and ask who the right person is.
Do email verifiers flag role-based addresses?#
Many do. They may mark the address as valid but "risky" or "role". Check how your tool labels them before you filter your list.
How do I find a person's email instead of a role address?#
Search the company's domain, then use a first name, last name and domain with an email finder. Verify the result before you send.
Next step#
Find the person behind the role. Try the Tomba Email Finder to look up a named contact from a name and a company domain, then confirm it with the Email Verifier.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA