What belongs on a contact page, and what suppresses calls

A tel: phone number above the form, because the urgent buyer does not fill in forms. The service area, stated, because do-you-come-here is the first question. Hours, including whether out-of-hours reaches anyone. The address, if you have premises, or an explicit service-area statement if you do not. A form asking only what the job needs, because every field is a chance to stop. Labeled, keyboard-reachable fields. And what happens next, and when.

The address item has a profile consequence: if you travel to customers rather than receiving them, Google's service-area business guidance covers that case, and a service-area business does not display a street address.

Labels are not a compliance aside. The success criteria are in the WCAG 2.2 quick reference, and a form a screen reader cannot label is a form some of your buyers cannot submit.

The form as the only path. It excludes the buyer with an emergency, who in service work is often the most valuable one.

Fields the job does not need. Baymard's benchmark put the average checkout at 11.3 form fields in 2024 against the 8 it finds most sites need. A quote request is not a checkout and the number does not transfer; the direction does.

A required message box, which asks the visitor to compose rather than choose. No response expectation, because silence after submitting reads as a dead form. And a CAPTCHA the visitor fails — the leads it blocks are not all bots.