Is OhRelay a mailbox hosting product?
No. OhRelay is not another mailbox suite. It is a brand identity and inbox routing layer that works with the mailbox workflow your team already uses.
FAQ
Questions people should understand before they ever touch setup.
The goal is to make the model clear: keep the inbox workflow, move brand identity complexity into routing, and avoid replying from the wrong sender.
Common questions
The short version
These are the objections and misunderstandings the website should answer before a prospect even asks for a demo.
Is OhRelay an email marketing or bulk sending system?
No. OhRelay is built for receiving, routing, and replying from the correct branded identity. It is not designed for newsletter campaigns, bulk outreach, or mass sending.
How is this different from ordinary forwarding?
Forwarding only solves where a message arrives. OhRelay also keeps track of which branded identity should be used when the operator replies.
Do I need many domains for this to make sense?
No. OhRelay also fits single-domain businesses that still need several visible identities such as support, sales, admin, billing, or founder.
Do operators need to log into OhRelay every day?
Not necessarily. In the current owner-focused model, the owner or admin mainly configures routing. Operators can stay inside the inboxes they already use.
Can we keep using Gmail, Outlook, or Apple Mail?
Yes. The product is designed to preserve the existing mail workflow instead of forcing a move into a new shared inbox or mail client.
Why can replying be blocked sometimes?
The system should not guess the sender identity. If the routing context is not strong enough to prove which branded sender should be used, the safe action is to stop instead of sending from the wrong identity.