Use mail merge without sending the wrong personal details

A correct greeting can still conceal a wrong recipient

A mail merge can produce a perfectly spelled name beside somebody else’s booking reference. Checking punctuation will not catch that mistake. Before sending, establish that the email address, name and personal details all belong to the same person.

This guide uses Word for Microsoft 365 on Windows, an Excel workbook and classic Outlook. Have a working Outlook account and mailboxes you control for testing. Microsoft’s compatibility guidance says Word needs classic Outlook to send merged emails. New Outlook’s separate merge option does not insert personalized contact fields. If you only have new Outlook, stop here rather than assuming these instructions apply.

Use a modest, non-sensitive mailing such as workshop booking confirmations for your first attempt. Keep payment details, medical information and passwords out of the template. A mail merge is only as trustworthy as its source list; it does not independently verify who owns an address.

Build a send-only workbook before opening Word

Keep the master list intact and prepare a separate workbook containing only approved recipients and the fields this message needs. Use clear headers such as Email, FirstName, BookingRef and Session. Put one person’s complete record on each row. Avoid merged cells, repeated header rows and notes mixed into the data.

Microsoft’s Excel preparation guide calls for the merge data on the first sheet, a locally stored workbook and completed edits before connecting Word. Format identifiers as text before entering them when leading zeroes matter. Changing the format after Excel has discarded a zero will not reconstruct the original identifier.

Here is a hypothetical check, using reserved example addresses rather than real recipients:

If somebody sorts only the Email cells, Alex’s booking can become paired with Jo’s address. Sort the complete data range together, then compare complete rows against the trusted booking record. A plausible greeting is insufficient evidence.

Count intended recipients and investigate repeated addresses. A duplicate might represent a shared household or two legitimate bookings, so do not delete it automatically. Resolve missing names, ambiguous dates and uncertain addresses before proceeding. Write dates and times unambiguously, including a time zone when recipients need one. Save and close the workbook.

Connect the list and make every personal detail a field

1. In Word, open a new document and choose Mailings > Start Mail Merge > E-mail Messages. Under Select Recipients, choose Use an Existing List, select the workbook and its intended worksheet. Confirm that Word recognizes your header row.
2. Open Mailings > Edit Recipient List. Check that the expected people are selected and exclude anyone who should not receive the message. Treat this list as the sending boundary, even if Excel had rows hidden from view.
3. Write the common message. Place the cursor at each personalized position and use Mailings > Insert Merge Field to select the corresponding column. Do not type imitation field brackets or paste one person’s details into the shared wording.

Microsoft’s field instructions explain that these fields come from source-column headings. If field commands are dimmed, first check that you selected a recipient source. Selecting an explicit FirstName field also avoids assuming that an automatic address block has matched your custom columns correctly.

For example, construct “Hello [FirstName], your booking [BookingRef] is for [Session],” inserting actual fields at the bracketed positions. The brackets here explain placement; they are not text to paste. Search the rest of the document for a previous customer’s name, reference or private link left behind from an earlier message.

Read the merged records, then test delivery separately

Select Mailings > Preview Results and use the next/previous record arrows. Check names, references and sessions against complete source rows. Use Edit Recipient List to check the corresponding email address as well; a body preview does not prove the destination is correct. Inspect every record for a small mailing. For a larger batch, independently reconcile all address-to-detail pairings and also inspect unusual records: blanks, long names, repeated addresses and identifiers beginning with zero.

Next, save a separate test document and create a tiny test workbook. Give it the same headers but only invented booking details and real mailbox addresses you control. Include two visibly different records. Reconnect the test document through Select Recipients; confirm that no customer addresses remain selected.

Use Finish & Merge > Send E-mail Messages. Set To to Email, enter an unmistakable test subject, choose HTML, and send only the test records. Microsoft’s email-merge instructions document these controls and the Current record option. Choosing OK runs the merge; treat that click as authorization to send.

In the received messages, check the sender account, destination, personalized text and links. Two records sent to one test inbox still need two different expected bodies. If either is wrong, repair the template or source and repeat the test. These are recommended checks, not tests performed for this article.

Return to the real list with a fresh final check

Close the test document and reopen the production document. Recheck its workbook connection, selected recipients, previewed fields and intended count. A successful test proves the test setup worked; it does not approve a different source file. If you changed production data, reconnect and repeat the relevant checks before sending.

For a hypothetical batch of 24 confirmations, the approved list should contain 24 intended recipient records. If it contains 25, explain the extra record before release. Never treat a rough estimate as permission to send.

Open Send E-mail Messages again, verify Email in To, replace the test subject with the final subject and review Send records. All is the default: choose the intended scope deliberately. This Windows merge sends individual messages without CC/BCC or file attachments; check any document links and their access permissions separately.

If something is wrong, stop before retrying

Before sending: cancel the send dialog. For shifted details, repair the complete source records rather than swapping names inside Word. For lost zeroes or malformed dates, correct the source values and check the actual merged output again. Do not solve a missing value by borrowing the neighboring row’s detail.

After starting: stop additional batches and inspect Outlook’s Outbox and Sent Items. Remove identifiable unsent campaign messages from the Outbox if present. This cannot retrieve messages already delivered, and an empty Outbox does not prove every recipient received the message. Do not rerun the whole batch because one person reports a missing email.

If personal details reached the wrong person, record the affected addresses and fields, notify the responsible person in your organization, and follow its incident process. Send any correction individually after verifying the destination. Asking a recipient to delete a message is not a guarantee that copies disappear.

Finally, keep only the approved records needed under your retention policy. The saved Word document retains its source connection. Before reusing it, inspect that connection and the recipient list again; yesterday’s successful mailing does not authorize today’s audience.