Match contact options to how you actually work
A contact page is an operational promise. If you cannot answer calls while working on site, do not make “Call for immediate help” its central message. Our recommendation is to choose the route you can monitor reliably, then explain when someone should use the alternative. A phone number, email address and short form can coexist without competing equally for attention.
Display important contact details as text as well as links. MDN documents telephone links using tel: and email links using mailto:, with behaviour depending on the device and available applications. Ask your developer to implement them appropriately. Then try them on a phone and a desktop; a correctly displayed number can still link to an old number.
Prevent the most common wrong enquiries
State the service area and any appointment-only arrangement before the form. For a business that travels to customers, explain that clearly instead of encouraging visits to a private address. For a customer-facing location, provide accurate access or parking information where it helps. Do not publish a map pin that implies a staffed office you do not operate.
Illustrative contact introduction: “Tell us about your window-cleaning job in San Jose or the nearby areas listed below. We review messages on weekdays and reply using your selected contact method. If your property is outside the listed area, include the ZIP code so we can check.” Replace this sample with your actual area, schedule and response practice.
Make submission and follow-up unambiguous
A form should not leave the visitor wondering whether it worked. W3C recommends clear feedback about successful submission and errors. Show a readable confirmation that distinguishes a received enquiry from a confirmed appointment. If a request requires manual review, say so. Avoid “You’re booked!” when nobody has checked the calendar or accepted the job.
Write the confirmation before building the form. Our example: “Thanks, your enquiry has been sent. We’ll review the details and reply by email. Your appointment is not yet confirmed.” Add a realistic response window only if you can maintain it. If you send an automated email, check that the reply address reaches a monitored inbox.
Test the whole journey, including the inbox
Submit a clearly marked test enquiry with a real email address you control. Check the visible confirmation, the notification received by the business and any reply sent to the visitor. Look at the information as the person handling the enquiry would see it. Is the service identifiable? Can they reply directly? Is the customer’s preferred contact method obvious?
Repeat after changes to forms, email providers or website software. Assign one person to review submissions and one backup for absences. An attractive contact page with unmonitored notifications is unfinished. Keep a simple record of the last successful test, the receiving inbox and who owns the response, so the process survives staff changes.
Your practical checklist
- Show real, current contact details.
- State service area and visit arrangements.
- Describe when and how you respond.
- Distinguish enquiries from confirmed bookings.
- Test delivery and replies with a real submission.
- Assign a primary responder and backup.
Written with AI-assisted research and drafting, with source checks and editorial review for this guidebook. Platform facts link to official documentation. Examples and recommendations are our own; no client results are implied. Sources reviewed October 8, 2026. About Getting Found Local