Skip to main content

Email workflows and runtime checks

Email work is not finished when a sender is configured. Review the runtime workflows that send invitation, verification, recovery, and account emails so users receive the right message at the right time.

Create or review invitation templates​

Switera email template creation workspace with invitation examples
Start from an example when you need a safe baseline, then adjust the subject and copy for your product voice.

When creating a template:

  1. Open Services > Email.
  2. Open Templates.
  3. Select Create template or Start from example.
  4. Choose the email purpose and locale.
  5. Write a clear subject.
  6. Keep the body short and action-oriented.
  7. Preview with sample data.
  8. Save and send a test before using it for customers.

Review built-in messages​

Switera built-in managed email detail page
Built-in messages cover common account flows. Review copy, timing, and active state before relying on them in production.

Review built-in emails for:

  • verification
  • password recovery
  • passwordless or code sign-in
  • invitation lifecycle
  • security notifications
  • account changes
  • welcome or onboarding flows

Runtime checks before launch​

Run these checks with test users:

  • invitation reaches inbox
  • recovery link arrives and expires correctly
  • verification link works once
  • reply-to goes to a monitored mailbox
  • message renders on desktop and mobile email clients
  • app name and organization name are recognizable
  • links land on the intended hosted page or product callback
  • failed sends are visible in Switera or your operational process

Writing email copy​

Good Switera account emails are direct:

  • explain why the user received the email
  • name the app or organization when relevant
  • put the primary action near the top
  • avoid long marketing copy in transactional messages
  • include a support path when the user might be confused
  • avoid raw IDs, internal environment names, or implementation details

When to send tests​

Send a test when:

  • a sender domain changes
  • the app name or logo changes
  • the invitation template changes
  • legal or support links change
  • an Auth policy changes
  • a new locale is added

Troubleshooting email flows​

If users do not receive emails:

  1. Confirm the email address is correct.
  2. Check whether the user was invited or imported into the right app.
  3. Confirm the sender is configured.
  4. Review suppression, bounce, or block handling.
  5. Send a test to an internal mailbox.
  6. Check whether the hosted page link is expired.
  7. Review audit logs for recent email setting changes.

Related pages: