How it works

Not forwarding.
Identity-aware routing.

Customers write to any address on your domain. OhRelay routes it to your inbox and keeps the sender identity intact — so your reply comes back from the right address, automatically.

The flow

One conversation, start to finish

01

Customer writes to a managed address

The outside world still writes to support@, billing@, sales@, or another domain address without seeing anything about your internal inbox structure.

02

OhRelay resolves which address was contacted

The system identifies exactly which managed address the customer contacted instead of treating the message like generic forwarding with no reply context.

03

Mail lands in the mapped working inbox

That address is routed into the inbox that should actually process the work, whether it belongs to an owner, one operator, or a small remote team.

04

The operator replies from their usual workflow

The operator keeps working inside Gmail, Outlook, or Apple Mail instead of switching into another mailbox product or juggling multiple domain accounts.

05

The correct sender address is restored on the way out

The reply goes back out with the same visible sender address the customer originally contacted, which is the part ordinary forwarding usually does not preserve.

Under the hood

Why this is different from plain forwarding

Not a mailbox.  Not a bulk email tool.  Not a forwarding alias.

OhRelay is a routing and identity layer.

It's the piece that sits between your domain addresses and the inbox you already use, and keeps everything aligned.