Product
Table Bookings
CRM enrichment
Summarygenerating…
Overview
The moment a booking is confirmed, the booker's email and phone join the unified guest profile. Visit count, last booking, party size, and notes roll up onto the profile for audiences and workflows.
How it works
The bookings engine writes booking events directly to the shared profile layer. Duplicate detection merges matching identities.
Core concepts
Auto-enrichment
no separate opt-in step required for the profile to form.
Visit count
number of times the guest has booked.
Usage & workflows
Marketing to bookers, lifecycle workflows, segmentation.
Example
After 6 months, 2,100 booker profiles exist in CRM; 900 have received a post-visit review request and 120 have returned through a lifecycle workflow.
Note
Where to find it
Configure this in the Stampede admin app under Admin → Bookings. Permissions are role-gated — contact your account owner to request access if you don't see it.
Tip
API reference
The Stampede API exposes guest, booking, and campaign data programmatically. See developer.stampede.ai for authentication, base URL, rate limits, and endpoint reference.
Note
Need help?
Contact support via the Stampede admin app or your account manager. The knowledge base at help.stampede.ai has guided walkthroughs for common tasks.
Want to see it live?
Book a 20-minute walkthrough and we'll show you the feature in your own admin.