Nobody's at the Desk: Building a Contact Page That Copes After Six
Photo: Gage Skidmore from Surprise, AZ, United States of America, CC BY-SA 2.0, via Wikimedia Commons
It's 21:40 on a Tuesday in November. Someone in Leeds has finally decided to deal with the damp patch in the back bedroom. They search, they find your firm, they fill in the form, they hit send, they get a thin grey auto-reply, and then — nothing. At 10:15 the next morning your office manager opens the shared inbox. By then the person has already booked someone else.
The website did its job. The gap between the website and a human is what lost the work.
The nine-to-five assumption
Most UK SMEs still think of their site the way they think of a shopfront: shutters up at nine, down at five, closed Sundays. But enquiries don't respect that. They arrive on Sunday evenings when the kids are in bed, on the bank holiday Monday when someone finally has a free day, in the odd dead week between Christmas and New Year when people redecorate out of boredom.
The pages that cope with this aren't dramatically different from yours. They're just set up on the assumption that nobody is watching.
Put the promise beside the button
Where the response-time line sits matters more than the exact wording. In the footer, nobody reads it. In the terms and conditions, definitely nobody reads it. Directly above or below the submit button, everyone reads it — because that's the last thing they see before they hand over their details.
One line, plainly written:
We answer every enquiry within one working day. Anything sent at the weekend is picked up on Monday morning.
Two rules. Don't write it if it isn't true. And don't write “we'll be in touch shortly”, which is a phrase that has never reassured a single human being in the history of the internet.
While you're there, check the form itself for structural rot: does it actually need a landline field? Does the postcode box reject a space? Is there a second, quieter route for someone who'd rather send an email than fill in six boxes?
Your confirmation email is a second landing page
Most auto-replies read like a receipt from a car park. They should read like the start of a service. A good one does five jobs:
- Repeats back what the person asked for, so they know it landed
- Says what happens next and when — “Kirsty will call you before 10am tomorrow”
- Names a human and gives a number they can actually ring
- Tells them what to have ready (photos, the postcode, access notes, the boiler make)
- Explains what to do if it turns out to be urgent
That last point is the one people forget. If a burst pipe at 23:00 lands in an inbox that isn't checked until nine, the honest thing is to say so on the page — and to offer an emergency route if you have one. “Out of hours, call this number. Call-out rates apply” is a far better outcome than an unanswered form.
Opening hours that machines can read
Search engines and AI assistants are now fairly confident about when things are open, and they will happily be confidently wrong. Your hours need to exist as structured data, not just as a paragraph or — worse — as a JPEG of a sign above the door.
Add openingHoursSpecification to your LocalBusiness JSON-LD. Use specialOpeningHoursSpecification for the ones that break the pattern: bank holidays, Christmas closing, the two weeks in August when you're on a site in Cornwall. Keep the markup identical to your Google Business Profile, because the two get compared, and mismatches get resolved in the direction you least want.
A few specifics worth getting right:
- “24/7” is only accurate if someone picks up. Otherwise say “emergency line 24/7, office hours Monday to Friday”.
- If you're appointment-only, say so in the markup, not just in the copy.
- Don't list hours you don't keep. An hour of padding is an hour of someone standing in your reception area.
Capture that doesn't need a desk
Four small structural choices do most of the work here.
Give the form a second channel. A phone number that goes to voicemail is fine, provided the voicemail message states when the call will be returned. A beep is not fine.
Offer a callback slot. “Choose a time tomorrow and we'll ring you then” outperforms “we'll be in touch” because it converts an open question into a booked one. Even a simple two-option field — morning or afternoon — helps.
Make the form fail loudly. Test it quarterly with a deliberately broken address and confirm that the notification reaches a human, that the thank-you page fires, and that the mail isn't quietly sitting in a spam folder. Silent form failure is one of the most common and most expensive faults on a small business site.
Audit your chat widget. If it's live only between nine and five, put that in the widget. A chat box that swallows a 21:00 message and never replies is worse than having no chat box at all.
A twenty-minute audit for your contact page
Open the page on your phone, at home, in the evening, and work through this:
- Is there a response-time promise next to the submit button, and is it accurate?
- Does the confirmation email arrive within two minutes, and does it name a human?
- Does the confirmation explain weekends and bank holidays?
- Are your hours in structured data as well as in text?
- Do the hours match your Google Business Profile exactly?
- Does the form reach a real inbox, tested this quarter?
- Does the phone number lead somewhere with a useful message?
- Is there an out-of-hours route for genuinely urgent work?
The night shift isn't glamorous. It's a line of copy, a confirmation email that does a bit more than acknowledge, and machine-readable opening hours. But it's the difference between a site that collects interest and a site that converts it before your competitors open their laptops.