Organisations and properties
Properties belong to an organisation; membership and roles are explicit records, not settings on a user.
Guest Club · Guest identity
A. Papadaki
a.papadaki@… · 1 420 pts
4 stays · Silver
Anna Papadaki
+30 69… · 900 pts
3 stays · Member
One guest profile
7 stays · Gold · shared history
1,420 pts
Multi-tenant
One account, many properties
Access is enforced on the server, per organisation and per property. A property manager sees their property. A group owner sees the group. Nobody sees another customer's data.
Roles that match hotels
Group admin, property manager, staff and guest, each with a different screen and different permissions.
Audit trail
Credential rotations, merges, redemptions and administrative actions are recorded with who and when.
Loyalty engine
Every point has an explanation
Awarded on check-out only
Not on booking, not on arrival. Points reflect revenue you actually recognised.
Reversals are automatic
Cancellations, no-shows and refunds reverse the matching points with a linked transaction.
Activation date respected
Stays before your launch date are imported for context but never award points unless you ask.
Every movement is traceable
Each point has a reason, a source event and a timestamp. Guest disputes take seconds, not an afternoon.
Identity
One guest, one profile
The same guest arrives as three records: an OTA alias, a phone booking and a walk-in. Guest Club matches on verified email, verified phone and RoomRack guest ID, then proposes merges for anything ambiguous.
Confident matches join automatically
Verified identifiers merge without asking, so balances stay in one wallet.
Ambiguous matches wait for a human
Suggestions are queued with the evidence, and merging keeps the full history of both records.