Five strangers.One guest.
One explainable guest profile, from data scattered across every system in the hotel.
The vision
One guest, not five strangers.
We are working toward hotels that know a returning guest as one person, whichever of their systems the guest passed through, from a profile they can ask why it believes what it does, and correct when it is wrong.
What we hold to
Seven values, each with the thing we never do.
A match is not trusted until it is justifiedWe never switch on a merge that no person asked to trust.
Every merge can be explained and undoneWe never ship a way of merging guests whose decisions cannot be read back and undone.
Everything the engine does is on its APIWe never build an engine capability that can only be reached through a job, an internal call or the database.
Never drop what can be parsedWe never discard a parseable record because it does not look the way we expected.
Store what happened, derive who it wasWe never overwrite a source record to fix what a guest's profile says.
Tenants never meetWe never add a path, for an operator or for ourselves, that reads one tenant's guests from another's.
The core stays openWe never hold back or degrade a capability of the core to sell the hosted service.
The idea
Five records, one profile.
The same person books, checks in, eats, joins the wifi and leaves a review — and every system stores someone different. GuestGraph resolves those records into one profile, and can always tell you why.