Snooze & Send Later
Two ways of moving a message in time. Park a thread and it comes back at the hour you named, unread, so it cannot be walked past. Hold a send and it leaves at the hour you named, once, never twice.
Two ways of moving a message in time
the moment arrives- snoozed_until 08:00in the list
the timestamp has passed
- back in the listimmediate
the query compares the timestamp to now, so nothing had to run
- the five-minute sweeppending
timestamp cleared, marked unread again
- is_scheduled, scheduled_atdraft
it waits as a draft, editable, nothing enqueued at the provider
- is_sending false to trueunclaimed
the claim is taken before the provider is contacted, and it matches one row
- accepted, draft deletedpending
no local copy in the sent list, nothing tracking it
Product figures from the platform’s own defaults - not customer averages
How it works.
Back on time, then back to unread
The list stops hiding a parked thread the instant its moment passes, so it returns when you asked rather than on the next tick of something. A pass every five minutes then clears the timestamp and marks it unread again, so it stands out the way fresh mail does.
Tomorrow morning means your tomorrow morning
Presets are worked out where your timezone actually is and sent as one absolute instant. The server is never asked to decide which Saturday you meant.
A held message goes out once, never twice
It waits as a draft marked scheduled, and the worker takes an exclusive claim on it before it contacts the provider, so no customer ever gets the same message from two workers.
A failed send lands back in drafts
An ambiguous failure is not retried, because nobody can tell a message that never left from one that arrived before the connection dropped. A duplicate at a customer is worse than a button you press again.
Two moments in every message.
Every message passes through the same seven. Snooze & Send Later is the lit ones, and everything either side of it is a different page in this category.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
who may use what, and see what
The specifics.
8 facts- Presets
- Later today, tomorrow morning, this weekend and next week, then a picker for anything else
- Ceiling
- A year ahead on a parked thread, and a moment already gone is refused. A held send is only required to be in the future, with no far bound at all
- On maturity
- It is back in the list immediately, and within five minutes a sweep clears the timestamp and turns it unread so you cannot walk past it
- Finding a parked one
- Hidden by default, with one view that shows only the parked threads and another that shows everything at once
- Holding a send
- Five quick picks: fifteen, thirty, sixty or a hundred and twenty minutes, or tomorrow. A picker sits under them for anything else
- Delivery guarantee
- At most once. A failure puts the message back in drafts rather than trying again
- Editing a held one
- Take the hold back first. The worker sends what was stored, so a change made after it has claimed the draft arrives too late
- Taking one back
- Canceling a hold returns the message to drafts with its schedule cleared, at any point before the worker claims it
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
12 capabilitiesWebmail, four mailbox connections, tracking, calendar and meetings.
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change comes back when you sync.
Mail is here without anybody pressing refresh or forwarding anything, filed against the lead holding the address. Google knocks the moment something changes.
The mailbox stays connected, and a message somebody moved is not sitting here twice. Outlook and Microsoft 365 over Graph, picking up only what changed.
A Microsoft mailbox brings its diary and address book with it, and whether it sits in Microsoft 365 or on a server in your building is worked out for you.
The connection for a mailbox nobody hosts for you. We sign in for real before saving the hosts and ports, so a typo is caught while you are still at the form.
Templates with merge variables, organized into groups and granted per team, so the answer your best rep writes becomes the answer everybody sends.
Regulated copy stays with the people allowed to send it. Filing a template into a group is what shares it, so there is no second step for anybody to forget.
A meeting agreed on a call is never lost because somebody else's service was slow. The booking is saved here first, then the room and the calendar entry.
Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes too, with nobody chasing it.
The join link is made by the calendar itself, on the same save that books the meeting, so nobody hunts for it later. One Google account is the whole setup.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
Mail files itself against the lead, on a rule short enough to print: the addresses on the lead, matched exactly. No domain guessing, and nothing to dispute.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Email & Calendar
See snooze & send later on your own floor.
Thirty minutes, your numbers and your data. We will set snooze & send later up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included