Skip to booking a call

The 09:12 email had somewhere to land.

On Thursday a client's email reached Northwind on its own domain, in the right folder. One morning of setup, ten days before.

Mon 10:02

MailEarly access

“Why does our email still end in someone else's name?”

Your domain. Two records.

On Monday 2 November, Tobias adds northwind.example and two records where the domain is managed. Mail starts when repa finds them.

Both required records found

Mon 10:30

MailEarly access

“Who has the password for sales@?”

A shared mailbox. No shared password.

[email protected] opens under each person's own sign-in: Ana answers from it, Marcus reads and flags.

sales@ with Ana and Marcus and their rights

Mon 11:15

MailEarly access

“I am not learning another mail app.”

Keep the mail app you have.

Priya downloads one profile for iPhone Mail, and her phone gets her mail, calendar and contacts through the apps it already has.

Priya's mailbox in Apps and devices, last used from iPhone Mail

Thu 09:12

MailEarly access

“It was in my inbox somewhere. Under the newsletters.”

Client mail files itself.

Ana's rule moves anything from harbour-hotels.example into one folder, so Clara's message is the only unread thing in it.

The Harbour Hotels folder with Clara's message

Thu 09:13

MailEarly access

“Is this her latest reply, or is there another one?”

One conversation, in order.

Tuesday's proposal, Wednesday's reply and Clara's answer sit in one conversation, with her two attachments under it.

The whole conversation in order

Thu 11:46

MailEarly access

“Did she get it? Should I send it again?”

Sent. Then shown as delivered.

Ana replies in the same thread with the contract and copies sales@. The Sent folder says when Harbour Hotels' mail server accepted it.

Delivered 11:46
northwind.exampleown domainsales@her own appfiled by ruleone threadSendingDelivered

Nobody at Northwind thought about mail on Thursday.That was the point.

Two records, one shared mailbox, one rule. Four messages in one conversation, and a contract shown as delivered at 11:46.

Checked before it reaches you.

Incoming mail is scored for spam; mail carrying a virus is refused; mail that fails its sender's own rules goes to Junk; a link that hides where it goes gets a warning; pictures from the web load only when you ask.

A warning about a lookalike link, with pictures held back

Calendar and contacts come along.

Calendars and address books reach the apps already on a phone or a laptop, and an invitation is answered inside the message. Standard mail apps connect too.

An invitation answered inside the message

From your own software.

Your own software can send from your addresses, with a key limited to the addresses you pick.

Send the contract from your system@repa/mail
import { createEmailClient } from "@repa/mail";

const mail = createEmailClient({ apiKey, subject: userId });

await mail.send(
  {
    from: "Ana Ribeiro <[email protected]>",
    to: ["[email protected]"],
    subject: "Harbour Hotels: first-year proposal",
    text: "The contract is attached.",
    attachments: [{ filename: "contract.pdf", contentType: "application/pdf", content }],
  },
  { idempotencyKey },
);

Bring the domain you already own.

Thirty minutes. We walk through the two records; you decide if it is worth a Monday morning.