Relationships
How everything about a guest connects — visits, bookings, orders, the people they dine with — shown as one picture.
What is it?
Where the explorer shows the parts of a profile, this view shows the connections between them: who visited, who booked, who ordered, who they came in with, who they gifted to. It is the web that turns scattered records into a single story about a guest.
Those connections carry detail of their own. The link between a guest and a venue knows how many times they have visited, when they first and last came in, and what they have spent there. The connection is not just a line — it remembers.
This is why a returning regular’s history loads instantly, however big your guest base grows — the connections are built in, not pieced together on the fly.
Element features
Visits, bookings, orders and more are linked, so a guest reads as one story.
The link between a guest and a venue holds their visit count, first and last visit, and total spend.
Pulling up a guest’s full history stays quick no matter how much data you hold.
Stampede is built around guest connections from the ground up, not bolted on afterwards.
Segments and automations see these details the moment they change.
FAQs
Detail lives on the connection itself. The link between a guest and a venue holds how often they have visited and what they have spent there.
Guest connections are built into the platform, so pulling up a history stays quick even across a large estate.
Yes. Segments read details like total spend straight off the connection, so visit history drives who is in a group instantly.
It lives on the guest-to-venue connection and updates as visits are recorded, so the profile always reflects the latest.
See Relationships running on your venues
Thirty minutes is enough. Book a demo or send a question — both routes land on the same team.