Skip to content
Lines open
Map my coverage

Call operations

Create a message-taking checklist for a caller reporting a facility outage

A message checklist for facility outage calls, covering location, safety, affected systems, access, and a clear handoff to the on-call owner.

Create a message-taking checklist for a caller reporting a facility outage
Table of contents

A facility outage call arrives with urgency and very little structure. The caller may be a tenant, a staff member, or a passer-by, and each one describes the problem differently. The agent has minutes to capture facts that a technician will rely on later. A fixed checklist turns a panicked description into a message the on-call owner can act on.

Key takeaways

  • Confirm the exact site and building before anything else.
  • Ask about immediate safety hazards first.
  • Separate what is out from what is still working.
  • Record access details, contacts, and any site rules.
  • Read the message back and state who will respond.

Start with the location

Ask for the full address and the building name before the details of the outage. Many organizations have several sites with similar names, and a vague location wastes the first response. Confirm the unit, floor, or suite when the site has more than one. A precise location is the one detail that cannot be reconstructed later.

Check whether the caller is on site or reporting from somewhere else. A remote caller may have fewer facts and a different sense of urgency. Note the difference so the technician knows what to expect. It also tells the agent which follow-up questions are worth asking.

Ask how the caller is connected to the site. A tenant, a cleaner, and a delivery driver all have different access and different authority. The relationship shapes how much the caller can authorize. Record it in the caller's own words where possible.

Ask about safety first

Ask whether anyone is in danger before asking about equipment. Fire, smoke, flooding, and live wires change the response from a repair to an evacuation. If the answer is yes, direct the caller to emergency services first. The message can wait until people are safe.

Ask whether the hazard is contained or spreading. A small leak in a utility room is different from water moving toward electrical panels. The caller may not know the cause, so ask what they can see and hear. Record observations, not guesses.

Warn the caller not to touch damaged equipment. This is especially important for electrical panels, exposed wiring, and standing water near outlets. The agent should not talk a caller through a repair. The role is to collect facts and route them quickly.

Separate what is out from what works

List the systems that have failed and the systems that still run. Power, water, heat, internet, and phone lines are common categories. A partial outage is often easier to diagnose than a total one. The contrast between working and failed systems is a useful clue.

Ask when the problem started and whether anything changed just before it. A new piece of equipment, a storm, or a scheduled works project may explain the timing. Record the time as the caller reports it and mark it as an estimate. Do not correct the caller's clock.

Ask whether the outage has happened before. A repeat fault points to a known weak point, while a first fault may need a broader inspection. Note any prior ticket number the caller mentions. That reference can save the technician a search.

Capture access and contacts

Record how the technician will get in. A keyholder, a code, a loading dock, or a staffed front desk all change the plan. Ask for the name and number of the person who will meet the technician. Confirm that the person knows the visit is coming.

Ask for the site's access rules and any safety requirements. Some buildings need a sign-in, a permit, or a lift booking before work can start. A technician who arrives unprepared loses time at the door. The after-hours callback check covers the same discipline for night calls.

Note who else needs to know about the outage. A building manager, a safety officer, or a tenant group may need an update. Add them to the message as recipients, not as decision makers. This keeps the handoff clean.

Set the response expectation

Say who will respond and through which channel. A named on-call owner with a phone number is clearer than a vague promise that someone will come. Tell the caller what to do if the situation gets worse. Give the emergency number and the conditions that justify using it. The caller should leave the call knowing exactly who is on the way.

Give a response window that the team has agreed to. A window of "within the hour" is useful only if the team can keep it. Record the window in the message and repeat it to the caller. The outage triage study shows how to set thresholds that match capacity.

Do not promise a repair time. The agent cannot know the cause or the parts needed. Promise a response, not a fix. That distinction protects the caller from a second disappointment.

Read back and hand off

Read the location, the hazard, the failed systems, and the contact back to the caller. Ask them to correct anything that is wrong. A short readback catches most errors while the caller is still on the line. It also confirms that the agent listened.

Send the message to the on-call owner through the agreed channel. Mark the urgency using the checklist's own scale so the owner can sort it quickly. Attach the caller's number and the site contact. Do not bury the hazard below the equipment list.

Log the time the message was sent and the time it was acknowledged. An unacknowledged message needs a follow-up call. The emergency callback verification guide explains how to confirm receipt without alarming the caller. Close the loop only when the owner has the facts.

Sources

Map the first queue

GIVE MISSED CALLS A WAY BACK IN.

Share your call types, hours, tools, and escalation rules. We will turn them into a practical coverage plan with a clear first week.

Book a free consultation ↗See the call lanes