WHY IT MATTERSYou have a list of people you need to email. Maybe it's 12 customers, maybe 1,200 prospects. You want each person to get a message that reads like it was written for them alone, without exposing the rest of the list and without landing in spam. The wrong way is to drop everyone into the To or CC field. The right way depends on how many people you have and how often you do this. This guide walks through the four methods and when to use each.
Individually vs To, CC, and BCC: What's the Difference?
Every email field decides who can see whom. Getting this wrong is the single most common privacy mistake in business email, and it is a real compliance risk under GDPR, which treats a leaked list of email addresses as a personal data breach. [GDPR.eu]
| Field | Who sees the addresses | Best for | How you do it |
|---|---|---|---|
| To | Everyone sees every address | A small group that already knows each other | Type each address in the To line and send one message |
| CC | Everyone sees every address | Looping in people who should be visible | Add visible recipients to the CC line of one message |
| BCC | No recipient sees the others | A one-off blast where addresses stay hidden | Put every address in the BCC line; one send, capped at your daily limit (500 on Gmail, 2,000 on Workspace) |
| Individually | Each person sees only their own address | Personalized outreach, sales, and any list you do not own consent for sharing | Run a mail merge (Gmail multi-send, YAMM, or Word Mail Merge in Outlook) or an outbound tool that sends one personalized email per person |
The key distinction: BCC hides addresses, but everyone still gets the exact same message in a single send. "Individually" means each recipient receives a separate email, addressed only to them, that can carry their own name, company, and details. That difference matters for both privacy and reply rates.
Why Mass BCC Hurts Your Deliverability
BCC feels like the safe shortcut. It hides addresses, so the privacy problem is solved. But mailbox providers treat a single message blasted to dozens of BCC recipients as a classic spam signal. Spam filters look at exactly this pattern: one identical body, many hidden recipients, no personalization.
Here is what works against you when you BCC a large list:
- Identical content to many inboxes looks like bulk mail, which filters downrank by design.
- No personalization tokens means the message has none of the signals that legitimate one-to-one email carries.
- Sender reputation damage compounds. Gmail and Yahoo now require bulk senders to keep their spam complaint rate below 0.3% and to authenticate with SPF, DKIM, and DMARC, or messages get blocked or filtered. [Google]
- One reply-all accident on a mishandled thread can still expose the conversation, and BCC does nothing for engagement metrics that providers reward.
Email is still the workhorse channel, with an average return of roughly $36 for every $1 spent according to Litmus, so protecting deliverability is protecting revenue. [Litmus] Burning your domain reputation on a clumsy BCC blast is an expensive way to save five minutes. If your deliverability is already shaky, start with email warmup and our tips to avoid the spam folder before sending anything at volume.
Sending Individually With Mail Merge
Mail merge is the manual-but-private way to send each person their own email. It takes a list of contacts and a template with placeholders, then generates and sends one separate message per row. Each recipient gets a clean email addressed only to them, with their own name and details merged in. The mechanics differ between Gmail and Outlook, so here is the exact path for each.
How to send individual emails in Gmail, step by step
Gmail gives you three routes, depending on volume and how personalized you need the message. Workspace accounts have a native multi-send feature; everyone else reaches for a mail-merge add-on like YAMM or a Google Apps Script. For a quick one-off where addresses just need to stay hidden, plain BCC is enough.
Build your list in Google Sheets
One row per person, with columns for the personal fields you want to merge.
Open a Google Sheet and create one column per variable, for example First name, Company, and Email. One contact per row. This sheet becomes the data source the merge reads from, so clean it before you send: no blank email cells, no duplicate addresses, consistent capitalization in the name column.
Pick your sending method
Native multi-send, a YAMM-style add-on, or Apps Script.
- Gmail multi-send (Workspace only). In a new email, click the Toggle multi-send mode button in the toolbar. Each address you add receives its own separate copy, not a shared thread. It supports basic mail-merge tags and an automatic unsubscribe footer, but no follow-up logic.
- A mail-merge add-on like YAMM (Yet Another Mail Merge). Install it on your Sheet, write your draft in Gmail with placeholders such as
{{First name}}, then run the merge from the Sheet. YAMM generates one individual email per row and sends from your inbox. This is the most common route for non-Workspace accounts. - Google Apps Script. If you want full control and no add-on, a short Apps Script loops over the rows in your Sheet and calls
GmailApp.sendEmail()once per contact. More setup, zero per-email cost, and you own the logic.
Write the template with placeholders
Compose once, personalize per row.
In your Gmail draft, write the message as if to one person and drop in placeholders where the personal details go, matching your column headers exactly: Hi {{First name}}, I saw {{Company}} just.... The merge swaps each tag for that row's value. Keep at least one real, specific line per contact; a merge tag alone is not personalization.
Preview, test, and send
Send yourself a test row before the real run.
Send a test to your own address first and confirm every placeholder resolved (no stray {{First name}} left in the body). Then run the merge. Each recipient gets a separate email addressed only to them. Watch the daily cap: a standard Gmail account allows up to 500 recipients per day, Workspace up to 2,000. [Google]
How to send individual emails in Outlook, step by step
Outlook has no Gmail-style multi-send. The supported path is Word Mail Merge, which pulls names and addresses from an Excel file and pushes one individual email per row through Outlook. You need Word, Excel, and Outlook all installed and signed into the same account.
Prepare the recipient list in Excel
One column per field, one row per contact.
Build an Excel sheet with columns such as First Name, Company, and Email, one row per person, and save the file. Word reads this Excel file as the mail-merge data source, so the header row names must be clear; you will map them to placeholders in a moment.
Start the mail merge in Word
Mailings tab, Start Mail Merge, E-mail Messages.
Open Word, go to the Mailings tab, click Start Mail Merge, and choose E-mail Messages. Then click Select Recipients, choose Use an Existing List, and point Word at the Excel file you just saved.
Write the message and insert merge fields
Type once, drop in the Excel columns.
Compose your message in the Word document. Where a personal detail goes, click Insert Merge Field and pick the matching Excel column, for example First Name or Company. Use Preview Results to scroll through real rows and confirm each contact's data lands where it should.
Finish and merge to email
Finish & Merge, Send E-mail Messages.
Click Finish & Merge, then Send E-mail Messages. In the dialog, set the To field to your email column, write a subject line, and choose HTML as the format. Word hands each message to Outlook, which sends one individual email per row from your account. Every recipient sees only their own address, exactly like sending one by one, just automated.
Mail merge, whether through Gmail, YAMM, Apps Script, or Word and Outlook, is a solid fit for a few dozen recipients, a one-time announcement, or an internal update. The limits show up fast at scale: there is no automatic follow-up, no reply detection, and the same daily caps apply (500 recipients on standard Gmail, 2,000 on Workspace). Spreadsheets also get messy once you are tracking opens, replies, and who still owes a follow-up.
Outgrowing mail merge?
Overloop sends each prospect their own individual, personalized email from your inbox, then handles follow-ups and reply detection automatically.
Try Overloop free →See featuresDeliverability and GDPR: The Part Generic Guides Skip
Most "how to email multiple people" articles stop at the mechanics. The part that actually decides whether your emails land, and whether they are legal, is deliverability and data protection. This is the difference between sending and being seen, and it is where we spend most of our time at Overloop.
Deliverability: authenticate before you scale
Sending one personalized email per person is the right pattern, but it does not exempt you from the rules mailbox providers enforce. Since February 2024, Gmail and Yahoo require bulk senders to authenticate with SPF, DKIM, and DMARC, keep the spam complaint rate under 0.3%, and offer one-click unsubscribe. Miss those and your mail gets filtered or blocked outright. [Google] Before any volume send, do three things:
- Authenticate the domain. Publish SPF, DKIM, and DMARC records. Neither Gmail multi-send, YAMM, nor Word Mail Merge sets these up for you; they send from your domain, so the burden is on you.
- Warm a new domain. A domain with no sending history that suddenly pushes hundreds of emails looks exactly like spam. Ramp volume gradually with email warmup first.
- Throttle and keep lists clean. Spread sends across the day rather than dumping 500 at once, and remove dead addresses so bounces and complaints stay low. Our tips to avoid the spam folder cover the rest.
GDPR: a leaked list is a reportable breach
The privacy stakes are not just etiquette. Under GDPR, an email address is personal data, and exposing a list of addresses to everyone on it, the exact thing a mass To or CC send does, can qualify as a personal data breach. [GDPR.eu] Sending individually removes that risk by design: no recipient ever sees another, because no one shares a message. For European teams, that is not a nice-to-have. It is why Overloop stores its 450M-contact database in the EU and sends each recipient a separate, private email rather than a shared blast.
Doing It at Scale for Outbound
When sending individual emails becomes a repeating job (sales prospecting, partner outreach, recruiting), a spreadsheet and a mail-merge add-on stop holding up. This is where an outbound sequencing tool earns its place. Each contact still receives their own private, personalized email, but the tool also manages the parts mail merge cannot.
For sending individual emails at scale, Overloop is the tool I would reach for first, and not only because we build it. Here is what it adds on top of a basic merge:
- One individual send per recipient. Every prospect gets a separate email from your own mailbox. No one is in CC or BCC, and each message can be personalized with merge variables and AI-written openers.
- Automatic follow-ups. You set a sequence, and Overloop sends the follow-ups on schedule until the prospect replies, then stops automatically so no one gets a "still following up" email after they answered.
- Sending limits and throttling that spread sends across the day to protect your domain reputation, instead of dumping 500 emails in one minute.
- Reply and bounce tracking so you see who engaged without rebuilding a spreadsheet by hand.
- LinkedIn plus email in one sequence, so an individual touch on email can be paired with a LinkedIn step for the same prospect.
The honest caveat: a tool removes the manual work, it does not remove the responsibility. You still need clean lists, real personalization, and respect for the recipient. The same rules that keep one email out of spam apply to a thousand: warm the domain, authenticate it, watch your bounce rate, and follow our guidance on best practices for links in your emails so a tracked link does not tank your placement. If you want a wider view of the category before deciding, our roundup of cold email software compares the main options.
The bottom line: for a one-off message to a small group, BCC is fine. For a few dozen personalized emails, mail merge does the job. For recurring outbound where each recipient should feel individually addressed and you cannot babysit a spreadsheet, a sequencing tool is the only approach that scales without wrecking deliverability.
