The right email.
The right day.
Reminders, follow-ups, and invoice chasers that fire off real events — and stop the moment someone replies.
Nobody has to remember.
A booking, a finished job, a sent invoice — the sequence starts itself, sends on the days you picked, and bows out the moment the customer answers.
Real events, not cron jobs
Visit scheduled, crew en route, job completed, invoice sent. The event fires, the sequence enrolls the contact — nobody opens a spreadsheet.
Filter who gets in
Condition groups run once, at enrollment. Only overdue invoices, only first-time customers, only the jobs you actually want followed up.
Or enroll them yourself
Pick contacts from a list, or add someone straight from their record. Up to 50 at a time, into any published sequence.
Five sequences, already written.
Every workspace ships with them, switched off. Read the emails, pick a mailbox, turn them on.
- Visit remindersVisit scheduled
- 1Your visit is bookedRight away
- 2Reminder: your visit is coming up2 days before the visit · 9:00 AM
- 3We'll see you todaySame day as the visit · 7:30 AM
- 1
- Invoice remindersInvoice sent
- 1Your invoice is due soon2 days before the due date · 9:00 AM
- 2Your invoice is overdue3 days after the due date · 9:00 AM
- 3Invoice still outstanding10 days after the due date · 9:00 AM
- 1
- Job follow-upJob completed
- 1Thank you!Right away
- 2How did everything go?10 days later
- 1
- On our wayVisit en route
- 1We're on our wayRight away
- 1
- Visit follow-upVisit completed
- 1Thanks — see you next timeRight away
- 1
Or write your own. A sequence is an ordered list of emails, a delay between each, and a mailbox to send from — nothing to wire up.
It reads like you wrote it. Because you did — once.
Hi contact.firstNamethere,
A quick reminder that invoice invoice.number for invoice.total is due on invoice.dueDate.
Let us know if you have any questions.
It won't email your customer at 11pm.
A delivery window, a timezone, and business days only. A step that comes due at midnight on a Friday waits for Monday morning — because that's when a person would have sent it.
Delivery window & timezone
Pick the hours, pick the IANA timezone, and flip on business-days-only. Anything that comes due outside the window waits.
One thread, not six
Step one opens the thread; every later step replies into it. Your customer sees a conversation, not a pile of unrelated mail.
Replies end it
An inbound reply exits the run on the spot. Nobody gets nudged about an invoice they already answered.
Unsubscribe means everywhere
One click suppresses that address across the whole workspace — every sequence, now and later.
Every send, accounted for.
Who's in, where they got to, and why they left — without opening a single email client.
Where everyone stands
Every enrollment, which step it reached, and how it ended.
The numbers, live
Enrolled, active, completed, exited, failed — plus reply and bounce rate.
Pull someone out
Remove a recipient and their run stops on the spot.
Publish when you mean it
Edit the draft freely — in-flight runs keep the version they started on.
Sequences don't run alone.
They compile down to a workflow, enroll off dispatch and billing events, and report into the same dashboards as everything else.
- [01]Workflow
Every sequence compiles down to a workflow the engine runs and retries.
- [02]Dispatch
Scheduled visits, en-route crews, and completed jobs are the events that enroll.
- [03]CRM
Recipients are real contacts, and the fields you merge in are their fields.
- [04]Messaging
Sends from a connected mailbox — and their reply lands in your shared inbox.
- [05]Agents
When a reminder needs a decision instead of a timer, an agent takes it.
- [06]Reporting
Sequence activity reports alongside everything else in your dashboards.