How We Put an Age-Checked Contact Form on a Dispensary Site in an Afternoon.

Sales are underway for the first CBD drug approved by the U.S. Food and Drug Administration. The drug, Epidiolex, treats two rare types of epilepsy and is made from marijuana plants grown in the United Kingdom. The maker of the …

The two problems with a dispensary contact form

The first is reliability. A contact form that lives inside the site, wired to a plugin and a mail function, fails quietly. The button still clicks, the visitor still sees a thank-you, and the message goes nowhere. For a dispensary that is a month of lost patients who think they were ignored. The second is age. A cannabis site is expected to gate its interactions, and a contact form that anyone can submit, regardless of age, is a gap most owners never think about because the form came with the theme.

Step one: the form itself

We threw out the plugin and wrote a plain HTML form: a name field, an email field, a message box. No database, no server code on the site to break or patch. Plain markup cannot fail silently in the way a plugin can, because there is no plugin in the loop to go stale when the theme updates.

Step two: the age gate

Before the form will submit, the visitor has to confirm they are of legal age, with a single required checkbox tied to the submit button and a short line of script that keeps the button disabled until it is ticked. It is deliberately simple. A heavy age-verification popup annoys real customers and rarely stops anyone determined, while a clear, required confirmation at the point of contact is honest, fast, and exactly the friction the situation calls for. The confirmation is recorded with the submission, so there is a record that it was asked.

Step three: where the message goes

This is the part that fixes the silent failure. Instead of relying on the site to send mail, the form posts to Formblade, a form backend that catches the submission off the site entirely. It lands in the dispensary's inbox and in a Slack channel the staff already watch, the moment it is sent. A message that fails to deliver is the backend's problem to flag, not a quiet hole in the site. Spam, the reason so many dispensary contact pages get ignored until they are abandoned, is filtered before anyone sees it.

Setup is genuinely a copy-and-paste job: create the form in the dashboard, copy the endpoint, point the form's action at it. Because the markup is ordinary, the same approach works whether the dispensary is on WordPress, Squarespace, or a hand-built static site, which matters when you are fixing someone else's stack rather than your own.

Step four: proof that it works

The step everyone skips. We sent a real test submission and watched it arrive in both the inbox and Slack, then checked that the age checkbox genuinely blocked submission when unticked. Five minutes that turn "it should work" into "it works." If you take nothing else from this, test your own contact form today by actually filling it in. A surprising number of them are quietly broken right now.

What to keep, and for how long

One thing worth deciding before you switch a dispensary form on is what you actually store, and for how long. A contact form does not need a customer's life history. A name, an email, the message, and the age confirmation are enough to reply and to show you asked. The less you keep, the less you have to protect, and the simpler your answer is when someone asks you to delete their data. A backend like Formblade that lets you export and delete records on request, and that ships the common privacy presets, turns that from a project into a setting. On a dispensary site, where regulatory attention already runs higher than average, holding only what you need is not just tidy, it is the safer default.

The same restraint pays off on mobile, where most of these inquiries actually come from. Every extra field is a reason to give up halfway, and a long form on a phone is a form that gets abandoned. Keep it to the few things that matter, make the age check one clear tap, and the people trying to reach you will actually finish.

The afternoon was the point

None of this needed a developer on call or a monthly plugin license. A plain form, one honest age check, and a backend that catches and forwards the message reliably. For a dispensary, the contact page is not a detail, it is the front desk, and a front desk that loses messages or waves through minors is worse than no front desk at all. The fix is small, it is cheap, and it took an afternoon. The month of lost inquiries before it is the part that was expensive.