Snooze & Send Later
Two ways of moving a message in time, built on opposite mechanics: parking one is a timestamp the reading list obeys, and holding one is a draft a worker has to claim before it can go.
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 exactly 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.
The clock arithmetic happens in your browser
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 send is a claimed draft
The message waits as a draft marked scheduled, and the worker takes an exclusive claim on it before it contacts the provider, so two workers cannot each deliver a copy.
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
- Cancelling 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 sync providers, tracking, calendar and meetings.
Google Calendar writes out the moment you save and mails the invitations, and reads back on demand, so a meeting booked on a call is there before it ends.
Connect Gmail on one scope and mail arrives by push rather than polling, filed against the lead holding the address, with nobody having to forward anything.
Outlook and Microsoft 365 sync through Graph with delta queries and subscriptions, so large mailboxes stay current without re-reading themselves.
A Microsoft mailbox brings its calendar and address book over Graph, on subscriptions that renew themselves, with a ten-minute pass running underneath.
Any mailbox that speaks IMAP and SMTP connects with a form and a live login test, so a provider nobody built an integration for is still a real inbox here.
Templates with merge variables, organised into groups and permissioned per team, so the answer your best rep writes becomes the answer everybody sends.
Grant a whole template folder to particular roles and teams, so regulated copy stays with the people allowed to send it. Filing is the act of sharing here.
Book from the conversation, with the invitation, the joining link and the record all created together instead of in three separate tabs afterwards.
Connect Zoom and a booking creates, moves and cancels the meeting for you, with the joining link and passcode riding inside the calendar invitation.
Pick Google Meet on a booking and the calendar write mints the link with the invitation, so everyone on the account gets it rather than finding it in a note.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.
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