Sending email

Email is how your app speaks when nobody is looking at it: confirmations, invitations, password resets and reminders.

Adding a sender

Connect an email sending service, then verify the domain you want to send from, for example notifications@yourdomain.com. Verification is what stops your messages being treated as spam.

Until you verify a domain, you can send from a shared address for testing. That is fine while building and not fine for real users.

The emails worth writing first

• Account confirmation and password reset
• A confirmation for the main action, with the details in the message
• A notification to staff when something needs attention
• A reminder before a booking or a renewal

Start with these four. Most other email is noise.

Writing a good transactional email

• Put the facts in the first line: what happened, when, and with whom.
• Include one clear button, not three.
• Say what happens next if the person does nothing.
• Keep the same branding as the app, but simpler.

Triggering email from the app

Ask for it as part of a flow: "when a booking is confirmed, email the customer with the date, time and address, and copy the studio." The builder adds the template and sends it from the server, so it still goes out if the browser closes.

Testing deliverability

Send to a real mailbox you control, not just a preview. Check the spam folder, the sender name and how it looks on a phone. If a message does not arrive, the usual cause is an unverified domain.