meetergomeetergo Help

Change Your Email Sender Address and Reply-To Address

Change which address attendees see as the sender of your booking emails and where their replies land: sender name, Reply-To per meeting type, a contact email instead of your Google or login address, the no-reply option, custom SMTP and Microsoft 365.

Updated on July 27, 2026

Booking emails carry three separate addresses, and almost every "wrong address" question is really about one of them. Start here:

What you seeWhat it's calledWhere you change it
The name in the inbox list, e.g. "Acme GmbH (via meetergo)"Sender nameAdmin → Emails → Branding → Sending → Sender name (details)
The address the mail is sent fromSender ("from") addressDetermined by which system sends — see Choose the sender address below
The address that gets filled in when an attendee hits ReplyReply-To addressThree settings, in a fixed order — see Change where replies go below

Choose the sender address

The "from" address on your booking emails isn't a free-text field — not in meetergo, and not in any other booking tool. It's a technical limitation of how email works: modern providers (Gmail, Outlook, etc.) reject mail sent from addresses the sender isn't verified to use. Allowing it would mean your invites land in spam, if they arrive at all.

What you can choose is which system sends the email, and the sender address follows from that. Below are your options, from the simplest setup to the most customizable.

Quick overview — which option fits you?

You want…Use
The simplest setup, with deliverability handled for youmeetergo email confirmations
Invites that arrive from your own personal email and calendarCalendar invites
Every meetergo email to be sent from your company's own mailbox or serverConnect your own email (M365 or SMTP)

You don't have to commit forever — you can change the option per meeting type and switch later.

Option 1: meetergo email confirmations (default, easiest)

When a meeting type is set to send "Email confirmations", meetergo sends the email from its own optimized system address, shown as your company or team name followed by "(via meetergo)". Replies still reach you: the Reply-To is set to the host's address unless you override it — see Change where replies go.

Best for: users who don't need invites to come from a specific personal or company address, and just want messages to land reliably in the inbox.

This option requires no setup — it's the default.

If you want invites to actually arrive from your own email address, switch the meeting type to send "Calendar invites". meetergo will tell your connected calendar (Google, Microsoft, or Exchange) to send the event invitation, so the invite comes directly from the email address tied to that calendar.

Attendees see your name and email address as the sender, and replies go straight to your inbox.

Best for: individual users — sales reps, consultants, anyone who wants invites to feel like they sent it themselves.

To switch to Calendar Invites:

  1. Go to your Meeting Types.
  2. Find the meeting type you want to change and click "Edit".
  3. Scroll down to the "Communications" section.
  4. Under "Email Confirmations", select "Switch to Calendar Invitations".
  5. Click Save.
Image

This requires a calendar connection in your Integrations settings. If you haven't connected one yet, meetergo will guide you through it.

Option 3: Connect your own email (most control, fully branded)

If you want all meetergo emails — confirmations, reminders, follow-ups — to be sent from your own company mailbox or mail server, you can connect your own email provider. meetergo will route messages through your infrastructure, so the sender address is fully under your control and consistent across every email your attendees receive.

Today we support the two integrations below. They cover most setups — Microsoft 365 directly, and anything else via SMTP — but they're not a hard limit on what's possible. If you use a provider that needs a direct integration (Google Workspace OAuth, a specific transactional API, etc.), let us know — we add native connectors based on what customers actually run.

Microsoft 365 (OAuth) — easiest

If your organization runs on Microsoft 365, you can connect your M365 mailbox with a one-click OAuth authorization. No passwords are stored, no server settings to configure. After connecting, all meetergo emails go out from your M365 address.

This is the right choice if you're a Microsoft 365 user and want branded emails without touching technical settings.

Using Microsoft 365 Email

Custom SMTP — works with any mail server

If you don't use Microsoft 365 — or you have a dedicated transactional mail provider (Postmark, Mailgun, AWS SES, your own mail server, etc.) — you can configure meetergo to send through any SMTP server. You'll need the host, port, and credentials from your mail provider.

This option gives you the most control, but it does require some technical setup.

Using a Custom SMTP Server

Change where replies go (Reply-To)

The Reply-To address is what an attendee's mail program fills in when they hit Reply. Unlike the sender address, this one you can set freely.

meetergo picks it in this order, and the first match wins:

OrderSettingWhere
1Custom Reply-To address for a single meeting typeMeeting type → MoreAdvancedEmail Notifications
2Use no-reply address for the whole companyAdmin → Emails → BrandingSending
3The host's contact email (falls back to the login email)ProfileAccount Management

Route replies for one meeting type to a shared inbox

Use this when replies for a specific booking page should reach a team address like sales@ or support@, no matter which host was booked.

  1. Open the meeting type and click Edit.
  2. In the left sidebar, open the More group and choose Advanced.
  3. Scroll to Email Notifications.
  4. Enter the address in Custom Reply-To address.
  5. Click Save.

Leave the field empty to fall back to the host address. This override applies to attendee emails and to the notifications the host receives for that meeting type.

Reply to my business address, not my Google or login address

By default, replies go to the host's login email — which for anyone who signed up with Google or Microsoft is the address of that account. To point replies somewhere else without changing how you sign in, set a contact email on your profile. Full steps: Setting a Contact Email.

Stop replies to booking emails entirely

Admin → Emails → BrandingSending → turn on Use no-reply address. Replies to automated booking emails then go to no-reply@meetergo.com. This is company-wide, and it does not affect calendar invitations — those still come from the host's calendar account.

FAQ

Why can't I just type in the email address I want to use?

Because letting anyone send mail from any address is exactly what spammers do. Modern email providers (Gmail, Outlook, etc.) reject or spam-folder messages that aren't sent from a verified source. The options above all use a verified source — either ours, your calendar provider's, or yours — so your invites actually reach attendees.

If I use Calendar Invites, can attendees reply to the invitation?

Yes. Replies go directly into the inbox of the calendar account you connected (your Gmail, Outlook, etc.).

What's the best option for me?
  • Most individual users → Calendar Invites. Personal, professional, replies land in your inbox.
  • Don't have Google, Microsoft, or Exchange → meetergo email confirmations. Simple and reliable.
  • Microsoft 365 user who wants branded emails across the company → Microsoft 365 Email integration.
  • You have your own mail server or a transactional provider → Custom SMTP.
Can I use a different sender or reply address per meeting type?

The Reply-To address, yes — set Custom Reply-To address on each meeting type (see above). The sender name and sender address are not per meeting type: the sender name is set per company, or per team if the meeting type belongs to a team, and the sender address follows the sending system you chose.

The sender name is different from what I set under Emails → Branding

A team can override the company sender name. If the meeting type belongs to a team, check Admin → Teams → open the team → Email tab → Email Sender Name. Leave that field empty for the team to use the company setting again. The Email Sender Address next to it only takes effect once the company sends through its own SMTP server.

Why does the sender read "… (via meetergo)"?

meetergo sends from its own verified address on the default setup, and mail clients label that as sent via meetergo. Connect Microsoft 365 or custom SMTP and the suffix disappears, because the message then really is sent from your own domain.

I changed the setting but the old address is still showing

Settings apply to emails sent from that point on. Emails already sent — including confirmations for existing bookings — keep the addresses they had when they went out.

Was this article helpful?

Let us know if this article answered your questions.