When the Same Code Opens the Door and the Conversation

How an uncomfortable question — “Do you use WhatsApp?” — became a private communication channel for our guests.*

---

When guests arrive at Apartma Matevž, they receive a keycard with the essential information for their stay: a QR code and the PIN for the door.

But here, the same code does more than open the apartment.

It also opens a conversation.

A question I never liked asking

Communication with guests is usually scattered across Booking.com, email, text messages and various apps. WhatsApp is often the easiest option, but I have never felt entirely comfortable asking a guest: “Do you use WhatsApp?”

It sounds harmless, yet it already asks something of them. They need an account with a particular company, they may need to share their phone number, and the conversation moves away from the reservation into another external system.

So I turned the question around: why should the guest have to enter my communication channel? Why shouldn’t a private channel already be waiting for them where they are staying?

No account, no app, no new password

That idea became Guest Chat — a private communication channel between guest and host.

The guest scans the QR code on the keycard, opens a web page and enters the PIN they already know. There is no registration, username, app installation or social network involved.

The PIN finds the relevant reservation and opens its conversation. When the guest sends a message, it is stored with the correct stay and the host receives a notification. I immediately know who is asking, which apartment they are staying in and when they are leaving.

For the guest, the whole process is simply:

scan, enter a familiar code, ask a question.

A useful reason to visit our website

I admit there was also a slightly mischievous thought behind the idea: how could I encourage guests to use our own website?

Not through advertising, pop-ups or a request to remember the address. I wanted them to open it because it was genuinely useful at that moment.

Guest Chat became that reason.

A guest may arrive because they need help, but the website then becomes more than a brochure they once saw before booking. It becomes part of their stay — a place for communication, instructions and support. Along the way, they may also notice the gallery, local information, availability or the possibility of returning through a direct booking.

It is promotion hidden inside a useful service. And the first measurements already show that it works.

A conversation with its own time window

Because the channel belongs to a reservation, access does not remain open forever. The host can define how many days before arrival and after departure the PIN is valid. This gives guests enough time to ask questions before check-in, get help during their stay and resolve a final detail after leaving.

For returning guests or people with whom we choose to remain in contact, a reservation conversation can be converted into a permanent channel without losing its history. The guest can later change the PIN themselves if needed.

One system can therefore support both a short, purpose-specific conversation around a stay and a longer relationship — but only when both sides want it.

Sometimes a photograph is the best explanation

Not every problem needs a long description. A confusing symbol on an appliance or a small fault can often be explained much faster with a photograph, so guests can attach an image to their message.

The system also includes a small library of instructions for equipment in the apartment. A dishwasher, EV charger or heating control can have a short guide and its own QR code. I can send the guide directly into the conversation or place the code beside the device.

Help remains where it is needed, instead of disappearing inside a thick information folder that nobody opens.

Notifications without noise

The host can receive email and push notifications, but an active conversation does not generate a new alert for every sentence. Messages arriving within the same short exchange are treated as a continuation rather than a series of separate emergencies.

While the page is open, the guest sees replies automatically. Permanent channels can also use optional push notifications. Nothing is forced; the basic channel works without them.

Born beside CM, but independent

Guest Chat is a standalone, self-hosted module. It does not maintain its own guest database and it never changes reservations. It only reads the small amount of information it needs from an existing CM installation: the PIN, guest name and dates of the stay. Messages, uploaded images and notification settings remain in the module’s own storage.

This follows the same principle from which CM grew: the essential service should remain with its user, while external platforms should be a choice rather than a requirement.

Guest Chat was born beside CM, but the idea is not limited to it. Wherever there is a reservation, a time-limited access code and a need for a private conversation, a channel like this could exist.

The detail that changes the experience

Guests will probably never think about the architecture behind it. They may not notice how many decisions were needed so that they would not have to create an account.

They will only notice that help is close at hand.

They scan the code, enter a PIN they already know and ask what they need. I know who is asking and how I can help.

Sometimes the best digital solution is not the one offering the most features. It is the one that puts the right detail in the right place — and then almost disappears.

Here, the same code opens the door and the conversation.

And that is really the whole story.