How OhRelay works: one inbox, many domain email addresses

The address your customer sees

A managed address is any domain email address a customer can write to: support@, billing@, hello@, founder@, or anything else tied to your domain.

These addresses matter because customers trust them and expect replies to come from the same place. They’re not just delivery endpoints. They’re part of how your business presents itself.

The problem when addresses multiply

Most small teams don’t have a separate person behind every address. One founder or a small team handles everything across several domains.

Traditional mailbox tools force you to turn every visible address into another account, another subscription, another inbox. The result: too many inboxes for too few actual handlers.

• More customer-facing addresses than real operators
• More logins and more seat cost than the team needs
• More chances to reply from the wrong sender

What OhRelay changes

OhRelay sits between the addresses your customers contact and the inboxes your team already uses. Mail arrives at support@ and routes into your Gmail. You don’t need to switch to a new mailbox product or change how you work.

• Customers keep writing to the addresses they already know
• Mail lands in the inbox mapped for that address
• You keep working in your familiar mail client

Why replies look correct

Getting mail in one place is only half the job. The harder part: making sure your reply goes back from the same address the customer originally wrote to.

OhRelay tracks which address each conversation came through. When you reply, the message goes out through your OhRelay gateway. In Gmail, that means choosing the gateway in the From field. In Apple Mail and many desktop clients, once SMTP is configured, you usually don’t need to keep selecting it. Either way, OhRelay uses the conversation context to restore the correct domain address on the outbound message, so the customer sees a reply from the address they originally wrote to.

A simple example

One founder handles support@studio-a.com, hello@project-b.com, and founder@project-c.com. Without OhRelay: juggling three mailboxes or maintaining a fragile alias setup. With OhRelay: one inbox, one gateway configured on that inbox, and replies that still show the correct address to the customer. In Gmail, that usually means selecting the gateway when you send. In desktop clients, it often fades into the background once the SMTP server is configured.

It’s not just one inbox

One inbox for all addresses is the most common use case, but it’s not the only one. Different addresses can route to different people or teams. What matters is that routing is configurable without requiring a separate mailbox account for every customer-facing address.