One profile per person
Records matched conservatively on shared phone, email, or source ID — never on name alone, because two guests share a name far more often than people expect.
For multi-concept groups
Your best guest is a stranger at four of your five restaurants.
They have been coming to your flagship for years. They walk into your new concept across town and nobody knows who they are — because to that location’s systems, they are a first-time booking.
Why groups lose this
- Each location’s reservation book is its own island, often on a different platform.
- Acquisitions arrive with their own POS and their own guest list.
- The same person books under a nickname here and a work email there.
- Group leadership sees five reports and no single relationship.
What you get
A duplicate queue, not a silent merge
Uncertain matches go to a person with the evidence laid out. A wrong merge destroys history permanently, so we would rather ask.
Context that travels
The host at your newest concept sees that tonight’s 7:30 has twenty-one visits with the group — before they arrive.
Permissions that respect the room
Group-wide recognition without every location seeing everything. Some notes travel; some stay where they were written.
Show me the overlap
Compliments of the house.