One job at a time
start to finish.
39 short walkthroughs of things people do with OpenEmail. Each one shows the setup, the screens you use and the parts it runs on.
One domain, a different job on every address.
01
Mailboxes and addresses
Everything that arrives. Domains you own, addresses you invent on the spot, and inboxes that expire.
Give everyone at your company an address on your domain, and decide who reads what.
Own the addresses on your domain, and have them land in mailboxes people already use.
Own the domain your email lives on, and the address stays yours whatever else changes.
02
Inboxes a team works
One address, several people, and a record of who answered what.
Keep every client in its own workspace, with its own domains, people and rules.
Bills land at one address, get filed by rule, and stay searchable by sender or file.
Applications arrive at one shared address, get filed by rule, and are answered from a template.
Read what arrived in your language, answer in theirs, and check it before it goes.
The invoice is due on Friday.
Make any address on your domain and hand it to the people who answer it.
Send from a template, see who opened it, and book the call in the thread.
Everyone works from the same contacts, and your code and agents read the same rows.
An address belongs to the workspace, so the person changes and the mail stays put.
03
Sending
Mail your product sends, and mail you write and schedule yourself.
Send a real invitation from your own address and watch the replies land on the event.
Design the email once, send it from your own code, and see what was opened.
Write it today, land it on Tuesday morning, and edit or stop it until then.
See what happened to every send, and keep dead addresses out of the next one.
04
Built on top
An API, an SDK and MCP, for products and agents that need a mailbox of their own.
Point an assistant at a mailbox and let it read, draft and send.
Every call a key made, every webhook you sent, with the code and the timing.
Say what happens to a message before anybody opens it.
Give each test run its own address and read the mail it receives.
Send, read and organise mail from your own code with a typed client.
Mail arriving at your domain reaches your server as a signed webhook, seconds later.
05
Trust and safety
Who a message is really from, what it carries, and who else can read it.
Publish the records that prove your mail is yours, and check what your domain says in public.
Every message arrives scored, with the sender checks, the reasons and the look-alike domain named on it.
Give every site its own address, then see which one starts getting spam.
Publish an address and decide what reaches you, sender by sender and word by word.
06
Daily work
Triage, drafting, search and the rest of the inbox you sit in every day.
Give the composer a one line note and get back a draft that sounds like you.
Hi Priya, thanks for the quick turnaround.
Can you hold order 4471 until Friday?
Match the mail you choose and answer it with a template, once per sender a day.
Charts for what arrives, what you sent, what was opened and what was clicked.
Every attachment this mailbox sent or received, searchable, weighed and one click from its message.