How to Address Multiple People in an Email (Rules and Examples)

This guide is part of our broader coverage of client communication for Virtual Assistants and Executive Assistants.

The two-name rule

For two recipients, always name both.

Right: Hi Sarah and James,

Wrong: Hi both, / Hi you two, / Hi guys,

Hi both is technically fine but reads impersonal. Hi you two is casual to the point of unprofessional in most contexts. Hi guys is off-limits when either recipient is not male-identifying, and increasingly avoided across the board.

Order the names by seniority, or alphabetically if seniority is equal. Small courtesy, real signal.

Three or four recipients: named or grouped?

Depends on why they are all on the email.

Name each when everyone in the To line has to act, decide, or reply. Example: you are asking three department heads to sign off on a plan.

Hi Sarah, James, and Priya,

Use a group greeting when the message is directional (announcement, update, information share) or when only some of them need to act.

Hi all,
Hi team,
Hi everyone,

Hi team is best when the recipients are actually a team (they work together, know each other, have a shared context). Hi all works for any group. Hi everyone is slightly warmer, slightly less common, still safe.

Five or more recipients: group greeting only

At five recipients or more, naming each person in the greeting makes the greeting longer than the message. Group greetings are the only readable option.

Hi all,
Hi everyone,
Hi team,
Hi [team name],

If the group has a name (Ops team, Product leadership, Board members), use it. Hi Ops team, reads more purposeful than Hi all.

To vs CC when multiple people are involved

The most consequential decision in a multi-recipient email is who goes in To and who goes in CC. Most VAs and EAs get this wrong at first.

• To is for people who owe you something: a reply, an action, a decision. Anyone in To is being asked to engage.
• CC is for people who need to know but should not be expected to reply. CC is information, not action.
• BCC is for people who should see the message but not be visible to the other recipients. Use rarely and deliberately.

The single most common failure is asking a question of someone who is in CC. If Sarah is in CC and the email says "Sarah, can you share the numbers?", Sarah is being asked to do something, so she belongs in To. Move her.

When to include a CC in the greeting

Almost never. The greeting is for the people you are speaking to, meaning the people in To. CCs are audience.

Two exceptions:

1. You want to explicitly acknowledge the CC in the flow of the email. Example: "Sarah, following up on the budget question below (looping in Priya on our side for context)." Priya is in CC, but she gets a mention because Sarah needs to know why she is there.
2. The CC is very senior and needs the deference of being named. Example: emailing a peer and CC-ing their boss. Naming the boss in the greeting signals awareness of the audience without pulling them into the conversation.

Both exceptions are situational. In the default case, name only the To recipients.

Ordering names in a multi-recipient greeting

Two accepted orderings:

• By seniority, most senior first. Formal contexts, external stakeholders, first outreach.
• Alphabetical, either by first or last name. Casual contexts, internal peers, group discussions.

Never order by relationship (person you know best first) unless the group is truly informal. It reads as favoritism to the person who ends up second or third.

What to do when the group is mixed formality

Sometimes one recipient warrants Hi and another warrants Dear. Two options:

1. Default to Hi. In modern professional writing, Hi works up to almost every level of seniority. The more junior person will not be offended by Hi; a more senior person will assume the register is chosen deliberately.
2. Send two emails. If the two recipients would genuinely be better served by different tone (one a founder, one a vendor), send separate emails with tailored greetings. The efficiency loss is trivial. The clarity gain is not.

Greeting a group that includes people you have never met

Two lines in the opening:

Hi Sarah, James, and (introducing myself to Priya),

Priya, we haven't met. I am [name], the executive assistant to [client name]. [Sarah] suggested I loop you in on this thread.

The parenthetical in the greeting signals the shift. The second line introduces you before asking anything. Skipping introductions in a group thread is the fastest way to have a new recipient tune out.

When to use no greeting at all

In an ongoing internal thread with the same recipients, you can drop the greeting after the first two or three exchanges. Everyone knows who is talking. Repeating Hi all, at the top of every reply reads as bureaucratic.

Rule of thumb: if the thread has more than three back-and-forths in one day, drop the greeting for replies four onward.

Do not drop the greeting in external threads, formal contexts, or threads with senior stakeholders. Always keep it for first emails, external outreach, and anything going to a boss or a client of the client.

For VAs and EAs writing group emails on behalf of a client

The client's default group greeting goes in the tone sheet (see our task management guide's section on context-switching between clients). Match it every time. Recipients notice when the pattern breaks, even if they cannot articulate why.

If in doubt, Hi all is safe. If in doubt about that, Hi everyone is safer.

Related: How to End an Email Professionally and Email Etiquette at Work.

When to CC, when to BCC, and the reply-all trap

Group email addressing is only half the challenge. The other half is deciding who gets what visibility.

To vs. CC vs. BCC decisions. The To field is for people expected to act. The CC field is for people who need visibility but no action. BCC is for people who need to receive the message without other recipients knowing they were included.

For VAs and EAs, the two most common mistakes:

• Putting the client's team on CC when they should be on To. If the client's team members are being asked to act, they go in To. CC signals "you can safely ignore this," which is not what you meant.
• BCC'ing yourself as a paper trail. Instead, use the Sent folder. BCC-to-self clutters your inbox and looks unprofessional if it accidentally becomes visible.

The reply-all trap. When a client forwards you a thread to reply on their behalf, check the recipient list before hitting reply-all. If the original thread has an external distribution list (clients@company.com or board@), reply-all sends to all of them. Instead, reply only to the direct sender unless the client explicitly asks for a wider distribution.

One rule of thumb from experienced EAs: if the thread has more than four recipients and you were forwarded in, reply directly to the client who forwarded you and let them decide who else to include. This avoids at least one embarrassing wide-audience blunder per year.