Skip to main content
Soventro

Automated emails

Send one of your email templates by itself: when a registration is received, confirmed or waitlisted, when payment is still due, or a number of days before the event starts or after it ends.
From the video guide Emails, with its transcript.

An automation sends one of your own email templates when a registration reaches a stage. Use it for a welcome note with practical details, a follow-up a few days after someone registers, or a message to people who join the waitlist. It's sent in addition to Soventro's own automatic emails, not instead of them.

Create an automation

  1. Make sure you have a template. See Email templates and components.
  2. Open the event and go to Communications → Your emails & campaigns.
  3. In New automation, enter a Name.
  4. Under When, choose the trigger: When a registration is received, When a registration is confirmed, When someone joins the waitlist, When payment is still due, Days before the event starts or Days after the event ends.
  5. Choose the template under Send template.
  6. For the event-day triggers, enter the number of days. For the others, optionally set Wait this many hours first, from 0 to 1,440 (60 days).
  7. Under Attendee types, tick the types it's for. None ticked means all. Open More conditions to limit it by ticket, group, check-in or hotel room. A delayed automation checks these again when it falls due.
  8. Select Create, switched off.
  9. In the Automations list, select Turn on when you're ready.

Automations start switched off, so nothing goes out until you decide.

When each trigger fires

  • When a registration is received fires once for every new registration: when an open or invitation registration is confirmed, when a card payment goes through, when someone is approved to pay by invoice, or when an application is submitted for review. Joining the waitlist doesn't count; if a waitlisted person later gets a place, it fires then. Someone who cancels or is rejected and registers again from your event page gets it again.
  • When a registration is confirmed fires each time a registration becomes confirmed: straight away, after approval, after payment or when an invoice confirms them.
  • When someone joins the waitlist fires when a registration is waitlisted.
  • When payment is still due fires when someone owes a payment: an invoice is due, a card payment failed or needs confirming, or your team registered them to pay. It's checked again when it falls due, so anyone who has paid by then doesn't get it.
  • Days before the event starts goes to everyone confirmed at that time, and to anyone confirmed later until the event starts. Switched on after its time, it goes straight away, as long as the event hasn't started.
  • Days after the event ends goes to everyone confirmed at that time. Switched on more than a week after its time, it doesn't go.

The event-day triggers follow the event's dates: if you change them, the email moves with them.

The standard Know before you go, See you tomorrow, Get the event app, Thank you for coming and Payment reminder emails come with automations like these, switched off. See Standard emails.

Rules that keep automations safe

  • Once per person. Each automation sends to each registration at most once.
  • No back-sending. It reaches only registrations that reach the stage after it's switched on, not people already there.
  • Checked again when it's due. With a delay, the status is checked again before sending. For example, a confirmed email isn't sent to someone who was cancelled in the meantime.
  • About their own registration. Automations are sent like confirmations, not like campaigns. They reach people who unsubscribed from campaigns, have no unsubscribe link, and don't need a postal address (it's added to the footer if you've set one). You can switch one on as soon as its template is active.
  • Replies reach you. Replies go to your organization's Reply-to address, or to the account owner if it's empty.
  • Quiet staff actions stay quiet. When your team registers someone with emails turned off, or imports registrations, automations don't fire.

Track and turn off

The Automations list shows each automation's trigger, delay, template, whether it's On or Off, and what happened, for example "Sent 3, failed 1, not sent 2." When an email wasn't sent, the latest reason follows, such as "Not sent: by the time it was due, the registration was cancelled.", with a link to See the message log. Select Turn off to stop it. Delayed emails that fall due while it's off aren't sent, and are recorded as not sent.

Who can manage automations

Owner, Admin and Event manager.

Note: Soventro still sends its own confirmations, invoices and payment emails. Automations are extra messages on top of them, so you don't need one to tell people they're confirmed.

Still need help?

Email the Soventro team and a person will get back to you during business hours (US Eastern).

info@soventro.com