A mailto: link looks simple until mobile mail apps fail and spam filters eat the result. Use a form with name, email, subject, and message so ‘email us’ still works on a static US or UK site without exposing the address.
Notifications can mirror the old inbox.
That is the email-form difference.
Same visible label, better capture.
The dashboard is storage, not your only reply path.
An email form is the public way to send a message that would otherwise be a composed mail. Subject and body are first-class fields, which is why the contact pack fits: you get a thread title instead of a blank. US and UK visitors both bounce when a tap-to-mail link opens the wrong app or nothing at all.
You still receive an email notification if you want. The difference is the row also lives in a dashboard with spam filtering, so the address on the site is not a magnet for harvested hello@ scrapes.
Subject-less messages become ‘misc’ and die.
Put the team’s public address in the footer if legal or press still need it; keep this form as the default CTA.
Chat is not email. Some visitors want a record they composed.
Works on GitHub Pages, Webflow, and WordPress HTML blocks.
Break on locked-down work laptops and many phones.
Rarely on-brand and still expose routing.
Overkill when you needed a subject and a body.
Documentation and brochure sites stay static on purpose. Publish the form where you used to put the address.
If you serve both markets, a ZIP or postcode in the message is optional context—do not require it on a simple email form.
No. It posts to your form backend. You get a notification; they stay on the page.
Configure notification routing in the product, not in HTML.
Add a file or URL field on the form if you must.
No. Use a signup pack page if you only wanted an email list.