Your website form still emails one person's Gmail

If your website form still emails one person's Gmail, the enquiries you pay to attract depend on that one person reading it. When they're off sick or out on a job, nobody else knows the enquiry exists. The fix is to send form enquiries into a shared lead list with an owner and a status, and to let email become a notification rather than the record.

How a contact form ends up in a personal inbox

It's rarely a decision. Someone built the first site years ago, a plugin needed an address to send to, and the founder typed their own. The business grew. The form didn't change.

So the form now does one thing: it turns a customer's message into an email and drops it into a private Gmail account. No copy lands anywhere else. There's no record on the website side that the enquiry happened, beyond whatever the form plugin happens to log.

This isn't the same problem as a shared info@ address. I've written about the info@ inbox nobody owns, where too many people can see a message and none of them owns it. A personal Gmail is the opposite. One person owns everything, and nobody else can see any of it.

What breaks when one person holds all the enquiries

• Holiday and sick days: Enquiries keep arriving while the inbox owner is away. Unless they log in from a sun lounger, those people wait, and some of them ring a competitor instead.
• Phone-only triage: The message gets read on a phone between jobs, marked as read, and forgotten. Now it looks handled.
• No hand-off: Passing an enquiry to a colleague means forwarding it. The forward has no status, so you can't tell later whether anyone replied.
• Leaving staff: If that Gmail belongs to an employee rather than the owner, the enquiry history leaves with them.

And the reporting is the unread count. Ask how many enquiries came in last month and how many turned into work, and the honest answer is a guess. A badge on a mail app is not a pipeline.

There's a privacy angle too. Customer names, phone numbers and sometimes addresses are sitting in a personal account the business doesn't control. That's awkward to explain if a customer asks what you hold about them.

What should replace a form that emails one person

The change is smaller than it sounds. The form stops treating email as the destination and writes the enquiry into a list the team shares. Email still has a job: telling the right person that something new has arrived.

A sensible replacement has these parts:

• A lead record: Each enquiry is a row with the customer's message, contact details, where it came from and a status such as new, contacted or quoted.
• An owner: One named person is handling it, and everyone else can see that.
• Notifications by role: Alerts go to whoever covers enquiries this week, not to a fixed personal address.
• A path to a quote: The lead becomes a customer and a quote without retyping it from an email.

Whether that's a CRM you buy or something built into your site matters less than one rule. The website form should never be the only copy of an enquiry, and a personal inbox should never be the system of record.

How Eight Mile websites handle form enquiries

Our managed websites run on TradeOps, our own platform, which keeps bookings, quotes, invoices, email and customer records alongside the site. Enquiries from the site's contact form arrive in the TradeOps leads list rather than someone's mailbox.

That list records the topic picked on the form, the customer's message, contact details, a status, the person handling it and notes. Statuses include new, contacted, quoted, won and lost. A team member picks up the enquiry, then creates a customer and starts a quote with the details carried across, and the lead is marked won when the quote is accepted. Phone calls and referrals can be typed in with their source recorded, so the list isn't only for web traffic.

Because the form and the office tools sit on one platform, nothing has to be copied out of email or passed through a connector between vendors. Roles decide who can view and change the list. A hidden trap field and server rate limits help cut form spam, which matters once real people are working through the queue.

If TradeOps isn't the right shape for your business, the same idea can be built as a small internal tool through our software development work. The point is the record, not the brand of software.

If your website form still emails one person's Gmail today, that's the first thing I'd change. Tell us where enquiries land now and who should own them, and talk to an engineer about moving them somewhere the whole team can see.