Five input fields on a contact page are worth less than one prefilled email draft.
The template we opened on 25 October had exactly that: five boxes, and a small note saying form collection was not enabled. A visitor could fill in a name, a company, a country, an email address and an application description, then find nothing to click.
One test decides whether a contact page works. A visitor clicks once, the message reaches your inbox, and it carries what you need to quote. Input boxes cannot fix a broken last step.
Three channels, and the backend question
| Channel | Prerequisite | Fits | Main risk |
|---|---|---|---|
| Web form | Inbox backend, spam control, alerts | High inquiry volume, structured fields | Without a backend it is decoration |
| Prefilled email | One mailbox that receives mail | Custom parts, low volume | Depends on the visitor's mail client |
| Messaging apps | Someone on duty | Southeast Asia, Middle East | Time zones slow replies; records scatter |
You can run all three. Order matters. Email first, messaging second, form last. The form is the only channel that needs development and maintenance.
Five boxes, zero messages
The field design was fine. Name, company and country, plus an email field and an application box. Nothing wrong with the questions.
The failure sat at the end. No submit button, no action attribute, no destination address. The internal note said the RFQ inbox was coming in a later gate, while the page already invited visitors to type.
The fix was blunt. Delete the five inputs, keep the email button, add a mailto link with the subject and body prefilled. The page states the situation: a secure form ships before launch, email works today.
Then we added a test. No input elements on the page, and the mailto link plus the draft block must both exist. Twenty-three related tests passed, and the fast gate ran 8 of 8 checks in 11 seconds.
Tests beat documents here. A document describes the intended stopgap. A test only accepts a page that actually has the link.
Seven lines in the email body
A prefilled draft decides what the visitor has to think about. An empty email is easy to postpone.
| Line | Content | Why it matters |
|---|---|---|
| 1 | Equipment type | Picks the product line for the quote |
| 2 | Supply voltage and load | Sets the relay and wiring options |
| 3 | Sequence of operation | Sets control logic complexity |
| 4 | Destination market | Sets certification and plug standards |
| 5 | Annual volume and launch window | Sets price band and scheduling |
| 6 | Connectivity | Decides whether a comms module is needed |
| 7 | Attachments | Drawings or a photo of the old unit |
Fill those seven lines and the first reply can carry a price range. Otherwise the quote takes three more rounds. Order the fields the way a quote needs them, not the way your company form has always been ordered.
Prefill the subject too. RFQ, equipment type, destination market. It sorts itself in the inbox.
Three hard rules for channel settings
- Email is mandatory. Other channels may be empty. The email field may not.
- WhatsApp accepts 7 to 15 digits. Strip plus signs and brackets before saving.
- QR codes accept a site-relative path or an https URL. External images break and slow the first screen.
Empty values must not render dead links. No WeCom ID configured means no WeCom row on the page. Put that in the renderer, not in an editor's memory.
One mailbox, two addresses on the page
The same day surfaced a quieter bug.
Someone changed the contact address in the admin panel, while the body copy still hardcoded the old one. The page showed two email addresses and no way to tell which was current.
The fix removed the address from the copy and pointed to the Direct contact block instead. One source of truth, set in the admin panel.
The build could not catch this. It checks dead links and required fields. It cannot see that both addresses resolve, and only one is current.
Five checks before publishing
- Click the email button. Your mail client opens with subject and body filled.
- Load the page offline. The address stays readable without JavaScript.
- At 375 pixels wide, the button does not wrap into two lines.
- Change the address in admin, refresh, and confirm one address site-wide.
- The page states which channel works today, without promising the form early.
All five, then publish.
Where this applies
This fits B2B custom parts, larger order values, and single-digit inquiries per day.
It does not fit two cases. At dozens of inquiries per day, email loses messages and you need a form plus a CRM. On a retail site, customers order directly and the contact page is only a support entrance.
Forms are not the problem. Shipping a form without a backend, and letting visitors fill it first, is.
FAQ
What if a phone has no mail app configured?
Most phones open their default mail app. A phone without an account cannot. Show the address as plain text next to the button so it can be copied.
Does email-only look unprofessional?
It depends on the buyer. Industrial buyers in Europe and North America work by email and will send a model number and parameters. Buyers in the Middle East and South America often prefer WhatsApp. Publishing both is fine. A week without a reply is not.
When is a form actually required?
When three conditions hold at once: more than ten inquiries a day, routing by field to different salespeople, and a spam control plan. With one missing, skip it.
Will a prefilled draft land in spam?
A subject with RFQ and the equipment type, plus specific parameters in the body, passes normal filters. Oversized attachments are the usual trigger. Send a link instead.
Should the contact page list a phone number?
For B2B, yes, with service hours and time zone stated. A number nobody answers damages trust more than no number.
Last updated: 2026-10-28