For agencies
You did not create this problem. You are just the one who has to answer for it.
Every client site has its own arrangement, none of which you chose, and you are the one who hears about it. The message is always a version of the same thing: did the site break, we are not getting leads.
Nine times out of ten nothing broke. A password expired, a captcha started refusing real people, or the form is working perfectly and what it delivers is rubbish. You are maintaining a pipeline you never sold, across stacks you did not all choose, and you cannot see into any of them without logging into somebody else's site.
One field per form — the address it sends to — and all of them report into a panel you control: what arrived, what we did with it, and where it went, per client.
Every inbox keeps its own address, its own mode and its own threshold.
No client meeting required
You already have the access
This is the part that makes agency rollout unlike every other tool you have evaluated. There is no plugin to vet, no snippet to add to a theme you inherited, no build to run on a site whose original developer left three years ago. The form already sends email. You are already the one with access to the settings screen where it says who receives it. That is the entire integration surface.
01
Generate an address
Add an inbox in the panel. You get an address that belongs to that one form and nothing else.
02
Paste it into the form
Wherever the form stores its recipient, whether that is a settings field, a form builder or a config value, replace what is there.
03
Name who receives it
Point the inbox at a person or at a team where every member gets a copy. The client's mailbox carries on as normal.
It works on stacks you would rather not touch. WordPress, a static site with a form service, a bespoke Laravel app, a page someone built in a website builder and never handed over properly. Because the integration is an email address, the underlying stack stops being your problem.
One panel, every client
Before the client asks
When a client calls to say something got through, or worse, that something did not arrive, you should not have to log into their site to find out. Every message that passed through any of your addresses stays visible in one place, with the decision that was made and the signals behind it.
Who receives a client's enquiries lives in your panel, not in their website, so changing it needs no deploy and no conversation with whoever maintains the theme. And when somebody leaves — theirs or yours — removing them removes them: the next enquiry does not go to an address nobody is watching.
-
Filter to one client without leaving the view you use for all of them.
-
Nothing is held silently, so a message we stopped can be read, released and explained.
-
Each decision lists the signals that fired and what each one weighed, which is what turns a support call into a one-line answer.
Onboarding without risk
Nothing about their mail changes
Dry run delivers everything, exactly as it does today, and records only what it would have held. The client sees no difference — attachments included: a CV, a drawing or a photo arrives attached to the forwarded mail the way it always did. You see a week of evidence you can show them before anything is switched on.
That evidence is the sales conversation. Not a claim about accuracy, but their own messages, from their own form, with the decisions written out. When they are convinced, you move the inbox to active. If they are cautious, mirror keeps delivering everything while the scoring continues to run.
How it is priced
Per client, not per message
A per-message bill punishes the client who gets targeted hardest, which is the client who needs this most. It also makes your own cost impossible to quote, because the number moves with something neither of you controls.
Humainbox costs the same for a client whatever amount of spam they get, so you can put a figure in a retainer and leave it there. €299 covers 25 client workspaces with 10 inboxes each; past that, tell us roughly how many clients you look after and we will work out a price.
What each client workspace gives you
Its own inboxes
One per form, so a leaked address never affects another client.
Its own thresholds
Loose, balanced or strict, chosen inbox by inbox for that client rather than for the average one.
Its own recipients
A named person or a team where every member gets a copy.
Its own record
Every message kept and readable, held or delivered.
Start with one client site
Pick the client who complains most, add an inbox, paste its address into their form and leave the inbox in dry run. You will know within a week whether this belongs in the rest of your portfolio, and the client will not have noticed a thing.