What people run
on OpenEmail.
12 jobs people run on OpenEmail, from the whole of a company's mail to the receipts an app sends. Each one shows the setup, the parts it runs on and the walkthroughs underneath.
One mailbox, and the jobs people hand to it.
Addresses for people and for roles, all on one domain. Each has its own people, keeps the shared sign-off, and stays put when somebody leaves.
One address on your own domain, worked by the people you grant it to. Rules label and answer mail as it arrives, and everybody reads the same thread.
sales@, jobs@ and billing@ get worked by several people at once, each with their own access. Nothing is forwarded, and nobody leaves with the address.
Your app posts a message and OpenEmail sends it from your own domain. Every call sits against the key that made it, and every send has an outcome to read.
Write it once as a template. Send it from the composer, from your own code or on a day you pick, then read what happened after.
Give an agent an address of its own and a key scoped to what it may do. It reads, labels, drafts and sends, and every call it makes is logged.
Every ticket, record or customer can have its own address. Mail sent there reaches your endpoint as a signed event, and your code answers as that address.
Each client gets a workspace of their own: their domains, their addresses, their people. You switch between them at the top of the sidebar, and nothing crosses over.
Your domain, an address you invent for each signup, and nothing reporting back when you read. Change provider later and the addresses come with the domain.
Every form wants an address. Give each one its own, see which starts getting spam, and switch that one off without touching the rest.