The First Hour of a Power Outage: A Script for a Remote Host

You won't be there. What you can control is how fast the first hour moves and who's holding which task.

Last updated: September 29, 2026

The lights go out and you find out from a message, not a screen. Nobody alerts you. A guest types "the power's gone" at eleven at night, and everything that follows depends on how the next sixty minutes are run. You can't reset a breaker from another country. You can decide who gets called, in what order, and what the guest hears while you're still guessing. That's the part this article builds for you.

Key Takeaways

• The repair isn't yours. The first hour is. A qualified tradesperson fixes the fault; you run the sequence that gets them there.
• Order the calls by what each one unlocks. The person with eyes on the property goes first, because everyone after them needs their answer.
• Send one holding message, not five. A single note with a time for the next update beats a stream of guesses.
• Never promise a repair time you weren't given. You'll be the one who breaks it.
• Write the script while it's calm. A script invented at midnight is panic with extra steps.

Why the first hour decides the rest of the outage

Most of the harm in a bad outage isn't the dark. It's the silence. A guest sitting in a dark room with no word from you starts making their own decisions. They ring around, they look for a hotel, they write the review in their head. By the time you've found an electrician, they've already rewritten the night.

The first hour is also the only stretch where you still have choices. Early on, you can move the guest, call in a favour, or ask them to sit tight for twenty minutes because the fix is close. An hour later, those options have mostly closed. The guest has either settled or given up, and a tradesperson you kept waiting has moved on to someone else.

So the aim isn't to solve the outage in the first hour. It's to make the first hour count. That means three calls and one message, in a fixed order.

None of this is about being the perfect host in a crisis. It's about removing the two things that make an outage worse: the guest guessing, and you improvising. Take both out, and a bad night stays a bad night instead of becoming the story a guest retells for months.

The three calls, in the order that saves the most time

Call one goes to whoever can put eyes on the property: your cleaner, your co-host, a neighbour with a key, the building manager. Their job isn't to fix anything. It's to answer one question — is this just your unit, or is the whole building dark? That single answer changes everything after it. A building-wide outage is a waiting game. A single-unit fault is a repair job.

Call two goes to the tradesperson, but only once you know which kind of problem you have. If it's your unit, you want an electrician. If it's the building, you want whoever maintains the shared supply, and there's nothing for an electrician to do. Ringing the wrong one first is the most common way hosts lose forty minutes.

Call three goes to the guest, and it's shorter than people expect. You aren't confirming a fix. You're confirming three things: that you know, that someone is on it, and when they'll hear from you again. If your guest wrote in a language you don't read well at speed, don't guess at a reply — a half-understood message just stacks a second problem on top of the first.

There's a fourth decision that's easy to skip: who's allowed to do what once someone is on site. If the only person standing in your hallway can't authorise a callout, the whole chain stalls at the worst possible moment. Settle that in advance, not at the door.

What to send the guest while you are still finding out

The holding message has one job: buy you time without pretending you have the answer. It should carry three things. That you know. What you've already done. When they'll hear from you next.

Keep the promise small, then keep it. "I've got an electrician on the way and I'll update you in thirty minutes" is a promise you can hold. "It'll be fixed by midnight" isn't, and it hands the guest a grievance later. If you don't know the cause yet, say so plainly. Guests forgive a slow answer. They rarely forgive a confident one that turns out to be wrong.

Times are the hidden trap when you and the guest aren't in the same place. When you promise "thirty minutes", you might both be counting from different clocks. Reading the thread back with its timestamps tied to the property's own time zone keeps the trail straight — you can see what was said at what hour without doing the arithmetic in your head. That's what the store's time-zone setting does at localsbnb.com: it keeps every time anchored where the property is, not where you happen to be sitting.

Keep the exchange in one place, too. If half the conversation happens in the platform inbox and half over a phone call nobody logged, you'll end up with two versions of the night when it's time to explain one.

Writing the script down before you ever need it

A script is worth having because it runs on reflex instead of judgement. Write it on one page, while the lights are on. Four lines: who's on site, who fixes what, what the guest gets told, and who may authorise spending.

Then give the same page to your on-site contact, so you're both reading from one version. If that person is a co-host or a cleaner rather than you, they'll need access to a few things and no more than that. Grant access by the area they actually work in — the calendar, the guest thread — rather than by handing over a general login. It's tidier in the calm weeks and far safer in the messy ones.

Two more details belong on the page. The first is that your credentials stay with you, on your own machine, instead of being passed around a group chat. The second is that your guest's personal details don't need to be visible to everyone in the chain. The name, the phone number and the ID are masked, so your on-site contact can do the job without holding more of the guest's information than the job needs. That's how access is built in the product, and it's also simply good practice.

One more reason to write it down: the morning after, you'll want to know the order things actually happened in. A script written in advance gives you the plan to hold the night up against.

FAQ

Should I promise the guest a repair time?

No. Promise a time for your next update instead. A repair time depends on a fault nobody has seen yet, and every minute it slips makes you look worse, not the electrician.

Whose job is it to report a building-wide outage?

Whoever maintains the shared supply, which is usually not you. If the whole building is dark, your task is to confirm that and pass it on, not to chase a fault that isn't on your side of the meter.

What if the outage only affects my unit?

Then it's a repair, and the clock starts with finding an electrician who'll come out at that hour. Your on-site contact should be ready to let them in, and your guest should already have the holding message.

The narrow aim of all this: three calls, one message, one page written in advance. You won't be there when the lights go out, and that's fine. What matters is that the first hour runs on a plan instead of an improvisation, and that your guest hears something true before they start filling the silence themselves. If you'd rather the thread and its timestamps sat where the property actually is, localsbnb.com anchors them to the store's own time zone, so the record reads the same way to everyone who opens it.

---

This article is general guidance for hosts, and it isn't legal, safety or insurance advice. Emergency and utility procedures, and who may authorise repairs, are set locally and change over time; check the current requirements of your local authority and the current terms of any platform you use.