Guest Chat Few Days Later: What Real Use Taught Me

A follow-up, not a rewrite

I previously wrote about Guest Chat — a private, account-free communication channel that opens with the same PIN a guest already has for the door. The idea held up. But using it in daily practice, on real reservations, quickly surfaced three gaps I hadn't planned for.

---

"Can I just send you the PDF?"

The first gap showed up on my own side, not the guest's. A printer problem in production meant I needed to get a document into the system and print it from wherever I was. A photo works for a broken latch or a confusing symbol on an appliance — it does not work for a document.

So the same upload button that already handled photos now accepts PDF, Word, Excel and plain text files. A document attached to a message opens directly in the browser, ready to read or print, with no separate download step and no new app. It is the same principle as before, extended rather than replaced: whatever needs to travel between guest and host travels through the one channel they already have open.

A notification is a notification, not a tier

The original version only pushed a notification to me for permanent channels — conversations that had been deliberately upgraded past a single stay. Reservation-based conversations relied on the page being open to be noticed in real time.

That distinction made sense on paper. It did not make sense in practice. A guest mid-stay does not care whether their channel is "permanent" — they care whether someone read their message. So host notifications now cover every active conversation, not just the ones that graduated. The channel doesn't need to earn attention; it already has a real guest behind it.

An expiry date, not just a start date

The last gap was less about usability and more about responsibility. A reservation-based conversation opens automatically within a window around the stay — but nothing closed it afterward. Messages and any attached files stayed on the server indefinitely, long after the reservation, and any reason to keep them, had passed.

That is not a small oversight under GDPR: personal data tied to a stay should not outlive its purpose. So the same window that opens a conversation now closes it. Once a reservation's access window has been over for good, its messages and uploaded files are automatically deleted — no manual cleanup, nothing to remember. Permanent channels, being a deliberate choice by both sides, are never touched by this; and removing a permanent channel now also correctly removes whatever files were attached to it, closing an unrelated gap where uploads could previously outlive the conversation itself.

The pattern holds

None of these three changes touch the core idea. A guest still scans a code, enters a PIN they already know, and asks what they need. What changed is closer to what should have been there from the start: a document can travel through the same door as a photo, a notification doesn't check whether a channel is important enough to deserve one, and data doesn't linger past the reason it existed.

Small corrections, but the kind that matter more once something is actually being used by real people, not just designed for them.