Managed inbound email routing
One inbox for every address your business publishes.
Business Inquiry Hub receives mail for your domains and forwards it to the mailbox your team already uses. Sales aliases, contact forms, listing inquiries, catch-all traffic — routed, authenticated, and delivered without adding a single new mailbox.
One DNS change per domain. No new mailboxes. No migration.
- sales@yourdomain.com
- info@yourdomain.com
- careers@yourdomain.com
- hello@second-domain.com
- *@retired-domain.com
Destination
you@company-inbox.com
The problem
Addresses multiply. Attention doesn't.
Every business ends up publishing more email addresses than it can reasonably watch. A sales alias on the website. An info address on the Google Business Profile. A careers address in a job ad. A per-campaign address on a printed flyer. A domain from a rebrand three years ago that still receives real mail every week.
The usual fixes both cost something. Buying a mailbox per address means paying a per-seat licence for an address that receives four messages a month. Configuring forwarding by hand means maintaining rules across several providers — and naive forwarding quietly breaks sender authentication, so the messages that do arrive land in spam.
Per-seat pricing punishes addresses.
Mailbox licences are priced for people, not for aliases. An address that receives four messages a month costs the same as a full-time employee's inbox.
Unwatched addresses lose work.
An inquiry sitting in a mailbox nobody opens is indistinguishable from an inquiry you never received.
Hand-rolled forwarding fails quietly.
Forwarded mail loses SPF alignment. Nothing errors and nothing alerts you. The message simply arrives in a junk folder, or not at all.
How it works
Four steps, one DNS change per domain.
- 01
Point your domain at us
You add the MX records we provide to each domain you want us to receive on. That is the only change to your DNS, and the only step that touches your own infrastructure.
- 02
Tell us where mail should go
Send us the routes: which addresses, aliases or wildcards should reach which destination. Specific addresses, per-domain defaults, catch-all, or any mix of the three.
- 03
We receive, filter and re-envelope
Inbound mail is accepted on your behalf, checked for spam and malware, then re-enveloped with SRS so that it authenticates correctly when it reaches you.
- 04
It lands where you already work
Gmail, Outlook, Fastmail, a shared mailbox, a helpdesk queue. You read and reply in the client you already use, from the address you already use.
Capabilities
Routing that matches how your business is actually organised.
Address-level routing
sales@to the sales inbox,careers@to whoever handles hiring. Every address you publish can resolve somewhere different.Wildcards and catch-all
Route
*@yourdomain.comto a single destination so a mistyped or discontinued address still reaches someone.Many domains, one destination
Consolidate trading names, regional domains and retired brands into the inbox you actually check.
One address, many recipients
Fan a shared alias out to everyone who should see it, without paying for a distribution list in your mail provider.
Contact form delivery
Route submissions from your website forms through the same pipeline as the rest of your inbound mail, so everything arrives in one place.
Attachments preserved
Messages are relayed intact. Attachments, inline images and formatting arrive as the sender composed them.
Filtering before delivery
Spam and malware are rejected upstream, so your destination inbox receives inquiries rather than noise.
Loop and duplicate protection
Routing rules are checked for cycles, and repeated deliveries are suppressed before they multiply.
Deliverability
Forwarding breaks email authentication. Handling that is the job.
When a message is forwarded, the receiving server sees it arrive from an IP address the original sender never authorised. That is not a flaw in your setup — it is how SPF is specified. Any forwarding arrangement that ignores it is quietly costing you mail.
| Mechanism | What forwarding does to it | How we handle it |
|---|---|---|
| SPF | What forwarding does to itThe original domain's SPF record lists the sender's own servers, not ours. A forwarded message therefore fails SPF when it reaches you. | How we handle itWe rewrite the envelope return-path to a domain we control, using SRS. The destination evaluates SPF against our published record instead, and it passes. |
| DKIM | What forwarding does to itSignatures cover the message headers and body. They survive forwarding intact, unless something modifies the message in transit. | How we handle itWe relay messages without altering signed content, so the sender's original DKIM signature arrives verifiable. |
| DMARC | What forwarding does to itRequires SPF or DKIM to pass and to align with the domain in the From header. A naive forward fails both tests at once. | How we handle itBecause the original DKIM signature survives the relay, DMARC still aligns for any sender who signs their outbound mail. |
| Bounces | What forwarding does to itA rejection sent to a rewritten return-path can be lost, leaving the original sender with no indication that delivery failed. | How we handle itReturn-path rewriting is reversible, so a rejection at your destination is returned to the original sender as a proper non-delivery report. |
We publish and maintain SPF, DKIM and DMARC records on our own sending domain, and we monitor the sending reputation of the addresses we relay from. Forwarding is only useful if the mail arrives.
Who it's for
Built for businesses running more than one front door.
Agencies and studios
Receive on behalf of client domains without provisioning a mailbox inside every client's tenant, and without asking clients to hand over administrative access to their mail.
Multi-brand operators
Several trading names, one team. Every brand keeps its own published address, and the team keeps one inbox.
Trades and local services
Your address appears across directories, listing sites, van livery and printed material. All of it arrives in one place, including the versions you have forgotten you published.
Domain portfolios and acquisitions
Retired and acquired domains keep receiving real mail for years after anyone stops watching them. Catch-all routing means none of it is silently discarded.
Multi-site operators
One routing layer for every contact form across every site you run, instead of a separate notification address configured per site.
Reliability
What happens when the destination doesn't answer.
Queue
Retried, not dropped
If your destination is temporarily unavailable, messages are held and retried on a backoff schedule rather than discarded.
Greylisting
Deferrals handled
Destinations that defer delivery on first contact are retried automatically, which is exactly the behaviour greylisting is designed to expect.
Logging
Delivery records
Each relayed message is recorded with its envelope details and delivery outcome, so “did that inquiry actually arrive?” has an answer.
Changes
Updated by request
Routes are changed by our team when you email us. There is no console for someone to misconfigure at two in the morning.
For recipients
Did you receive a message from emails@ or forms@businessinquiryhub.com?
Those addresses belong to our relay infrastructure. emails@businessinquiryhub.com and forms@businessinquiryhub.com are used to deliver mail on behalf of businesses that route their inbound correspondence through Business Inquiry Hub.
The message was addressed to you by a business, not by us.
We operate the delivery path it travelled along. The original sender's own details are preserved in the message body and its headers.
Reply exactly as you normally would.
Your reply goes to the business that contacted you, using the reply address in the message. It does not come back to us.
We do not send marketing and we do not sell contact data.
Every message relayed through these addresses originates from a business using the service to receive and route its own correspondence.
Something looks wrong?
Email support@businessinquiryhub.com with the full message headers and the Message-ID, and we will trace which account relayed it.
Frequently asked
Questions we get before setup.
What does Business Inquiry Hub actually do?
We receive email addressed to your domains and forward it to the mailbox you already use. It is a routing layer that sits in front of your existing inbox, not a replacement for it.
Do I need to change email provider or migrate anything?
No. Your existing mailbox stays exactly where it is. We change where inbound mail for your domains is received, not where you read or send it.
Will forwarded mail end up in spam?
Not when forwarding is done properly. Naive forwarding fails SPF at the destination. We rewrite the envelope return-path using SRS so SPF passes, and we relay messages unmodified so the sender's DKIM signature survives for DMARC alignment.
Can I forward several domains into one inbox?
Yes. Each domain needs its own MX records pointed at us, and after that the routes can be as specific or as broad as you like — including several domains all resolving to the same destination.
Can one address deliver to more than one person?
Yes. An address can fan out to several destinations, which is usually simpler than maintaining a distribution list inside your mail provider.
What happens to attachments?
They are relayed intact. We do not repackage, recompress or strip attachments, so the message arrives as it was composed.
Can I still reply from my own address?
Yes. You reply from your normal mail client using your normal address. We handle inbound routing; your outgoing mail continues to leave the way it does today.
Do you filter spam before forwarding?
Yes. Filtering upstream matters more with forwarding than without it, because anything junk that gets relayed reaches you from our infrastructure, and that can affect how your provider treats everything else we send you.
What about a domain I no longer use?
Catch-all routing is usually the answer. Point the retired domain at us and route everything to a destination you check, so mail sent to old addresses still reaches a person.
I received an email from emails@businessinquiryhub.com — what is that?
It was relayed through our infrastructure on behalf of a business that uses the service. Reply as you normally would and your response goes to that business. There is more detail in the section above.
Tell us where your mail needs to go.
Setup starts with an email. There is no signup form and no console to configure — describe your setup and we will send back the DNS records to add, along with the routes we have configured.
Emailsupport@businessinquiryhub.comWe reply to setup requests within one business day.
Useful to include
- The domains you want us to receive on
- The addresses or aliases you need routed
- Where each one should be delivered
- Whether you need catch-all on any domain
- Anything currently forwarding that is not arriving reliably