Back to Top

Copy, Paste, Repeat? Let Your Forms Do the Emailing

21 October, 2026

Picture your morning. Registration for your workshop closed last night, and 120 people signed up through your online form. Each of them needs an email with their session, the time, and the room. So you open a new message and start typing.

New messageDraft 3 of 120

Hi Sara, your workshop seat is confirmed for Tuesday at 10:00.

Hi Omar, your workshop seat is confirmed for Wednesday at 14:00.

Hi Lina, your workshop seat is confirmed for Tues 

Now do that 117 more times. Spell every name correctly. Copy the right KAUST email address into the To line. Paste the right session, not the one from the row above. And hope nobody gets Tuesday when they signed up for Wednesday.

Whether you collect responses with Microsoft Forms, Google Forms, or Formstack, there is a better way. Two, actually.

Let your form send the first emails

All three tools can email you when someone responds and show a thank-you message the moment they submit. Each one handles the person who responded a little differently:

 

Microsoft Forms

Respondents can get a receipt of their answers. For a message in your own words, pair it with Power Automate.

 

Google Forms

Respondents can get an email copy of their response, and you can write the confirmation message they see on screen.

 

Formstack

Write your own confirmation and notification emails with their answers filled in, or send people to another page when they finish.

Set these up before you share your form, and a lot of the follow-up takes care of itself.

For everything after that, meet mail merge

Automatic emails go out the moment someone responds. But what about the reminder the day before? The room change? The certificate link once the session is over? That is where mail merge comes in.

You write one message with placeholders for the details that change, such as the first name, session, and room. Mail merge pulls those details from your responses and sends each person their own email, from your KAUST mailbox. Nobody sees anyone else's address, and nobody gets a message that starts with "Dear all."

It works with responses from all three tools. If your KAUST email is on Outlook, use Word on Windows or macOS, or Power Automate in your browser. If it is on Gmail, Gmail has mail merge built in with Google Sheets.

Ready to set it up?

Our guide covers the automatic emails, thank-you messages, and redirects in each form tool, then walks you through mail merge for Outlook and Gmail.

Send Emails from Your Form Responses

Where it helps at KAUST

If your form collects an email address, there is probably a mail merge waiting to happen:

Training and workshops: send each registrant their session, room, or Teams link, then a reminder.

Events and enrichment programs: confirm seats for community events or Winter Enrichment Program sessions.

Program applications: let each applicant know what happens next, with their reference number.

Requests: tell each requester when and where to collect what they asked for.

Surveys: thank participants by name and share what changes next.

Keep it personal, not bulk

Mail merge sends from your own mailbox, so it is built for people, not campaigns. An Outlook mailbox can send 30 messages a minute and 10,000 recipients a day, and Gmail mail merge allows 1,500 messages a day. That makes it a great fit for tens to a few hundred people.

Two habits worth keeping

Treat your responses as personal data: keep only the columns you need, store the file in OneDrive or Google Drive, and delete it when you are done. And send the first message to yourself. Planning to email a much larger group? Contact KAUST IT first.

The next time 120 people need 120 slightly different emails, you will only need to write one.

 

Set up your form emails

Automatic emails, thank-you messages, and mail merge for Microsoft Forms, Google Forms, and Formstack.

Read the step-by-step guide

 

Ask fewer questions

Pre-filled links open your form with answers already chosen, so your responses arrive cleaner.

Stop Asking the Same Question Twice