Emergency electrician inquiries: the page a caller reads in the dark

What the first screen has to carry

The person reading this page is in a dark hallway or a kitchen with the fridge gone quiet, on a phone with whatever battery is left, deciding whether to call you now. What they need to decide sits above the first scroll: the number, as text they can tap; whether it is answered right now, in words ("answered around the clock", or "answered until 10 p.m."); and who picks up. Everything else on the page explains those three lines.

Say who picks up, because the caller finds out within two rings anyway. It may be an electrician on call, the owner's own phone, or an answering service that takes the details and pages whoever is on call. Each is an honest arrangement, and each sets a different expectation for the next ten minutes. A caller who knows a service will call back waits for the call. One who expected an electrician and hears a script hangs up and tries the next number.

The overview for electricians covers the site as a whole. This page is the one for the night: an answer page for one kind of emergency inquiry, written for a reader who will open nothing else you publish.

Which calls you take tonight, and which wait until morning

Write this in your own words, the way your dispatcher says it on the phone, because it is your policy and nobody else's. We do not write the list for you. Which situations your shop treats as an emergency depends on your crew, your area and your judgment, and the reader deserves your answer rather than a general one. Three lines are enough:

We come out tonight for: [the calls your shop treats as emergencies, in your words].
These can wait until [time] tomorrow: [the calls that can wait].
Not sure which yours is? Call [night number] and [who answers] will tell you.

Do not skip the third line. A caller who cannot tell which list they are on should be told to call, not left to guess, and the person who answers is the one who sorts it. A page that says only "emergency service available" gives the reader nothing to sort with. It also gives an answer nothing to repeat when a homeowner asks an assistant whether your shop comes out tonight for a problem like theirs.

When the caller should phone the utility or emergency services first

Some calls at night are not yours to take first, and the page should say which, as your instruction to your own callers. Write it the way you would say it on the phone: for these situations, call the utility on this number; for these, call the emergency number; then call us. The situations are yours to name, from your own practice. We leave them in brackets on purpose, because a list written here would be safety advice, and safety advice about someone's home has to come from you, from the utility or from the emergency services where the caller lives.

Call [your utility's outage or emergency line, as the utility publishes it] instead of us for: [the situations you send to the utility].
Call [the emergency number where you work] first for: [the situations you send to emergency services].
When they are done, call us on [night number] and we will [what your shop does next].

Copy the utility's number and the emergency number exactly as each one publishes it, and check them whenever you check your own. A night page with an old outage number on it fails the caller at the one moment it was written for.

The night area can be smaller than the day area

A shop that drives forty minutes for a panel upgrade in daylight may not send anyone that far at 2 a.m., and it does not have to. Name the towns and neighborhoods you reach at night, as a list in text, on the emergency page. If the night list is shorter than the day list, say so in one sentence: "At night we cover [towns]; for the rest of our area, we come out from [time] in the morning."

That sentence protects both sides. A caller outside the night area learns it before dialing, and any answer built from your page has the right towns to repeat. Your Business Profile's service area stays the area you work in by day, which Google's guidelines say should not reach farther than about two hours of driving from your base. The shorter night list lives on the emergency page and, as the last section shows, in the markup, attached to the night line.

What a night call-out costs, and how fast you come

A caller at night wants the price before the truck arrives, so put it on the page before they dial. State what the call-out fee covers, what is charged after it, and when night rates begin and end. Every figure below is a placeholder; the numbers have to be yours, and they have to be the ones your dispatcher quotes.

A night call-out is [amount]. It covers [what it covers: the visit, the first hour].
After that, [rate] per [hour or half hour].
Night rates apply from [time] to [time], and on [the holidays you charge night rates on].
We aim to reach you within [range] in [inner towns] and [range] in [outer towns].
[If you cannot come tonight: what you tell the caller, and whether anything is charged.]

Give the response time as a range you would stand behind on a bad night, not the best time you have ever made. A range by zone is honest where a single figure is not: the town you work from is minutes away, and the edge of your night area is not. If the range stretches in a storm, add a line saying so, and take it down when the storm has passed.

One set of night facts, in three places

The page, your Google Business Profile and your markup should say the same thing about nights, in the same words where they can. Google's Business Profile guidelines ask for your regular customer-facing hours, with special hours for particular days such as holidays, and Google's page on AI features lists up-to-date Business Profile information among its best practices. Agreement is harder than it sounds: in our audit of 9,483 small business websites (40 trades, 90 metros, late August to early September 2026), 43.1% were inconsistent about who and where they are across their own three main pages, before any profile was compared with them. That figure is sample-wide; we publish no electrician-only cut.

On the profile, we would set the hours to open 24 hours only when a person who can send an electrician answers at every hour. If nights go to voicemail, or to a message service that calls back in the morning, list the hours a person does answer and let the emergency page explain the rest. Set special hours for holidays before they arrive, and change the site on the same day. The same guidelines say a business that operates only by appointment should not provide hours at all, which is worth reading if your shop books every job ahead and keeps no line open for calls.

The markup has a place for each of those facts. Electrician is one of schema.org's LocalBusiness subtypes, and its node carries the business's hours in openingHoursSpecification and holiday hours in specialOpeningHoursSpecification. The night line can be a contactPoint of its own, with its telephone, the night towns in areaServed, and hoursAvailable for the hours it is answered. schema.org's OpeningHoursSpecification gives each set of hours its days, an opening time and a closing time, and it reads a closing time earlier than the opening time as running into the next day, so a line answered from 17:00 to 07:00 is one entry, not two.

{
  "@context": "https://schema.org",
  "@type": "Electrician",
  "@id": "https://www.example.com/#business",
  "name": "[Business name]",
  "url": "https://www.example.com/",
  "telephone": "[office number]",
  "areaServed": ["[day town]", "[day town]", "[day town]"],
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "[07:00]",
    "closes": "[17:00]"
  }],
  "specialOpeningHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "validFrom": "[holiday date]",
    "validThrough": "[holiday date]",
    "opens": "[09:00]",
    "closes": "[13:00]"
  }],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "emergency call-out",
    "telephone": "[night number]",
    "areaServed": ["[night town]", "[night town]"],
    "hoursAvailable": [{
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"],
      "opens": "[17:00]",
      "closes": "[07:00]"
    }, {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Saturday", "Sunday"],
      "opens": "[07:00]",
      "closes": "[17:00]"
    }]
  }
}

The template shows one shape: an office open on weekdays, and a night line that answers whenever the office is closed, every evening until the next morning and through the day at weekends. If one number answers at every hour, it is both the telephone and the night line, and the page should say so. Whatever the shape, nothing goes into the JSON-LD that a visitor cannot read on the emergency page itself, which is the rule in Google's introduction to structured data. The price and the response range stay in the text. And none of it makes anything appear: Google's general structured data guidelines say that even correct markup is no guarantee of showing up in search results. Whether the answers then give the right number is the check set out in AI visibility for electricians.