Skip to content

For growing teams

Your contact form stopped being a lead channel and became a mailbox to clean.

If enquiries are how work reaches you, the form is not an admin task. It is the top of the pipeline. And the risk is not the forty messages you delete. It is the one real enquiry sitting between them, from someone who is also asking two of your competitors this afternoon.

Humainbox sits between the form and your mailbox. You change one field, the address the form sends to, and real enquiries arrive with the right person named on them.

The failure nobody notices

A reply sent to the wrong address looks exactly like an answered enquiry.

Most contact forms send mail from the website's own address, and put the visitor's address somewhere inside the message instead. Hit reply and you write back to your own server. The message leaves your outbox, it lands in your sent items, and as far as anyone in the team can see, that enquiry was handled.

Nobody chases it, because nothing looks wrong. The enquirer thinks you ignored them. That is the quietest way a business loses work, and it will not show up in any report.

Humainbox resolves the visitor's true reply address before the message reaches you, records where it found it, and flags the messages where it cannot find one. A dead end is visible rather than silent.

The real cost

Spam that looks like an enquiry has to be read before it can be dismissed.

The obvious rubbish costs nothing. It is recognisable in half a second and gone. What costs is the message written in fluent English, addressed to your company by name, referencing a service you actually offer, and asking a question a real prospect might ask. Someone has to read it to the end to decide. Then the next one. Then the next.

That attention comes out of the same person whose job is to answer real enquiries quickly. Do it thirty times a day and the response time on genuine work gets worse, which is precisely the metric the form exists to protect.

Why this decision Spam · 68

“Generic outbound sales pitch with a booking link and no specific detail about this business.”

what the filter read in it

form_provenance
Arrived through the form, from the site's own domain
−15
llm_classification
Read and judged machine-written
+83
total 68 · holds at balanced (60) illustration of the format

The first week

Start in dry run, where nothing changes.

Enquiries can go to a named person rather than to a shared mailbox three people each assume somebody else is watching — but none of that has to be decided first. You should not have to trust a new system with your pipeline on day one. In dry run, every message is delivered exactly as it is now. Humainbox only records what it would have held, so at the end of the week you are reading your own enquiries and judging the calls for yourself.

If it read your traffic the way you would, move to live. And if our system is ever unavailable, mail is forwarded rather than held: the failure mode is a plain forwarder, never a lost lead.

One field, and the form goes back to being a lead channel.

No plugin, no developer, no change to the site itself. Point the form at an address we generate, name who should receive the real enquiries, and leave it in dry run until you are convinced.

We would like to count visits with Google Analytics, which sets two cookies. Decline and nothing is loaded and nothing is sent. What these are.