Automations: the emails you always mean to send

A month before the event, invite the client to book their final planning call. Three days after a quote goes out, follow it up if nobody has replied. The day after, send a thank-you and a feedback link. These are the jobs everyone means to do and half of them get lost in a busy week. Automations do them for you.

A trigger and its actions

Every automation reads as a sentence. Pick when it runs, then stack what happens when it does.

Triggers cover the event date (X days before, X days after), a lead crossing a step in your pipeline (enquiry received, quote sent, quote opened, quote accepted, agreement signed, booking confirmed), a crew member acting on their link (requests completed, self-registration, requests still outstanding), and appointments (a set number of minutes before a booking starts).

Actions are what happens: email the client, the organizer, the crew member, or yourself. Turn one of your checklists into tasks on the event. Or drop in a Wait and everything below it is delayed, which turns a single trigger into a proper drip: email now, wait three days, email again.

Your wording on the emails 1pm already sends

The Automations page has a second half. Every transactional email 1pm sends on your behalf, the crew invite, the quote and invoice and confirmation emails, the booking confirmed note, the expiring-document prompt, is now a card you can open and rewrite in your own voice. Reset puts the original back if you change your mind.

Emails take merge fields for the client, event, and crew details, light formatting, and buttons. Preview renders one against a sample event, and Send test drops the finished version in your own inbox.

A day to change your mind

Anything an automation sends to a client parks in a Sending soon queue for 24 hours first, listed with its recipient, subject, and send time. What you see there is exactly what will go. Cancel any row and it will not send, and it will not try again for that event. Internal emails, crew emails, and task creation happen straight away, because those are yours to see anyway.

Underneath, Recent activity shows what has gone out, marked sent, done, or failed with the reason. Nothing retries quietly.