HospisHospis
Soforthilfe
Back·Tech & Systems

Our guest data is scattered and unused

The same guest exists four times — in three spellings, with two email addresses and no history

Typical for: properties running PMS, booking engine, newsletter tool and spa software side by side · operations that switched systems without migrating the data · houses where reception “keeps it all in their head”

Documented by Hospis

Updated: 25 August 2026

How you recognize it

  • The guest exists several times in the PMS, spelled differently each time
  • Email addresses, phone numbers and postal addresses do not match across systems
  • Preferences and notes sit in free-text fields, on index cards or with individual staff members
  • When systems were switched, the old data was “for now” not migrated
  • Data protection is cited as the reason for not maintaining data at all
  • Analysing origin, length of stay or repeat visits is impossible or manual work

Matching Hospi

JW

Josef Walch

Digitalisation · AI in operations · Systems — Lech am Arlberg
Works with protel · Mews · Mews POS · Smart Host
AdviseImplement

Built a central guest master at Rote Wand — leading system, capture rules and duplicate maintenance from hands-on delivery.

Mapped to root cause
Leading systemCapture routineData protection processQuestions the data answers
View profilePersonally vetted · independent match

Which path fits your situation?

01

Diagnosis

390 € fixed price

A vetted Hospi analyses your situation in a structured way — in conversation and with a written result. Every statement clearly labelled: FACT, BENCHMARK, HYPOTHESIS or CONCLUSION. You get a concrete path, not a sales meeting.

  • A legitimate outcome is also: no engagement needed.
  • If an engagement follows, the diagnosis fee is fully credited.
02

Urgent support

Acute situation? Your case is reviewed with priority — response within 48 hours.

Cause fields — how to tell them apart

Scattered guest data is not a technology problem. It is the result of nobody deciding where the guest record lives.

These fields are complete, and many properties get there on their own — that is what this page is for. The cost simply does not appear on an invoice: internal hours, a few attempts, and a season that keeps running in the meantime.

01

There is no leading system

How you spot it

PMS, booking engine, newsletter, spa, restaurant — each keeps its own guest records. No system is defined as the source, so everyone maintains data wherever they happen to be. No reconciliation takes place.

The way out

Define one system as the guest master — usually the PMS. Everything else reads from it or feeds into it. Whatever cannot be connected is no longer treated as a data source.

02

Data capture is chance, not routine

How you spot it

Whether a guest is set up properly depends on how busy reception is. Duplicates appear because searching takes longer than creating a new record. Preferences are heard, not recorded.

The way out

One capture rule for everyone: search first, then create; mandatory fields defined; preferences into a structured field, not free text. Ten minutes of training, then applied consistently — and a duplicate clean-up once a month.

03

Data protection is used as a brake

How you spot it

Because nobody is sure what is allowed, nothing is done at all. Data is not maintained, not used, not deleted — which leaves the property in a worse legal position than a clear process would.

The way out

Clarify once which data is collected for which purpose, obtain consent properly, set deletion periods. A documented process is legally safer and operationally more useful than doing nothing.

04

The data has no consumer

How you spot it

There is no question that guest data answers on a regular basis. Nobody asks about repeat guests, source markets or length of stay — so nobody notices that the data could not answer them anyway.

The way out

Define three questions to be answered every month. If the data cannot answer them, that is the reason to fix it. Anyone wanting to use the data for communication will find the path in the problem “We do nothing with our guest data”.

Frequently asked

Do we need a CRM?
First a clean guest master in the PMS. A CRM built on scattered data is just another system that knows the guest differently.
How do we get rid of duplicates?
Most PMS have a merge function. Once thoroughly, then monthly. The “search first” rule prevents new ones.
What about the old data from the previous system?
Anything older than a few years with no repeat stay can go. The rest is a data import you do properly once.

Describe your situation

The problem context is automatically included — you do not need to repeat anything.

Problem
Our guest data is scattered and unused

Related situations

We do nothing with our guest data

Repeat guests aren't won back deliberately.

View solution

PMS, POS and CRM don't speak to each other

Guest data lives in silos — personalisation is impossible.

View solution

Our numbers are scattered across too many systems

Decisions take too long.

View solution
See all problems