Manual 2 · Your Website · 2.4
What a service page has to answer
for someone calling at a bad hour
The page a stranger reads with water on the floor
Picture the person on the other end of the next call. The water heater in their basement let go an hour ago. They've already shut the valve, and now they're standing there in socks, phone in hand, reading whatever your service page says.
They are not comparing craftsmanship. They are not admiring your logo. They are scanning, fast, for a short list of things: that you fix this, that you come to them, roughly what it runs, and a number that dials a real person.
Here's the short of it. A service page has one job, and it isn't to sound finished. Its job is to answer, in plain words, the questions somebody asks when something is broken.
Forget the word "ad." Think of it as a set of answers, left out on the table for a stranger having a bad hour, so they don't have to guess or dial three more numbers to find out.
Writing plainly about your own trade can feel like bragging. It isn't. Every line below is a thing you can answer in a sentence, and most of it is already true — you're filling in blanks, not staring at an empty screen.
Why a rushed reader won't dig for anything
Start with why the surface of the page matters more than the depth.
Researchers who study emergency buying — the sudden kind that locksmiths and plumbers live in — argue that when a need hits fast and the stakes feel real, people stop weighing options carefully and move toward whatever answer they can trust the quickest.
So most service pages don't fail by being boring. They fail because a person under pressure won't read past the first screen to find the one fact they came for. If the answer is buried, to them it isn't there.
That flips the whole job. Put the answers on the surface, in plain words, or a rushed reader treats your page like it said nothing at all.
The questions they arrive holding
They land on your page already holding a few questions. You don't get to pick which ones. Four show up on nearly every emergency call.
Do you fix this particular problem. Do you drive to where they actually live. Roughly what does a job like this cost. And how do they reach a real person right now.
The trap is thinking silence on any one of these reads as neutral. It doesn't. A gap doesn't leave them curious — it hands them the worst version of the answer, and they move on.
| The question they're holding | What they decide when the page won't say |
|---|---|
| Do you fix this exact problem? | You probably don't take this kind of call. |
| Do you come to where I live? | You don't cross town to my side. |
| Roughly what will it cost? | It's either too pricey to ask or too vague to trust. |
| How do I reach a person right now? | Faster to just call the next name on the list. |
Answer all four out loud and the page doesn't need to be clever. It needs to leave nothing for a scared brain to fill in wrong.
The number does two jobs at once
The phone number is the answer to "how do I reach you." It's also the plainest proof on the whole page that a real business stands behind it.
Two of the ten Stanford web-credibility guidelines land right here: a site reads as more believable when it shows a real outfit stands behind it — a real address and phone — and when it's easy to actually make contact. A number a stranger can dial beats a slick page that answers nothing.
Why a reachable number quiets a stranger's doubt, and the research under it, is its own page: what makes a stranger believe the page. Here it's enough to know the number answers the question and proves you're real in the same breath.
The form that quietly eats the message
If you take contact through a form instead of a call, one thing has to be true before anything else: the form has to actually deliver.
Google's GA4 recommended-events reference lists generate_lead as the event for a form submission or request for information — lead generation such as contact forms, demo requests, trials, bookings, and newsletter sign-ups. Best practice is to fire it on the confirmed success state (the thank-you/confirmation, not the button click), which keeps lead counts accurate.
The reason that matters here: forms fail silently, and a message that vanishes leaves no error and no trace. If your count only ticks up on the confirmation screen, a form that swallows the message never gets logged as a lead at all — which is exactly the warning sign you want.
Say the specific thing, skip the adjective
Somewhere out there is a service page with a "why choose us" block — reliable, professional, honest — that would sit just as well on the next outfit's site, because it names nothing only you could claim.
Try the test. Swap the company name at the top. If the paragraph still works, it was written to sound done, not to answer anything.
A vague adjective is filler. One real detail — the towns you actually drive to, what a repair like this runs, a number that rings through to a person — does more work than a whole paragraph of "quality" and "trust." Sounding polished does nothing. Saying the checkable thing does the work.
One example, filled all the way in
Here's the shape, worked out for one shop, so it's concrete before you write your own. Swap in your trade and your real numbers.
One shop's answers, filled in — a leaking water heater
"Water heater leaking or no hot water? We take those same day, and we answer nights and weekends."
"We work Springfield, Chatham, Rochester, and the towns between them."
"Most water-heater repairs run $150 to $400. A full replacement is more, and you'll get a firm number before we touch anything."
"Call or text 555-0100 — a real person picks up, not a machine."
Not one line in that is a slogan. Every line is a fact the caller could check by dialing the number. That's the bar for your own frames below: if a line can't be checked, it doesn't belong on the page.
Now write yours, one answer at a time
Four short blocks. Answer each for your own shop, in your own words. None of them needs more than a sentence or two.
Do you fix this, and when can you come?
"[The problem] — we [do / don't] take these after hours. If yes: [nights / weekends / holidays — name which]. Reach us now: [phone]."
Where do you actually drive?
"We work [the towns and neighborhoods you really cover], and everywhere between them. Outside that? [Say so plainly, or say you'll take the call and quote the drive]."
Roughly what does it run?
"A job like this usually runs [your real low-to-high range], depending on [the thing that actually moves the price]. You'll get a firm number before any work starts."
How do I reach a person right now?
"Call or text [phone] — [who actually answers: you, the office, whoever's nearest]. [If you keep a real response time, say it. If you don't, leave it out]."
A number you can't stand behind is worse than no number. The first promise you miss is the last one they believe.
What the words can't carry alone
The answers do the talking. Photos back them up — a real truck, a real job, proof the name on the page is the one who'll show up. That's its own short job, already written, with the five-shot list and the routine that gets the pictures onto your profile: the shot list.
And before any of this, they found your name somewhere — a neighbor, a search, a truck at a curb. What they do with that name, and what they're checking for the second they land, is its own page: where customers actually look. This page picks up where that one stops: they've arrived, and now it has to answer them.
Read it once as the person calling
Pull the page up and read it out loud, as if you were the one standing in water at a bad hour. Answer each line yes or no.
Add up the no's. Each is a question you've left a scared stranger to answer wrong — and each one you fix is one less reason for them to dial the next name.
A service page earns the call by answering plainly — what you fix, where you go, what it runs, how to reach you — and then getting out of the way so they can pick up the phone.
This page is free to use and share, like the whole manual.
If you'd rather hand the whole thing off, our prices are public