Passa al contenuto principale

Sending Emails to Your Clients

After reading this page, your studio will be able to actually send email to clients — booking confirmations, invitations, password resets, and marketing campaigns — from your own email address, and you'll be able to confirm it works with a test message before any client is involved.

Navigation label — Email: EN: Email · IT: Email · FR: E-mail · DE: E-Mail · ES: Email

Go to Settings → Email. Only studio managers can see this tab.


Before you start​

Nothing sends until a sending account is configured here. This is the single most common reason a studio sees no email going out.

Building an email template and assigning it to an event is not enough on its own. A template describes what the message looks like; an event assignment describes when it should go. Neither of them gives Agon an email account to send through. Until you complete this page, every send fails silently in the background and your clients receive nothing.

You will need one of:

  • A Google account (Gmail or Google Workspace) with 2-Step Verification already switched on, or
  • An account with another email provider, plus its server details.

The two ways to connect​

Settings → Email offers two paths, and it matters which one you pick today.

PathWhat it looks likeUse it when
Connect with Google / Connect with MicrosoftOne button, approve in your browser, doneMicrosoft accounts today; Google accounts once verification completes
Send from your own email account (SMTP)A short form you fill in onceGmail and Google Workspace accounts today, and any other provider

A note on "Connect with Google" right now​

If you click Connect with Google, your browser may show:

Access blocked: Agon has not completed Google's verification process

Error 403: access_denied

This is expected, and it is not a problem with your account or your installation. Agon's Google application is still going through Google's own verification review, and until that finishes Google only allows accounts that have been added as testers by hand. There is no setting in Agon that changes this.

If you see that message, use the SMTP path below instead. It sends from the same Gmail account and your clients cannot tell the difference — the email arrives from your address either way.

Connect with Microsoft is unaffected and works normally.


Setting up Gmail or Google Workspace (SMTP)​

This is the recommended path today. It takes about four minutes, once.

Step 1 — Create a Google app password​

Gmail refuses your normal account password over SMTP, so you need an app password: a 16-character code that works for one application only and can be revoked on its own without changing your real password.

  1. In Settings → Email, expand Send from your own email account (SMTP).
  2. Make sure the Email provider is set to Gmail or Google Workspace.
  3. Click Create an app password under the App password field. This opens myaccount.google.com/apppasswords in your browser.
  4. Sign in if asked, name the password Agon, and create it.
  5. Copy the 16 characters Google shows you. You cannot view them again afterwards — if you lose them, delete that app password and create another.
note

If that page tells you app passwords are unavailable, the Google account does not have 2-Step Verification turned on. Switch it on under Google Account → Security → 2-Step Verification first, then come back. Google requires it before it will issue an app password; Agon cannot work around this.

Step 2 — Fill in the three fields​

Back in Agon, under Send from your own email account (SMTP):

FieldWhat to enter
From NameThe name clients see as the sender — your studio's name
Gmail addressThe full address of that Google account
App passwordThe 16 characters from Step 1

That is everything. The server address, the port, the encryption setting and the sender address are all filled in for you from the provider you picked, which is why you don't see them.

FieldENITFRDEES
ProviderEmail providerProvider emailFournisseur e-mailE-Mail-AnbieterProveedor de correo
Sender nameFrom NameNome mittenteNom de l'expéditeurAbsendernameNombre de origen
AddressGmail addressIndirizzo GmailAdresse GmailGmail-AdresseDirección de Gmail
PasswordApp passwordPassword per le appMot de passe d'applicationApp-PasswortContraseña de aplicación

Step 3 — Save, then send yourself a test​

  1. Click Save Settings.
  2. Click Send Test Email.

Save first. The test button stays greyed out until you have saved, and hovering it explains why ("Save settings before sending a test message"). The test is sent to the email address of the manager account you are signed in as — not to the address you just configured, and not to any client — so you can check the result safely.

If the test arrives, you're done — bookings, invitations, password resets and campaigns will now go out through that account.


Setting up another provider (SMTP)​

If your studio already uses a transactional email provider such as SendGrid, Amazon SES or Mailgun, or runs its own mail server, set Email provider to Another provider and the full form appears:

FieldWhat to enter
From NameThe name clients see as the sender
From AddressThe address the email is sent from
SMTP HostYour provider's server address
SMTP PortUsually 587
SMTP UsernameUsually the full address, or an API-key username
SMTP PasswordThe password or API key
Use TLS/STARTTLSLeave this on unless your provider says otherwise

All seven values come from your provider's own documentation — Agon cannot guess them. Then save and send a test, exactly as in Step 3 above.

Why there is no Outlook option in the list​

Microsoft has been progressively switching off password-based sign-in for SMTP on personal Outlook.com addresses, and on Microsoft 365 business tenants SMTP sending is switched off by default until an administrator enables it. A preset would therefore look supported and then fail at the moment you tried to send.

If you use Microsoft, use the Connect with Microsoft button at the top of the tab instead. That path does not depend on SMTP at all.


If you configure both​

A Google or Microsoft account connected with the Connect buttons always takes priority over the SMTP form. Agon tries Google first, then Microsoft, then SMTP, and uses the first one that is connected. Filling in the SMTP form does not disable a connected account — to fall back to SMTP, disconnect the connected account first.


Daily sending limits​

Google limits how much a single account may send per day, and that limit belongs to the Google account rather than to Agon:

  • A personal @gmail.com account: 500 recipients per day
  • A Google Workspace account on your own domain: 2,000 messages per day

For an account connected with Connect with Google, Agon shows a counter in Settings → Email so you can see how close you are. Over SMTP there is no counter, so the limit announces itself as sends simply beginning to fail. A studio sending a campaign to a large client list should expect this: either spread the campaign over several days, move to Google Workspace, or use a transactional provider via the Another provider path, which is built for volume.


Frequently asked questions​

Will clients see that I'm using Gmail? They see whatever you put in From Name and the address itself, the same as if you had written the email by hand. Sending through a real Gmail or Outlook account is in fact why these messages reach the inbox reliably: the client's mail provider already trusts the sending domain.

Is the app password stored safely? It is stored encrypted in your studio's own database on your own machine, like every other credential in Agon. It never leaves your installation, and it is never shown back to you — the password field appears blank when you return to the page, which is normal. Saving other settings does not erase it.

Can I revoke access later without changing my Google password? Yes. Delete the Agon entry at myaccount.google.com/apppasswords. Sending stops immediately; nothing else about your Google account is affected.

Do I need this if I only use push notifications? No. Push notifications to the mobile app are a separate channel and work without any email setup. You need this page for anything that arrives as email — including the invitation that lets a new client log in for the first time, and password resets.

Do I need this for SMS? No, SMS messaging is configured separately under Settings → SMS.


What if something goes wrong?​

"Error 403: access_denied" when I click Connect with Google Expected, and not something you can fix from your side — Agon's Google application is still in Google's verification review, so Google only lets hand-added testers through. Use the Gmail SMTP path above; it sends from the same account.

"Failed to send test email" and I used my Gmail address Almost always the password. Gmail rejects your normal account password over SMTP: the App password field needs the 16-character app password from myaccount.google.com/apppasswords, not the password you type to sign in to Google. Create one, paste it in, save, and test again.

The app-password page says app passwords aren't available for my account That Google account does not have 2-Step Verification enabled. Turn it on under Google Account → Security, then create the app password. There is no alternative — Google will not issue one otherwise.

I clicked Send Test Email but nothing happened and the button looks disabled You haven't saved yet. Click Save Settings first; the test button is deliberately inactive until the settings it would test are stored.

The test email arrives but my clients get nothing The sending account is fine, so the problem is upstream of it: the message has nothing triggering it. Check that the email template is assigned to an event, and remember that only some events currently trigger a send. For scheduled sequences, see Marketing Automations.

Emails land in spam Check that From Name and the sending address look like your studio rather than something generic, and send from an address at your own domain where you can (Google Workspace rather than a personal @gmail.com). If you run your own mail server through the Another provider path, this is usually missing SPF or DKIM records on your domain — your provider's documentation will cover both.

Email stopped working after weeks of being fine, and I had used Connect with Google A Google connection made while Agon's application is still unverified is only valid for a limited period, after which Google expires it. Reconnect, or move to the Gmail SMTP path above, which does not expire.