What is a guest profile?
One page per guest — bookings, allergies, visits, no-shows, and loyalty in one place that you own. A CDP builds the profile automatically, so you stop chasing details across notes and separate systems.
- One profile per guest
- You own the guest data
- Built automatically
- Booking history
- Allergies
- Visit count
- No-shows
- Loyalty & stamps
- You own the data
Everything about the guest on a single page
Instead of hunting through emails, notes, and three separate systems, the guest's whole history sits on one profile. You open the name and see bookings, allergies, visit count, and stamps at once.
- Booking history and last visit
- Allergies and table preferences
- Stamps and loyalty on the same card
The guest is yours, not the portal's
When the guest data sits in your own profile, you can contact the guest directly, with no middleman. You don't rent your own regulars back from a booking portal, and you keep everything if you switch systems.
- The guest's data lives with you
- Reach the guest with no middleman
- No lock-in with a portal
The profile fills itself in
Every booking, visit, allergy, and no-show lands on the right profile on its own. When the same person books again they are recognized, and the new rows attach to the existing profile instead of creating a duplicate.
- Bookings and visits log themselves
- The same guest is recognized on return
- No extra work at the counter
The same guest, a very different grip
Without a guest profile the details sit scattered and leave with the staff. On one profile they stay put and show up for everyone. Side by side, the gap is plain.
- Allergies on notes that get lost
- Booking history lives with a portal
- No one knows the guest has been here before
- The knowledge leaves when the staff do
- Everything about the guest on a single page
- You own the data, not a middleman
- The guest is recognized on return
- The knowledge stays in the restaurant
What defines the format
What is a guest profile?
A guest profile is one page per guest that holds everything about a diner in one place — booking history, allergies and preferences, number of visits, no-shows, and stamps on the stamp card. Instead of details scattered across notes, emails, and three separate systems, you open the guest's name and see the whole history at once.
CDP stands for Customer Data Platform, and it is the system that builds the profile for you. A CDP pulls a guest's data from every booking, visit, and stamp and merges it into a single profile per person, automatically. You never join details by hand across tools, and the same guest is recognized on return rather than becoming a new row each time.
CDP here means Customer Data Platform, not a backup product. For a restaurant a guest profile is the core of guest work: it ties the booking system to the loyalty program, so the same guest you seat at the table is the one you reward and invite back.
Why does a guest profile matter for restaurants?
A guest profile matters because the knowledge about a guest otherwise walks out the door. When an allergy lives on a note and the visit history lives in the head of a server who quits, the restaurant starts from scratch with every guest. On one profile that knowledge stays put and shows up for the whole team.
Owning the data yourself matters just as much. If the guest only lives with a booking portal, you are effectively renting your own regulars, and you cannot reach them without a middleman. With your own profile you contact the guest directly and keep the full history if you switch systems.
The figures are an illustrative calculation — the real outcome depends on how many guests you have collected. The direction holds either way: a guest you own you can invite back; a guest held by a portal you cannot.
When you know the guest, every repeat visit gets cheaper. You know who is a regular, who has an allergy, and who has not shown up in a while, and you can act on it without guessing or asking the same thing twice.
What is on a guest profile?
A guest profile collects a few recurring parts, each tied to how you take care of the guest: the booking history shows the pattern, the allergies steer the kitchen, the visit count and stamps drive loyalty, and the no-shows flag who you should handle differently. It all sits on the same page.
- Booking history — every booking the guest has made, so you see how often, how many, and what times they tend to book.
- Allergies and preferences — a nut allergy, a favorite table, or a high chair, saved on the profile instead of on a note.
- Visit count and stamps — the visit count and the stamp card sit on the profile, so loyalty is tallied automatically.
- No-shows — every no-show logs to the guest, so you can see who often fails to turn up.
A restaurant taking 200 bookings a week quickly builds a list of guests it knows: who the regulars are, who has an allergy, and who often fails to show. That knowledge was always there — the guest profile is simply what keeps it from disappearing. The example is illustrative, not measured results.
Terms that sit nearby
- Booking system — where bookings are made, and the source that fills the guest profile with history.
- Stamp card — counts visits toward a reward and sits directly on the guest profile.
- No-show — a missed booking logged to the profile, so you can see who often fails to turn up.
- Loyalty — the repeat-visit outcome the guest profile exists to drive, brought together on the loyalty hub.
How do restaurants use guest profiles with Goboblo?
Goboblo builds the guest profile for you from the booking system. Every booking, visit, allergy, and no-show lands on the right profile automatically, and the stamps from the loyalty program sit on the same page. You open the guest's name and see the whole history — in one system instead of three.
That connection is the part a standalone booking tool misses. When booking and loyalty live in the same profile, you know who the guest is the moment they book, not only when they walk in the door. To see how booking, profile, and rewards fit together, start on the loyalty programs page or read more terms in the glossary.
Common questions about guest profiles
What is a guest profile?
A guest profile is one page per guest that shows everything about a diner: booking history, allergies, number of visits, no-shows, and stamps on the stamp card. It sits in one place instead of scattered across notes, emails, and separate systems.
What does CDP mean for a restaurant?
CDP stands for Customer Data Platform. For a restaurant it means a system that pulls a guest's data from bookings, visits, and loyalty into a single profile per person, automatically, so you never have to merge details by hand across separate tools.
Who owns the guest data?
You do. With your own guest profile the data lives with you, not with a booking portal that rents your own guests back to you. You can contact the guest directly, with no middleman, and you keep the data if you switch systems.
How is the guest profile built?
The profile is built automatically. Every booking, visit, allergy, no-show, and stamp lands on the right guest with no extra typing from staff. When the same person books again they are recognized and the new rows attach to the existing profile.
Want everything about the guest in one place?
Book a short demo and we'll show how a guest profile builds itself from bookings, collects allergies and visits, and drives repeat visits in a real restaurant flow.