Who should receive your website enquiries? Routing without info@

A shared info@ address feels safe and quietly loses enquiries. How to route each contact form to a named owner, cover absences and leavers, and keep fewer copies of personal data.

Most websites send every enquiry to the same place. It was set up years ago, usually by whoever built the site, and it points at info@, or at the owner, or at someone who has since left. It is rarely a decision anybody remembers making.

That address decides more than it looks like it does. It decides how quickly a customer hears back, whether anybody feels it is their job to reply, and how many people end up holding a stranger's name, phone number and description of their problem. This post is about making that decision on purpose.

Speed is set by who receives the message

The best-known research on this is old, American and still worth reading. In "The Short Life of Online Sales Leads" (Harvard Business Review, March 2011), James Oldroyd, Kristina McElheran and David Elkington describe two studies.

In the first, they audited 2,241 US companies by sending each a web-generated test lead. 37% responded within an hour, 16% within one to 24 hours, 24% took longer than 24 hours, and 23% never responded at all. Among companies that responded within 30 days, the average response time was 42 hours.

In the second, covering 1.25 million sales leads received by 29 B2C and 13 B2B companies in the US, firms that tried to contact a potential customer within an hour of the query were nearly seven times as likely to qualify the lead — which the authors defined as having a meaningful conversation with a key decision maker — as firms that tried even an hour later, and more than 60 times as likely as firms that waited 24 hours or longer.

The numbers are fifteen years old and from a different market, so treat them as a direction rather than a benchmark. The part that has aged best is the explanation. Among the reasons the authors give for slow responses are leads being retrieved in daily batches rather than continuously, and rules for distributing leads among agents "based on geography and 'fairness'". In other words: routing. The delay was not in the reply. It was in getting the message to someone who would reply.

Why info@ loses enquiries

A shared address is comfortable because it looks like cover. Five people get the message, so somebody will deal with it. That is precisely the problem.

In a 1968 experiment by John Darley and Bibb Latané, participants who believed others could also hear an emergency were slower to report it; in the authors' words, the presence of other bystanders "reduced the individual's feelings of personal responsibility and lowered his speed of reporting". A quote request is not an emergency, and a lab study from 1968 is not a study of mailboxes. But anyone who has worked from a shared mailbox will recognise the mechanism: each reader assumes one of the others has it.

The practical failure modes are less subtle.

The leaver's mailbox. The form still sends to someone who left in March. Their mailbox was converted to a shared mailbox, or forwarded to a manager, or quietly deleted. Nobody tested which.
The holiday. The one person who actually answers info@ is away for a fortnight. An out-of-office reply is not an answer, and depending on how the form sends mail it may never reach the customer at all.
The forgotten rule. A forwarding rule, a mail flow rule or a mailbox filter moves form mail to a folder. It was set up to deal with spam in 2021, by someone who is not sure it is still there.
The drowned message. The address is printed on the website, so it also receives supplier pitches, newsletters, invoices and every kind of form spam. The one real enquiry of the day is message thirty-one.

None of these produces an error. Mail that goes to the wrong place looks exactly like a quiet week. If you suspect messages are going missing rather than being ignored, how form notifications are sent, and why they get rejected covers the delivery side.

One form, one purpose, one owner

The design that works is not complicated, and it does not need new software.

Split forms by purpose. A quote request, a job application and a support problem are different pieces of work for different people. If they arrive through one form, someone has to read and re-send each message before anybody can act on it. Separate forms — or at least separate destinations — remove that step.

Give every form one named owner. Not a department, a person. The owner does not have to answer every message themselves, but they are the one who notices when a message has not been answered.

Use a team where cover matters, and still name one person. For a busy sales form it is sensible for three people to receive a copy. Agree which of the three is responsible today, and say so where the others can see it. Copies are for cover; responsibility is singular.

Always have a fallback. Every route needs a second person who picks up when the owner is absent, and who is told that they are the fallback. A fallback nobody has been told about is not one.

Define "answered". A reply that says "thanks, we'll be in touch" stops the customer chasing, but it does not move the enquiry on. Decide, per form, what a proper first response contains.

A routing table you can copy

Adjust the roles to your organisation. The point is that every row has a person, a definition and a backup.

Enquiry type	Who owns it	What "answered" means	Fallback
Quote or price request	Named estimator or salesperson	A price, a visit date, or one specific question that moves it on	Sales lead or owner
Existing order or job	Account or project manager for that customer	The customer has a status and a date	Office manager
Support problem or complaint	Support lead	Acknowledged by a named person, with the next step stated	Operations manager
Job application	Hiring manager	Acknowledged, and the candidate knows what happens next	HR or owner
Press, partnership, sponsorship	Marketing lead	A yes, a no, or a date for a decision	Managing director
Request about someone's personal data	Whoever handles data protection	Logged with the date received, then handled	A named deputy

The last row is there because it has a clock on it. Under Article 12(3) of the GDPR, the controller must provide information on action taken on a data subject request "without undue delay and in any event within one month of receipt of the request". A request that sits in info@ for three weeks has used most of that month.

Absences, leavers and the quarterly check

Routing decays. People go on holiday, change roles and leave, and the form keeps sending to the address it was given.

Have an absence plan before the absence. When the owner of a form is away for more than a day or two, change the recipient to the fallback, rather than relying on an out-of-office.
Remove leavers on their last day. Taking someone off every form's recipient list belongs on the same leavers checklist as disabling their account. The UK National Cyber Security Centre's guidance on identity and access management recommends a "joiners, movers and leavers" policy "so access can be revoked when no longer needed, or changed for movers". Receiving a copy of every enquiry is access, even if nobody calls it that.
Review who receives what every quarter. Fifteen minutes with the routing table: is every owner still here, still in that role, still the right person? Send a test enquiry through each form and check it lands where the table says.

Fewer copies is also a data protection decision

Every enquiry contains personal data: a name, an email address, often a phone number, sometimes a description of a health problem, a legal dispute or a financial situation. Each person who receives a copy holds that data in their own mailbox, on their own phone, for as long as they keep it.

The GDPR's data minimisation principle, Article 5(1)(c), requires personal data to be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed". The UK ICO's guidance on data minimisation adds: "You should periodically review your processing to check that the personal data you hold is still relevant and adequate for your purposes, and delete anything you no longer need." Article 5(1)(f) separately requires processing "in a manner that ensures appropriate security of the personal data".

Sending every enquiry to ten people because it is easier than deciding who needs it is hard to square with either. Routing a careers form only to the hiring manager, rather than to the whole company, is both better practice and less exposure if a single mailbox is ever compromised. This is an explanation of the principle, not legal advice; if your enquiries routinely contain sensitive information, confirm your approach with your own adviser.

Changing recipients without touching the website

The obstacle for most businesses is not agreeing the table. It is that the recipient address lives inside the website's form settings, and changing it means logging into WordPress, or asking the agency, or finding whoever still has the Webflow password. So it does not get changed, and the leaver stays on the form.

One way round that is to point each form, once, at an address whose recipients are managed somewhere else. In Humainbox, each form gets its own inbox address, and you set the recipients per inbox — a named person, or a team where every member gets a copy. Anyone who is not already a verified member of your workspace confirms before they receive anything, so a mistyped address or someone who never agreed to it does not silently receive customer data. When someone leaves or goes on holiday, you change the inbox's recipients in the panel; nobody opens the website. The how it works page covers the rest, and there are notes for growing teams and for businesses whose work arrives as a quote request, where one enquiry you never saw is a job that went to somebody else.

Whatever you use, the test is the same: can the person responsible for routing change it on a leaver's last day, without a developer?

Where this gets hard

One form for everything. Many sites have a single "Contact us" form, and splitting it is a website change someone has to pay for. In the meantime, a dropdown asking what the enquiry is about helps a human triage faster, but it does not route anything by itself — somebody still reads every message first. If you are stuck with one form, make that triage a named job with a fallback, and treat splitting the form as the fix.

Enquiries that belong to two teams. A customer with an open complaint asks for a quote for more work. A job applicant is also a customer. There is no clean rule for these. The useful habit is that whoever receives it first owns it until they have handed it over explicitly — "I've passed this to Sam, who will reply today" — rather than forwarding it and assuming.

Filtering and routing interact. The more people a message passes through, the more places it can be wrongly binned. If you add spam filtering to a form, make sure the owner can see what was held and why; our post on false positives in spam filters goes into what that costs when it goes wrong.