Guest stories · October 6, 2026 · 8 min read

A guest could not open our smart lock in Johor Bahru. We walked them through it on a video call and still got a bad review. Here is what we changed.

The check-in guide with photos went out days before arrival. The guest never opened it, stood at the door and could not get in. We talked them through the lock step by step on a video call, then a review arrived saying check-in was unclear, hard and exhausting - and we never replied to it. A real case from our 100-plus units in Johor Bahru and Desaru, what it cost, and the four rules we changed.

中文 → · Bahasa Melayu →

Short answer: when a guest is standing at the door and the smart lock will not open, nine times out of ten the lock is fine and the check-in instructions were never actually read. In this case we got the guest in by walking them through the lock on a video call. We still received a bad review, and we never replied to it. Looking back, both failures were ours: nothing in our process told us the guide had not been read, and nobody owned the review before the 30-day reply window closed. Below is what happened, what it cost, and the rules we changed.

This is the first article in our "real cases" series. The earlier pieces on problem guests and our three layers of defence and what we do in the first hour when guests exceed the headcount describe types and procedures. From here on, each article is one thing that actually happened, written as: what happened, what we did in the moment, what it cost, what rule changed. Guests stay anonymous; we leave out dates and building names.

What actually happened?

A party booked one of the condominium units we manage in Johor Bahru. As with every booking, the check-in guide went out before arrival: how to enter the building, how to register the car, where the lock is, how to key in the code, and the detail that trips most people - after the code, wait for the beep, then press the handle. Every step had a photo. The guest also completed eKYC before arrival (ID upload, face match), and the door code was only released after that.

On arrival day the guest stood at the door and the door would not open. By the time they called, they were already fed up. The colleague who answered ran through the usual questions: did you press the confirm key after the code, did the screen light up, did you hear the unlock sound, are you pushing the handle down or pulling it up. After a few rounds one thing was obvious: the guest had never opened the guide. Not misunderstood it. Never opened it.

What did we do in the moment?

Some things cannot be explained over a voice call. The colleague switched to a video call and asked the guest to point the camera at the lock, then led them through it: where to touch to wake the screen, how to key in the code, which key confirms, how many seconds after the beep to press the handle, which direction. Twice the guest paused too long with the screen lit, the lock went back to sleep, and they had to start over. Then the door opened.

From the first call to the open door took roughly half an hour. For that half hour the colleague did nothing else, and the guest stood in a corridor with their luggage.

At the time it felt resolved. The door was open, the guest was inside, and there were no more calls for the rest of the stay.

So why was there still a bad review?

A few days after checkout the review appeared on the platform. The gist: the instructions were not clear, check-in was hard, and the whole thing was exhausting.

The first reaction was to feel wronged. The guide was sent. The photos were there. The guest did not read them. But run it from the guest's side once: their experience really was "stood outside the door for half an hour". They will not remember what we sent. They remember being tired. A star rating measures how the guest felt, not who was right.

Then the second failure: we never replied to that review. Not a decision - it just slipped. Nobody owned it, and by the time anyone remembered, the reply window had closed. Airbnb gives hosts 30 days from publication to post a public response; after that the option is gone for good. Every future guest who opens that listing now sees a review that says check-in was hard, with nothing underneath it.

What did this actually cost?

Laying the account out is more useful than the review on its own:

ItemActual cost
Staff timeAbout half an hour on the phone and video, plus the conversation with the owner afterwards
Guest timeAbout half an hour in the corridor with luggage
ReviewOne public negative review, of the most damaging kind for a self check-in unit: "check-in was hard"
Right of replyA 30-day window missed, which reads as agreeing with the review
Owner confidenceThe owner sees the review and asks "I thought you had a process" - that takes time to repair
The lockZero. The hardware worked perfectly

That last row is the point. The only thing that worked as designed was the hardware. One US self check-in guide puts it bluntly: when self check-in fails, hardware is about a fifth of the problem and instructions are the rest. We were the rest.

Why does "we sent it" not mean "they got it"?

In hindsight we had been treating "sent" as "done". Between booking and arrival a guest's phone receives the platform confirmation, the payment notice, our guide, the building's parking form and their own travel plans. A long message with five photos getting swiped past is normal, not unusual.

The real problem was not that the guest did not read it. It was that nothing in our process could tell us they had not. eKYC done, code released, process over. There was no "I have read this" step anywhere. So at the door, we discovered the guide had gone unread at the same moment the guest did.

This is also why this guest was not, strictly, a problem guest. No damage, no extra heads, no refusing to leave. They just did not read a message - and we had the chance to know that before they left home.

Which four rules did we change?

  1. The code is no longer "sent", it is released after confirmed reading. After eKYC, the guest sees a one-screen summary of the check-in essentials (where the lock is, how to key in, how long to wait) and has to tap "I've read this" before the door code appears. One extra tap buys us a signal we can see: who tapped, who has not, and when. Anyone who has not tapped a few hours before check-in gets a phone call from us.
  2. The guide now has a 30-second video version. The photo guide stays, and a short phone video goes alongside it: walk up, wake the screen, key in, beep, handle, one take. The video call was effectively us filming this live. Filming it a day earlier would have saved the half hour.
  3. A guest stuck at the door gets eyes on the problem within 15 minutes. Five minutes of guessing on a voice call and no door: switch to video, stop guessing. A guest outside for more than 15 minutes has already written the review in their head; a perfect stay afterwards does not undo it.
  4. Every review gets a reply within 30 days, and no bad review gets a reply within 24 hours. A review response is not customer service; it is written for the next guest. So the rule is: a bad review appears, let it sit for a day, then one named person replies publicly inside the 30-day window. The owner of that task and the deadline are written on the booking itself.

If we could reply to that review now, what would we say?

The window has closed, so this is the only place it can go. Not a template - what we would actually say:

Thank you for the feedback, and we are sorry you were left waiting at the door for so long. We did send the check-in guide before your arrival, but it clearly did not reach you in a way that worked, and that is on us, not you. The lock instructions now have to be confirmed as read before the code is released, and there is a 30-second video of the door being opened. Our colleague staying on a video call with you until the door opened is something we will keep doing - the goal is that nobody needs it.

Three things matter in it: apologise before explaining; say exactly what changed, because the reply is for the next guest; and never push it back onto the guest - "you didn't read it" in a public reply only makes the reader side with the guest.

What should an owner take from this?

If you manage your own unit, ask yourself one question: how do you know a guest has read your check-in guide? If the answer is "I sent it", you are where we were before this happened.

If you are considering handing a Johor Bahru or Desaru unit to a management company, use this article as the interview: a guest cannot open the lock - how many minutes until someone is on video with them? Is there a confirmed-read step before the code goes out? Who replies to bad reviews, and within how many days? The last one you did not reply to - what happened afterwards? A company willing to write up its own misses tends to be the one that closes the gap before the next time. If you want to see what our check-in flow looks like now, tell us about your unit and we will show you the exact screens a guest sees.

This article describes our own operating practice and the handling of one real incident; guest details have been anonymised. Review and reply rules are set by each platform and may change - check the current terms.

This is how we protect an owner's unit

Every rule in these stories exists because something went wrong once. If you want that experience managing your unit, talk to us.

Talk to us about your unit