AH Media
AH Media
Where Your Enquiry Form Data Actually Goes
Technology Decisions

Where Your Enquiry Form Data Actually Goes

By Alex Hayes ·

Every firm I worked with had a contact form. Almost none could tell me where the submissions went after somebody clicked send. That is an odd gap in a business that holds tax records and financial statements for a living, and it exists because the form is treated as a decoration on the contact page rather than as the piece of data infrastructure it is.

The Form Is a Database, Not a Letterbox

How to Reset and Restore Your HP Laptop Keyboard | HP® Official Site

What Happens Between Submit and Inbox

A visitor fills in four fields and clicks send. What follows is three separate operations that most firms assume are one.

First, the form plugin writes the submission to your website's database. Second, it assembles an email and hands it to the server's mail function. Third, something somewhere delivers that email, or quietly does not.

Those steps fail independently. The database write almost always succeeds, which is how a firm ends up sitting on eighteen months of enquiries it never saw. Delivery is the fragile one, and the only one anyone notices, because it is the only one that produces something visible.

When a partner tells me the contact form is broken, they mean the third step. They rarely know the first two exist.

The Submissions Table Nobody Opens

Most form plugins retain submissions by default. Not as a feature somebody switched on - as the shipping configuration. Names, email addresses, phone numbers and whatever the sender typed into the message box, held in your site database indefinitely.

For a cafe taking booking requests, that is untidy. For an accounting practice it is a holding of personal information nobody has assessed, duplicated into every nightly backup, and readable by anyone with database access - your host, your developer, and whoever inherits the site after them.

The free-text message field is the part that should bother you. People disclose more in an open box than they intend to. I have seen IRD numbers, account balances and the outline of a family trust dispute typed into a contact form by someone who assumed it went straight to a partner's inbox.

The Privacy Act 2020 applies from the moment that data lands, and the retention principle the Office of the Privacy Commissioner keeps returning to - do not hold personal information longer than you have a use for it - is not an unfamiliar idea inside your firm.

Why This Matters More for Your Firm Than a Cafe

Two things separate a financial services practice from an ordinary small business here.

The first is what people volunteer. A prospective client explaining why they are looking for a new accountant is usually describing a problem: an audit, a partnership coming apart, a trust that has gone wrong. That is the enquiry, and it is also the disclosure.

The second is the standard you are held to. Clients hand over their financial lives assuming your firm is careful with information, and an unaudited archive of form submissions sits awkwardly next to that assumption.

None of this warrants alarm. It warrants an answer to one question: how long does our website keep form submissions, and who can read them? If nobody in the firm can answer that, you have found something worth resolving this quarter.

The Enquiries That Never Arrive

Your Server Is Not a Mail Server

Notification email is where enquiries actually disappear. The default arrangement on most hosting is that the web server generates the message itself and pushes it out directly. That worked in 2010. It does not work now.

Receiving systems have spent fifteen years learning to distrust mail from unfamiliar servers, and a shared web host sending mail that claims to come from your firm's domain is precisely the pattern they are trained to reject. Sometimes it bounces and you find out. More often it is accepted and filed as junk, which is worse, because nothing tells anybody it happened.

The remedy is unglamorous. Notification mail should leave through the same authenticated mail service the rest of the firm already uses, rather than being improvised by the website - usually a half-hour job nobody has been asked to do.

SPF, DKIM and DMARC in Plain Terms

Three standards decide whether the receiving system believes your mail is really yours.

- SPF is a list, published in your domain's DNS records, of the servers permitted to send mail on your behalf. If the website is not on it, the mail is suspect.
- DKIM is a signature attached to each message and checkable against a key in those same records, proving nothing was altered in transit.
- DMARC is your instruction to everyone else about what to do when the first two fail: ignore it, quarantine it, or reject it outright.

The failure I met most often was a firm with a strict DMARC policy, correctly configured by their IT provider, and a website the IT provider had never been told about. The policy was doing exactly its job. It was rejecting the firm's own enquiries.

Getting the three records consistent is routine work, and New Zealand's national cyber security agency publishes plain guidance for organisations without an in-house mail administrator.

Spam Filtering Has a Cost, and It Is Not Money

Women hands typing on laptop keyboard | deBanked

The Three Ways to Stop a Bot

Form spam is not really a question about spam. It is a question about which genuine enquiries you are prepared to lose in order to avoid it.

There are broadly three mechanisms. A challenge asks the visitor to prove they are human, either visibly or in the background by scoring their behaviour. A hidden field catches automated submitters that obediently fill in everything they find. A content filter judges the submission against patterns, keywords or a reputation list.

Each trades convenience against accuracy in a different direction. Challenges are the most effective and the most intrusive, and the background-scoring variety sends behavioural data about your visitors to a third party - worth knowing before you put one on a page where people disclose financial trouble. Hidden fields cost the visitor nothing and stop perhaps half of it. Content filters are the most likely to be wrong about a real person.

The Enquiries Your Filter Ate

False positives are the expensive part, and they are invisible by design. A filter that quarantines a genuine enquiry does not tell you it has done so; that is what quarantine means.

The submissions most likely to be caught are the ones you most want. Long messages. Messages carrying figures and dates. Messages with a link in them, because the sender pasted their current accountant's website or their Companies Office listing. Spam scoring was tuned on retail contact forms, and a detailed enquiry from a business owner in difficulty looks statistically odd.

If your form has a spam folder, somebody should open it monthly. In every firm where I asked whether anyone did, the answer was no, and in roughly a third of them we found real enquiries sitting in it.

Where the Data Goes Next

Close up shot of male hands typing on laptop while sitting at office desk  indoors, man fingers tapping and texting on comput...

Integration Is a Second Copy

The tidy answer is to push submissions straight into a CRM or practice management system, so the website becomes a doorway rather than a filing cabinet. That is the right instinct, and it brings a problem of its own.

An integration does not move data. It copies it. The submission still lands in the site database, still generates an email, and now also travels to a third system - frequently by way of an intermediary automation service that keeps its own log of everything passing through. One enquiry, four copies, three of which nobody has thought about.

That is manageable, but only when it is deliberate. The version that works has one authoritative destination, retention switched off at the website end once the handoff has proved reliable, and a written answer to where each remaining copy lives.

Questions to Ask Before You Sign Off

You do not need to configure any of this yourself. You need to be able to interrogate the person who does.

- Does the form store submissions in the site database, and if so, for how long?
- Which service sends the notifications, and do our SPF, DKIM and DMARC records know about it?
- What stops spam, where do rejected submissions go, and who reads them?
- If enquiries are pushed into another system, what else sees the data on the way?
- Who, by role, can read historical submissions today?

Any competent developer answers those inside ten minutes, and the answers tell you more about the condition of your website than a redesign proposal ever will. A blank look on the second or the fifth is itself the finding.

A contact form looks like the least consequential element on a professional services website - four fields and a button, delegated to whoever built the site. It is also the only part of that site that collects personal information from strangers, keeps it, and then decides on your firm's behalf whether an enquiry reaches a human. Most practices find out which of those three it is getting wrong when a client mentions the email they never got a reply to.

The Briefing

Digital strategy analysis for NZ financial professionals. No jargon, no upsells, no SEO promises -- just the insights Alex would give you over coffee if you had the meeting.