Home/Notes/A practical look at booking forms for a plant nursery
A practical look at booking forms for a plant nursery
10 Feb 2024
How a plant nursery deals with booking forms — and what usually goes wrong.
The problem: a mailbox that still points at the old host. This breaks booking forms for a plant nursery.
A static site for a plant nursery does not need a CDN, a build pipeline, or a container. It needs correct booking forms and a host that stays online.
Email deliverability is nobody’s favourite topic, but a plant nursery lost two bookings because booking forms was misconfigured and replies landed in spam for a week.
The real issue was not booking forms itself — it was a mailbox that still points at the old host. One feeds the other, and fixing only the visible symptom means it comes back in three weeks.
The vendor portal had silently rotated the key for booking forms, but a plant nursery was still using the old one. Every outbound message bounced quietly.
A form that collects data for a plant nursery should say where the message goes. Nine fields and a captcha on a quiet Tuesday will cost you the person who actually wanted to pay.
Instead of migrating booking forms all at once, we ran both configurations in parallel for a week. The switch happened on a Wednesday morning — the quietest traffic window.
A phishing page copying a plant nursery appeared last year. The only reason their customers could tell it apart was that booking forms was set up correctly on the real site.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com