A mail merge is the wrong tool when the email differs a lot from person to person, or when the people on the list need more than a private copy. That covers a handful of names, a group that has to agree on something, hard news, a private file for each person, and people who never asked to hear from you. For most other sends, a merge is a good fit. This guide helps you tell which one you have, and what to use instead.
A quick test before you build the sheet
A merge suits a send when all three of these hold:
- The message is the same for everyone, apart from a few details like a name or a date.
- Each person reads it on their own and answers only you.
- You’d be glad of a reply from every one of them, and you’re around to answer.
If one of those fails, something else probably fits better. Here’s the short version.
| The send | What fits better |
|---|---|
| Fewer than ten people | Separate emails from a saved template |
| A group that needs to agree on something | One email to everyone, or a booking link |
| Hard news, an apology, or news that differs per person | Individual emails, written one at a time |
| A private file for each person | A file shared with that one person, or a checked individual email |
| A notice where nothing changes but the name | One email with everyone in Bcc |
| People who didn’t ask to hear from you | A mailing platform, used under the email marketing rules |
| A notice a contract says must be given a certain way | The method the contract names |
The sections below take each one in turn.
When there are only a few people
A merge has a setup cost. You build the sheet, write the template, send a test and check a few rows. That’s worth it for forty people. For six, it often takes longer than writing six emails.
A saved template gives you most of the speed without the setup. You write the email once, then open it fresh for each person and change what needs changing. Gmail lets you save a draft as a template once you turn templates on in its settings. Outlook has email templates and My Templates for the same job.
Writing each one also leaves room for a line that fits one person only. “Good to see you at the Hendersons’ on Saturday” belongs in one email only. With a small list, you can give everyone a line like that.
When the people need to talk to each other
A merge gives each person a private copy. Gmail’s help says recipients “can’t check who else you sent the message to.” Their replies come back to you one by one. In Gmail, each one lands in its own thread.
That’s right for a fee notice. It’s wrong when the people on the list need to hear each other. Six board members picking a date each see only their own copy, so nobody knows who’s already said Tuesday. You end up passing messages between them by hand.
For a group that has to agree on something, send one email with everyone on it. Then the replies sit in one thread everyone can read. If the thing to agree on is a meeting time, a booking link or a single proposed time usually settles it faster. Booking a meeting without the email chain covers that.
When the news is hard, or different for each person
Some emails need to be written to one person because of what they say. A price rise that hits some clients harder than others. A delay that affects each project differently. An apology. Turning someone down.
A merge sends these in a shape that reads as a mailing. Gmail’s built-in merge adds an unsubscribe link to the bottom of every copy. That link under an apology tells the reader it went to a list. Even without it, a sentence built to fit every row reads flatter than one written to the person.
The sign to watch for is the part that changes. Once the lines you write per person outgrow the lines everyone shares, the merge is only adding steps. Write them one at a time instead. The craft of the hard ones is covered in how to say no in an email and how to apologize by email.
When each email carries a private file
Statements, tax forms, contracts and reports are different for each person. A merge is a poor way to send them.
The built-in tools attach one file for the whole send. Google’s help says a Gmail merge attachment “will be included in each recipient’s copy of the message.” So everyone would get the same file. Microsoft’s help for Word’s merge to email says “You cannot add attachments, but you can include links.” Some add-ons do attach a file per row. Then one row out of order in the sheet sends Maria’s statement to Tom, and you hear about it when Tom writes back.
Two routes are safer:
- Share each file with its one person. Upload it to your storage or client portal and share it only with that person’s address. A forwarded link stays locked to the person you chose.
- Send each one on its own. Attach the file, check the name on the file against the name in the To line, and send. It’s slower, and that’s the point.
If a file does go to the wrong person, the hour after a wrong recipient email walks through what to do.
When nothing changes but the name
“The office is closed Friday” reads the same for everyone. A merge only adds work here. One email, with your own address in To and everyone else in Bcc, does the job.
Bcc has one risk worth knowing. If the addresses land in To or Cc by mistake, everyone sees everyone’s address. A merge avoids that slip, because each copy carries one address. So if the list is clients who shouldn’t see each other, the merge is the safer choice even for a plain notice. Bcc addresses count toward your daily limit the same way merged ones do. Mail merge sending limits has the numbers.
When the list didn’t ask to hear from you
A merge from your mailbox is meant for people who know you: clients, members, suppliers, the parents in your group. A pitch to a bought list, or a regular newsletter, is a different kind of email under US law. The FTC’s guide to the CAN-SPAM Act says:
It covers all commercial messages … The law makes no exception for business-to-business email.
The same guide puts the penalty at up to $53,088 for each email that breaks the rules. That kind of sending belongs on a mailing platform built for it, and it’s outside what these guides cover. Your mailbox’s limits will stop a large list early anyway.
When a contract says how notice is given
Some emails are formal notices. Ending a lease, changing a contract’s terms, or giving notice under an agreement can come with rules about how the notice is delivered. A contract might ask for certified mail, a named address, or a signature.
A merged email might fall short of those rules, even if everyone reads it. Check the notice clause before you send. If it names a method, use that method, and send an email as well if you like.
When you’ll be away as the replies arrive
A merge that reads well gets answered. Send one to eighty clients on a Friday before your vacation, and those answers sit for two weeks. Some of them will be questions with a deadline.
So pick the day as carefully as the words. Send when you’ll be at your desk for the day or two after. If you need the email out before you go, keep the list to the people who must hear now. Send the rest when you’re back. Once the replies land, handling the replies to a mail merge takes it from there. For the people who don’t answer, following up without nagging picks up the thread.
When a merge is the right call
Plenty of sends pass the test above. A fee change for every client, a new office address, a reminder about a deadline everyone shares. For those, a merge saves real time and still reads as written to one person.
- Mail merge in Gmail covers the built-in merge, step by step.
- Mail merge in Outlook and Word covers the Word, Excel and Outlook route.
- Keeping a mail merge personal covers writing a template that holds up for every row.
Where the answers go
Point doesn’t send mail merges. Your mailbox does the sending, whichever route you picked above. Point’s part begins when the answers land in your inbox. The client with a real question rises to the top, and the out-of-office notes drop out of sight. A reply to that client is already drafted in your voice. Out of the box, it sits as a draft until you’ve looked it over and sent it. If the email was really about finding a time, Point runs that back-and-forth, and you approve the time it lands on. Everything else Point does with a busy inbox is on the benefits page.
Common questions
When should you not use a mail merge?
Skip it when the list is very short or the email differs a lot from person to person. Skip it when the people need to see each other’s replies, or when each one gets a private file. Hard news, apologies and formal notices are also better sent one at a time.
Is a mail merge or Bcc better for a group email?
Bcc is simpler when nothing changes per person, like a closure notice. A merge is safer when the list must stay private, because each copy carries only one address. A merge also lets you add a name or a detail for each person.
How many people is too few for a mail merge?
There’s no fixed number. Under about ten, writing separate emails from a saved template is usually quicker than building a sheet and testing a merge. It also leaves room for a line written to each person.
Can I send a different attachment to each person in a mail merge?
Gmail’s built-in merge puts the same attachment in every copy. Word’s merge to email can’t attach files at all. Some add-ons can, but a sorting slip sends the wrong file. Sharing each file with its one person is safer.
Can I use a mail merge to email people who haven’t heard from me?
A sales email to people who didn’t ask for it is commercial email under the CAN-SPAM Act. The FTC says the law covers business-to-business email too. That kind of sending belongs on a mailing platform, used within those rules.
Why does my mail merge reply come back as a separate thread?
Each person got their own copy, so each reply starts its own thread. Gmail’s help says you’ll “get the recipient’s replies in separate threads.” If the group needs one shared thread, send a single email to everyone instead.