Every email, on the record it was about.
Write it in the composer, send it from your own mailbox, and watch what happens to it — delivered, opened, replied — in the same feed as the form they filled in and the file they signed.
You can see what happened to it.
A send is not the end of the story, so the page does not stop there. Each state is a fact the message reported back, timestamped on the record — and the first open is something a workflow can start from.
In the composer
9:02 · as you
9:14 · twice
Starts on the open
9:20 · threaded
One page for everything you have sent.
Five tabs, and each one answers a question you actually ask about mail.
Outbound
Everything that went out, newest first, with what it was about and what it has done since.
Drafts
Started and not sent. Opens back into the composer with the recipients still on it.
Queued
Written and waiting — a batch going out, or a step whose delay has not run down yet.
Failed
What did not arrive, and why. A bounce says which address and what the server said about it.
Templates
The messages you send more than once, edited in the same window a workflow step uses.
The composer, and what it reaches.
It is one editor, and it is the same one everywhere — the Email page, a workflow step, a sequence step.
Fields from the record
Drop in a name, a date, any attribute. Each recipient gets their own version, resolved when it sends.
Attachments and share links
A file from Files, a link to a folder, or a PDF filled in from the record it is going to.
Signatures
Kept per workspace and picked on the message, so a sequence step signs off the way you do.
Templates
Save the message you send every time and open it again from the composer or from a workflow.
A list, or one person
Address it to a contact list and it goes to everyone on it, each as their own message — not a Cc pile.
Your own mailbox
Connect Gmail and it sends as you, in your thread. Or send through Resend from a domain you verify.
And what comes back lands there too.
The states a message reports, and the one it cannot report on its own — a reply, which is noticed and threaded onto the conversation it answers.
Opens
When it was first opened, and how many times since.
Clicks
Which links were followed, and how often.
Replies
Threaded onto the message they answer, and enough to end a sequence for that person.
Bounces
The address that failed and the reason the receiving server gave.
On the record
Every one of the above in the record’s activity feed, beside the notes and the files.
And it can start something
An open or a reply is a workflow trigger, so the follow-up is written once and fires on the first open rather than on your going back to check.
Mail is one part of it.
It reads the same records, and writes to the same feed, as the rest of the workspace.
Send the first one this afternoon.
Connect a mailbox, pick a list, and write it. The record keeps the rest.