The short answer: you cannot stop problem guests from existing, but you can make them pay for what they do and make sure they cannot book you again. Across 100-plus units in Johor Bahru and Desaru we now run three layers: a deposit set by platform and by the guest's own history (not one flat amount), a score for every guest who has stayed (payment, communication, care of the unit, responsibility, cooperation) and eKYC identity verification before check-in. Each layer exists because something went wrong first. Here is what happened, and what now stops it.
What does a problem guest actually look like?
Not every difficult guest is a problem guest. The one asking where the car park is at midnight is not. The one complaining the aircon is not cold enough is not either - that is our job. The ones who cost owners money are these:
- Headcount fraud: booked "2 adults"; at 11pm security calls to say twelve people and a crate of beer are in the lobby.
- Parties: neighbours complain, management issues a fine, the next morning the unit has vomit and cigarette butts, and the next group checks in at 3pm.
- Leave everything on: aircon at 16°C, every light, the water heater, for the six hours between checkout and the next arrival. The owner pays the electricity.
- Break it and say nothing: mattress, sofa, TV. Checkout photos do not show it; the cleaner finds it after the deposit has been refunded.
- Will not leave: checkout is 11am, they are still showering at 12:30, the next family is waiting in the lobby.
- Platform disputes: five nights in, then "the Wi-Fi was slow, full refund please", and platform support sides with the guest.
Every homestay operator in Johor Bahru has met all of these. The difference is whether the rules changed afterwards.
Layer one: the deposit is not one number - it depends on the platform and the guest
We used to do what most people do: a fixed deposit per unit, refunded after a clean checkout. The problem is that a fixed deposit is a nuisance for good guests and not painful enough for bad ones.
The deposit policy in our system now has three tiers, checked in order:
- Platform gate: guests carry different risk depending on where they booked. Some platforms have a guest review history and their own damage-cover mechanism; some have neither. Bookings from platforms with no protection face a stricter deposit.
- Guest trust: a guest who has stayed with us before has a score on file. Good score, lower or no deposit. Poor score, higher deposit or no booking at all.
- Default deposit: first-time guest, platform with no protection - the unit's default amount applies.
How the deposit is taken changed too: a card authorisation hold, not an actual charge. The guest does not pay a sum and then wait for us to send it back; the hold releases automatically after a clean checkout, and we only capture it if something is wrong. That one change removed most of the complaints from good guests, because "when do I get my deposit back?" was the number one complaint.
Layer two: every guest gets a score
This is where we differ most from other managers. After every stay the system records five scores:
| Score | What it measures |
|---|---|
| Payment | Paid on time, any delays, any disputes afterwards |
| Communication | Replies to messages, keeps to the arrival time they gave |
| Care of the unit | Condition at checkout, any damage |
| Responsibility | Owns up when something happens, willing to pay |
| Cooperation | Security registration, parking, headcount, house rules |
The five combine into one overall score. It is tied to the guest's phone number, not to one unit. The next time they book any of our units - any building in Johor Bahru, or Desaru - the deposit policy checks that score first.
It cuts both ways. Good guests get no deposit on their second stay and a discount for booking direct, so repeat guests keep growing. Problem guests find their second booking carries a deposit high enough that they go elsewhere, or the system declines outright. What a problem guest fears is not being told off. It is not being able to book.
Layer three: eKYC before check-in, so headcount fraud stops at the source
Parties and headcount fraud have one thing in common: the person who booked is not the person who stays. Someone books for friends and never shows up.
So check-in has an extra step: before arrival, the lead guest uploads an identity document on their phone and passes a face match. Only then is the door code sent; if it fails, one of our staff checks ID in the lobby.
This stops more than you would expect:
- The proxy booker either has to turn up in person or hand over the real guest's details - both put party bookers off
- Security has a real name on the register, so management stops giving our guests a hard time
- When something does happen, we know who to go to
For a normal guest it is two minutes. Owners and operators can switch it on or off per unit in the system, because some buildings already have strict security and do not need it twice.
Leaving things on and not leaving: locks and time windows
These two are laziness rather than malice, and rules beat deposits here.
- Smart locks follow the booking: at checkout time the code stops working. A guest who really needs a late checkout pays for it in the portal, charged by the hour, and the money lands in the owner's statement. Unpaid, the door does not open, so there is no "one more shower".
- Aircon: the first thing the checkout clean does is photograph the state of the aircon and appliances. A unit clearly left running all day has the electricity deducted from the deposit, with the photo attached to the reason.
Platform disputes: evidence beats argument
The "slow Wi-Fi, full refund after five nights" case almost always starts with platform support on the guest's side. We win more of these now because of three things:
- Timestamped photos of the unit before check-in, and another set after checkout
- All communication kept on the platform or in our system, never on a personal WhatsApp, so support can read it
- The guest's message history during the stay: five nights without a single complaint and then a full-refund demand on day six - once that is on the table, the case is over
What does the owner see?
Owners do none of this themselves, but they see all of it: every deposit deduction in the owner statement comes with photos and a reason, late-checkout income is itemised, and every incident has a record. Part of what the management fee buys is exactly this: when something goes wrong in the unit, someone is there.
Has your unit been through any of this? Units under our management get all three layers as standard. Tell us where the unit is and we will suggest the deposit policy along with everything else.
Guest behaviours described are recurring patterns from operations and do not refer to any individual or booking. The handling described is Antlerzone's current system configuration; owners and operators can adjust it per unit.