The message a contact sees right after submitting your form is one of the most overlooked parts of form design — and one of the highest-impact. A strong confirmation sets the tone for everything that follows. A generic "Thanks for submitting" misses a chance to welcome, reassure, or convert.

This guide is a best-practice companion to How to build a form in Connect. It covers what to write, when to use on-screen vs email vs SMS, and gives ready-to-adapt examples for the most common form scenarios.

Topics

• What makes a good confirmation message
• On-screen vs email vs SMS — when to use each
• Examples by use case
• Using mail merge for personalisation
• Common mistakes to avoid
• Test before you publish

What makes a good confirmation message

Four things separate a confirmation message that lands from one that gets skimmed and forgotten:

• Acknowledges the action. Confirms the form was received so the contact isn't left wondering if anything actually happened.
• Sets clear expectations. Tells them what comes next, when they'll hear from you, or what to look out for.
• Reflects your brand voice. Warm, professional, cheeky — whatever fits your venue. Generic doesn't build relationships.
• Offers a clear next step. Where relevant — visit the menu, follow on socials, redeem a welcome offer, save the date.

If your message ticks all four, you're already ahead of most.

On-screen vs email vs SMS — when to use each

You can configure all three for the same form. Each has a different role:

On-screen confirmation — appears immediately after submission. Use it to acknowledge the action and set short-term expectations ("You're all signed up — keep an eye on your inbox").

Email confirmation — lands in their inbox minutes later. Use it for richer content: a proper welcome, next-step instructions, a discount code, links to your menu or socials.

SMS confirmation — direct and time-sensitive. Best for high-urgency contexts: event entries, competition confirmations, booking reminders. Use sparingly so the channel stays valuable.

💡 Tip — Don't send all three with the same content. Each channel deserves a message tailored to how the contact will read it.

Examples by use case

Use these as starting points. Adapt to your brand voice, then test on yourself before publishing.

Website signup

• On-screen: Welcome to the table. We've added you to our list — keep an eye on your inbox.
• Email: Hi {{first_name}}, welcome to [Venue Name]. You're on the list for exclusive offers, event invites, and the occasional foodie surprise. Reply to this email any time — we read everything.

Preference capture (favourite team, dietary requirement, etc.)

• On-screen: Got it, thanks {{first_name}}. We'll use this to make your next visit even better.
• Email: Thanks for sharing, {{first_name}}. You'll now get offers tailored to what you actually like — starting with our next event.

Competition entry

• On-screen: You're in. Winner announced [date].
• Email: Thanks for entering, {{first_name}}. The winner will be drawn on [date] and notified by email. Good luck.
• SMS: {{first_name}}, you're entered in the [competition name] draw. Winner announced [date]. Good luck.

Event RSVP

• On-screen: You're on the guest list for [event name].
• Email: Hi {{first_name}}, you're confirmed for [event name] on [date]. Doors open at [time]. Show this email at the door — or just give your name. See you there.

Survey or feedback

• On-screen: Thanks for the honest feedback, {{first_name}}. It genuinely helps us get better.
• Email: Appreciate the feedback, {{first_name}}. We read every response and use them to shape what we do next.

Using mail merge for personalisation

Mail merge pulls values from the form submission (or existing contact data) into your message. The most common merge is {{first_name}}, but you can merge any standard or custom contact field — favourite team, last visit date, loyalty tier, anything you store.

To insert mail merge in any confirmation message:

1. Click Mailmerge in the message editor
2. Select the field you want to insert (e.g. First Name)
3. Optionally set a fallback value (e.g. "friend") for cases where the field is blank
4. Click Insert Tag

⚠️ Warning — Always set a fallback. If the field is blank and you haven't set one, the contact sees something like "Hi ," with a glaring gap. Useful fallbacks: "friend", "there", "foodie".

For the full setup steps, see How to build a form in Connect.

Common mistakes to avoid

• ❌ Generic "Thanks for submitting" — adds zero value beyond the form's default.
• ❌ All-caps or excessive exclamation marks — feels like spam, especially in SMS.
• ❌ No mention of what happens next — leaves contacts unsure anything got through.
• ❌ Mail merge without a fallback — broken-looking messages erode trust on the first interaction.
• ❌ Long blocks of marketing copy — confirmations are a moment, not a newsletter.
• ❌ Same content across all three channels — feels lazy and trains contacts to ignore future messages.

Test before you publish

Before sharing your form publicly, run through this quick check:

1. Submit the form yourself using a real email address and mobile to see exactly what your contact sees
2. Test mail merge twice — once with all fields filled in, once with the merge field deliberately blank — to confirm the fallback works
3. Open the email confirmation on your phone (most contacts will read it there)
4. Read the SMS out loud — if it sounds weird, rewrite it

💡 Tip — Get a teammate to test too. Fresh eyes catch tone issues and typos that you'll miss after writing.

Related articles

• How to build a form in Connect
• Manage your forms
• How to capture guest preferences via an email campaign
• How to capture new contacts with a website signup form
• Getting started with forms in Connect

Your confirmation messages should now do more than confirm — they should turn the moment of submission into the start of an ongoing relationship.

Any questions? Reach out to us via email at support@meandu.com