The goal is to make the model clear: keep the inbox workflow you already have, route each domain email address to the right working inbox, and avoid replying from the wrong sender. Your mail stays in your own account — OhRelay only handles the routing layer.
These are the objections and misunderstandings the website should answer before a prospect ever asks for a demo.
A managed address is any domain email address you route through OhRelay — for example support@yourdomain.com, hello@another-domain.com, or billing@project.com. You do not need a separate mailbox account for each one. OhRelay routes them into the working inbox you already use.
OhRelay does not store email bodies or attachments. Inbound mail is routed to your inbox using recipient metadata — the system reads the address it was sent to, not the message content. Outbound replies pass through OhRelay only to restore the correct sender address. The sent copy lands in your own sent folder, not in OhRelay. What OhRelay does store: your routing configuration — which managed addresses map to which members, and which domains are connected.
No. OhRelay is not another mailbox suite. It is a routing and identity layer that works with the mailbox workflow your team already uses. You keep Gmail, Outlook, or Apple Mail — OhRelay just makes sure the right address goes in and comes out.
No. OhRelay is built for receiving, routing, and replying from the correct address. It is not designed for newsletter campaigns, bulk outreach, or mass sending.
Forwarding only solves where a message arrives. OhRelay also keeps track of which address should be used when you reply, so the recipient always sees the correct sender — not your personal inbox address.
No. OhRelay also fits single-domain setups that still need several visible addresses — support, sales, admin, billing, or founder — without buying a separate mailbox seat for each one.
No. The owner or admin configures routing in OhRelay once. Operators then stay inside the inboxes they already use — Gmail, Outlook, or Apple Mail. OhRelay works in the background.
This is a safety-first feature. If the routing system cannot verify with 100% certainty which branded address should be used, it stops the send rather than risking a leak of your personal or internal inbox address. You simply fix the route configuration or use a verified sender to continue.
Cloudflare's free email routing forwards incoming mail to another inbox — it handles the receive side only. When you reply, there is no system to restore the correct branded sender address, and there is no control panel for managing which address is assigned to which team member. OhRelay adds the full layer: structured inbound routing, outbound sender restoration so replies always go from the right address, and a dashboard for assigning brand addresses to real people on your team.
The smoothest experience is a desktop mail client — Spark, Thunderbird, Mimestream, or any client that supports a custom outbound SMTP server. With that setup, replies go out from the correct address automatically with zero extra steps. If you use Gmail Web or Apple Mail with an external 'Send mail as' configuration, it also works correctly — you select the sender from a dropdown before sending. That one-step selection is required by Google's and Apple's own security model, not a product limitation of OhRelay.
