It is 23:10. The guest has been in the flat for twenty minutes and has sent three messages. The first is a photo of the laminated card on the kitchen counter. The second says the password does not work. The third says they have tried it four times.
You are in another city. You do not know which network their phone is joined to, whether the router has any lights on, or whether that card has said the wrong thing since the ISP swapped the box in March. What you do know is that the guest has been holding a dead phone for twenty minutes, and that this is the first thing that has happened to them in your property.
WiFi is one of the two or three questions almost every host answers most often, alongside check-in and parking, and most of that volume is self-inflicted. It is not a hard technical problem. It is a set of small, fixable defects in how the network name and password travel from your router to a stranger's thumb. It is worth handling like any recurring operational fault rather than as trivia, which is true of most of the inbox: see the ten questions guests ask most and how to answer them at scale.
This article covers what actually goes wrong, which of those failures are yours and which belong to the building, and the fixes in order of leverage: the password first, because it is worth more than everything after it.
What Actually Goes Wrong
"The WiFi is not working" is not one problem. It is at least six, and they have different causes, different fixes, and different people who can perform the fix. Separating them is the whole job.
| What the guest says | What it usually is | Who can fix it | Fixable from your phone |
|---|---|---|---|
| "The password doesn't work" | A character the guest cannot read on a printed card, or a card printed before the last router change | You, before they arrive | Yes |
| "I can't find the network" | The card names a network the router no longer broadcasts, or names one band of two | You, before they arrive | Yes |
| "It's connected but there's no internet" | The phone joined a neighbour's open network, or an old extender with nothing behind it | The guest, with one instruction | Yes |
| "It works in the kitchen, not the bedroom" | A mesh node unplugged by the last guest, or a genuine dead spot | Someone standing in the building | No |
| "There are no lights on the box" | The socket was switched off, or the router has died | Someone standing in the building | No |
| "Lights are on but nothing loads" | An ISP or building fibre outage | The provider | No |
The top three rows are information failures. They are yours, they are cheap to eliminate, and they account for most of the messages. The bottom three are physical failures. No message you send resolves them, and any advice that suggests otherwise is selling you something.
The Password Is the Highest-Leverage Thing You Own
Change the password to something a guest can be told down a phone line and type correctly on the first attempt, and a large share of the problem disappears before it starts.
The test is dictation. If you cannot read it aloud to someone across a room and have them type it correctly, it is the wrong password. That rules out more than people expect. Lowercase l, capital I and the digit 1 are the same shape in most printed fonts. So are capital O and zero. So are 5 and S, and 8 and B, and r-n set close together, which reads as an m. A password containing any of those has a permanent, built-in error rate that has nothing to do with the guest's competence.
It also rules out anything that fights a phone keyboard. Characters that need a language-keyboard switch, a leading capital that autocapitalise turns into a lowercase letter or the reverse, and anything a predictive keyboard will try to correct. Length is what makes a passphrase hard to guess, not punctuation variety, so the sensible shape is three or four unambiguous lowercase words joined by hyphens with a couple of digits on the end. Something like blue-door-lisbon-24. Long, unambiguous, and dictatable to a tired guest at 23:10.
Rename the network at the same time. A guest standing in your flat should see which network is yours without checking anything. If the router broadcasts separate names for its two bands, either give them the same name where the router supports it, or name them so the one to try first is obvious. Router behaviour varies enough that the only reliable check is the admin page of the actual box in the actual property.
Changing the password has a real cost worth planning for rather than discovering. Every device already on that network has to rejoin: the TV, the streaming stick, the thermostat, the noise monitor, the lock bridge, the robot vacuum, whatever the owner left in the cupboard. Do it on a turnover day with slack in it, not on the morning of a check-in, and update every printed and digital copy in the same hour.
Three Places, and They Have to Agree
Once the password is right, the job is making sure the guest meets it before they have to ask. Three places is the working answer.
In the room, at eye level, where the guest already is. A card by the television or on the fridge door, not page eleven of a welcome binder in a drawer. Add a WPA QR code if you can generate one (many phone cameras will join a network directly from it), but print the text underneath anyway, because not every phone and not every guest will use it.
In the digital house manual. This is the copy you can correct in thirty seconds from a train, which makes it the one that should be canonical. It is also where the rest of the property's answers should live, for the same reason: a house manual that actually reduces guest messages earns its keep on exactly this kind of repeated question.
In the messaging thread the guest is already using. Not as a screenshot and not as a PDF attachment. As plain text, so the guest can press and hold, copy, and paste it straight into the network prompt. A copied password cannot be mistyped, which removes the entire character-ambiguity problem for the guests who use it.
The failure here is almost never having too few places. It is having three places that disagree. The card says one thing, the listing description says another, and the guidebook was updated but the card was not. Pick the digital copy as the source of truth, and when the password changes, change all three before you close the laptop. Photograph the new card after you print it, so you have a record of what the property actually says.
Put It in the Arrival Message
The message that carries the door code should carry the network name and the password, in that order, as plain copyable text. That single change removes more WiFi messages than any physical signage, because it puts the answer in the guest's own phone, in a thread they can search, before they have walked through the door.
Send it twice: once with the check-in instructions, and again on arrival day. The arrival-day copy is the one that matters, because it is the one still visible when the guest is standing in the hallway with a suitcase. If you are already automating that sequence, this is a one-line addition to it: the mechanics of the arrival message are covered in automating check-in instructions over WhatsApp.
Say the network name explicitly, and say it exactly as the router broadcasts it, including capitals and hyphens. "The network is CasaVerde" is useful. "Connect to the house WiFi" is not, in a building where the guest can see fourteen networks.
The Diagnostic Ladder for When It Genuinely Does Not Work
For the guests who still cannot connect, you need a sequence that starts with the cheapest question and stops as soon as it hits a physical cause. Written in advance, per property, this can run without you.
- Which network is the phone actually joined to? Ask for a screenshot of the WiFi settings screen. This one question resolves a surprising share of cases, because the phone has quietly joined the neighbour's open network, or an extender with nothing behind it, or is on mobile data and the guest has not noticed.
- One device or all of them? One phone failing while the rest of the party is online is a device problem, and the fix is on that device. Everyone failing is a property problem.
- No connection at all, or connected with no internet? These are different diagnoses. The first is a password or a band problem. The second is upstream: the router has the network up and the line down.
- Forget the network, rejoin, and type the password rather than pasting it. A pasted password often carries a trailing space, and a typed one exposes a keyboard that has been autocorrecting.
- Power cycle the router. This only works if the guest can find it. That means a photo of the router in place in that specific property, with the plug identified, and a stated wait: thirty seconds off, then two to three minutes for the line to come back. Without the photo, this step fails every time.
- Read the lights. What each light state means differs by box, so it has to be written down per property in advance. Once it is, the guest can tell you whether the line is down without either of you guessing.
- Stop. If the lights say there is no service, no further instruction helps.
The ladder is worth building the same way you would build any symptom-first troubleshooting library: lead with the most likely cause, offer the second only if the first fails, and escalate rather than looping. The method is the same one described in appliance troubleshooting for vacation rental guests, and the assets it needs are the same: photographs, taken once, of the actual equipment in the actual property.
The Outage That Is Not Your Fault
A contractor puts a digger through the duct. The provider has a regional fault. The building's fibre is down and the management company will get to it on Monday. None of this is your doing, and all of it is your problem, because the guest booked a flat with WiFi.
What you control is the speed and the honesty of the response, and then the mitigation. Tell the guest plainly that the line is down, that it is a building or provider fault, and what you know about when it will be back (including saying that you do not know, if the provider publishes nothing). Then offer something concrete: a mobile data top-up you will reimburse, the name of a café nearby with sockets and a working connection, and, for a guest who is clearly working from the flat, an honest conversation about the booking.
Most of the review damage from an outage comes from the silence around it rather than the outage, which is the general principle behind guest experience automation: get the true state of things to the guest quickly, rather than managing the fault first and the guest second. A guest told at 20:05 that the building is down, and handed a data top-up, writes a different review than a guest who messaged at 20:05 and heard nothing until 21:30. If you let a property to remote workers, a 4G failover router in the cupboard is the only real fix, and it is a per-property hardware purchase you should make deliberately rather than after the first bad review.
Honest Limits
Most of this article eliminates information failures, and it is good at that. It is worth being exact about what is left over.
You cannot fix a provider outage from your phone. No password hygiene, no guidebook, and no assistant changes that. The line is down until someone in a van fixes it.
A mesh dead spot needs someone in the building. If the bedroom node was unplugged by a guest who wanted the socket for a phone charger, the only resolution is a person walking into that room. The most a messaging system can do is identify it quickly enough that you send the right person once rather than exchanging six messages first.
A dead router is a hardware failure. Nothing in a conversation resolves it. What a good system changes is the hour the guest would otherwise spend discovering that: the difference between a guest who knows within four minutes that someone is coming with a replacement and a guest who tries the password thirty times and then writes the review.
Password hygiene has a ceiling. Once the password is dictatable and the three copies agree, you have removed the volume that was yours to remove. What remains is physical, and the honest budget line for it is a callout, not a better message.
Be sceptical of anything that claims to eliminate WiFi questions, including Welco. An assistant answers from what you load into it. If what you loaded is the password from before the router was replaced, it will tell every guest the wrong thing: faster, more confidently, and in more languages than you ever could. A wrong answer delivered at scale is worse than a slow right one, and keeping the source current is an obligation that stays with you.
Where Welco Fits
Welco is a WhatsApp AI assistant for vacation rental hosts. On this problem it does the unglamorous half: a verified guest asks about the WiFi in their own language, gets the network name and password you loaded, and is walked down the diagnostic ladder you wrote, at 23:10, without waiting for you. When the ladder reaches a physical cause, it flags the escalation to you with an urgency level rather than pretending it can fix a dead line.
It syncs reservations by iCal from Airbnb, Booking.com, VRBO or Hostaway, so it knows who is in the property without a PMS behind it. Access today is by demo request, and the honest way to evaluate it is to load your real network details into the simulator and see what it says before a guest ever does.