Contact forms that don't lose messages
The contact form is usually the least-loved page on a business site, and often the most valuable one: it is where a stranger becomes a customer. The industry standard treats it as fire-and-forget — validate a little, send an email, hope. On our platform every public form is store-first. Here is what that means, and why we refuse to build it any other way.
Email is a doorbell, not a filing cabinet
An email can bounce. It can land in spam, hit a full mailbox, or arrive while the one person reading that address is on holiday. None of this is exotic — mail is an asynchronous relay between machines nobody fully controls. But when the notification email IS the message, any of those mundane failures silently deletes a customer. And nobody notices, because:
A lost message looks exactly like a quiet week.
Store first, notify second
On a Clonext instance the order is fixed: every submission is validated by the engine and written to your application's own database first; only then does mail move. The notification is the doorbell — the record is already in the book. It arrives with Reply-To set to the visitor, so answering is one click in your mail client, and the visitor can receive a copy of their enquiry in their own language, whichever of the platform's twelve they wrote in. In the panel, the Inbox walks every message through new → seen → handled — with spam and archive, notes, and who handled it, when. If an email ever goes missing, the message doesn't.
What about spam?
Storing everything sounds like an invitation, so the defence is layered and deliberately quiet: an invisible honeypot most bots fall into, a per-address throttle — five submissions an hour — and reCAPTCHA only on the forms that warrant it. Humans don't solve puzzles by default. Privacy consent is recorded with the submission's timestamp, and when someone asks to be forgotten, one action anonymises their message while your statistics survive. Boring, in the best possible way: a complete, private record of every conversation your website ever started.
