Case study · anonymised
28-room boutique in Krakow: contactless check-in cuts night-shift workload by ~60%
28-room boutique, leisure-led, Krakow city centre, ADR ~EUR 110, occupancy ~70% year-round
The challenge
Late-evening guest arrivals (after 20:00) were a structural problem: the night auditor handled check-in, ID verification, and key issuance on top of the daily close, which extended the night shift by 60-90 minutes on busy nights. The property had Cloudbeds for PMS and Stripe for payments but no guest-journey layer; check-in was 100% manual.
The approach
The team deployed a guest-journey platform with bidirectional Cloudbeds integration: pre-arrival message 24 hours out with a check-in link, in-portal ID upload and signature, Stripe authorisation hold 48 hours before arrival, PIN-code emission on the existing electronic locks (no lock replacement). The integration was the deliberate decision: the team chose a platform with a true webhook-driven bidirectional PMS sync over a cheaper option with XML feed sync.
Measured outcomes
Late-evening front-desk interactions (20:00-00:00)
Before: all arrivals served by night auditor
After: roughly 60% reduction in interactions during that window
Self-service check-in adoption (month 3)
Before: n/a (no portal)
After: ~72% of arrivals complete portal flow
Card pre-auth failure rate
Before: n/a (manual)
After: about 4% of pre-auths fail and route to a guest follow-up
The failure pattern and the fix
The naive deployment plan would have been to launch self check-in for 100% of arrivals on day one. The team instead piloted with 30% of arrivals for the first six weeks, identified the top three friction points (link not received for OTA-booked guests because the email field in the PMS was inconsistently populated; one specific ID-upload format being rejected; the lock-PIN duration being too short for late checkouts), and fixed them before expanding to 70-80% adoption. The remaining ~20-30% of guests remain front-desk-served because some explicitly prefer the personal touch.
What we took away
The lesson is that the integration depth, not the portal UI, is what determines whether contactless check-in saves staff time or just adds reconciliation overhead. The team's decision to spend extra on a bidirectional-PMS-sync platform paid back inside the first quarter through staff-hour savings on the night shift. Cloudbeds being a mature PMS with deep webhook APIs made the integration easy; on a legacy PMS, the same project would have been substantially harder.
Anonymisation note
This case study uses anonymised property data: segment, room-count band, market region, and outcome metrics. The property is not named. Operator-reported figures are presented with that framing; published industry benchmarks are cited inline.