A hotel guest database is one clean record per guest, built automatically from your PMS, booking engine and direct inquiries, with stay history, preferences and marketing consent attached. For an independent hotel or B&B it can be a lightweight CRM or even a well-structured list. Automation keeps it synced and de-duplicated. Staff decide who gets contacted and why.
Most small properties already have the data. It's just split across the property management system, the booking engine, an inbox, a spreadsheet of regulars and an OTA extranet. This post walks through a practical workflow to bring it together, then use it for repeat-guest offers without breaking privacy rules or annoying the people who stayed with you.
Key takeaways
- A hotel guest database pulls stay history from your PMS and booking engine into one clean record per guest, with consent and contact preferences attached.
- OTA guests often arrive with masked email addresses, so the database only holds a direct address once the guest has given it to you.
- Automation handles syncing, de-duplication and segment lists, while staff approve every campaign and handle anything sensitive.
- Consent rules differ in the US, UK, EU and California, so record the basis for every marketing contact and keep only what you need.
Why guest data stays scattered
Common problems at independent properties:
- Duplicates everywhere. "Jon Smith" from 2024 and "Jonathan Smith" from 2026 are the same person with two profiles and two stay histories.
- OTA addresses are borrowed. Booking.com, for example, doesn't share private guest email addresses. As Hospitality Net reports, quoting Booking.com's partner help, hotels and guests only see an anonymous alias, and messaging works from booking until seven days after checkout or cancellation.
- Consent isn't recorded. Someone ticked a box on the booking engine three years ago, but nobody knows which box or what it said.
- Notes live in people's heads. The front desk knows the couple in room 4 always want a quiet room. The system doesn't.
- Nothing is ever deleted. Old records from guests who stayed once a decade ago still sit in the export, which is a privacy risk with no upside.
The hotel automation hub covers the wider set of workflows for independent properties. This one is the foundation that pre-arrival messages, review requests and direct-booking campaigns all depend on.
What goes into the database (and what doesn't)
Collect what you will actually use. A simple structure:
| Field group | Examples | Source | Notes |
|---|---|---|---|
| Identity and contact | Name, direct email, phone, country | PMS, booking engine, direct inquiry | Only a direct address the guest gave you, not an OTA alias |
| Stay history | Dates, room type, rate plan, channel, spend | PMS | Synced automatically after checkout |
| Preferences | Quiet room, early check-in, pillow type | Front desk notes, pre-arrival form | Keep factual and kind; guests may ask to see them |
| Consent and preferences | Marketing opt-in, channel, date and wording shown | Booking engine, check-in form | Record the basis for every marketing contact |
| Suppression | Unsubscribed, complaint, do not contact | Email tool, staff | Must sync back to every system |
What to leave out:
- Payment card details. They belong with your payment provider and PMS, not in a marketing database.
- Health information. Allergy or accessibility notes can be health data. In the UK and EU, the ICO lists data concerning health as special category data, which needs a lawful basis plus a separate condition. Keep these notes in the PMS for the stay they relate to, not in segments or campaigns.
- ID document scans. If local law requires you to record guest identity details, that's a legal record with its own rules, not marketing data.
The guest database workflow, step by step
1. Sync stays from the PMS after checkout
Trigger: a guest checks out.
What the automation does: it pulls the guest record and stay details from the PMS through its API or a scheduled export and sends them to the database. It only takes the fields in your table above.
Who checks: the manager reviews the field mapping once and spot-checks a handful of records each week for the first month.
2. Match and merge duplicates
Trigger: a new or updated record arrives.
What the automation does: it looks for an existing guest with the same direct email or phone number. Exact matches merge automatically. Near matches, such as the same name and phone with a different email, go to a review list instead of merging.
Who checks: a staff member clears the review list weekly. Merging the wrong people is worse than leaving a duplicate.
3. Capture direct contact details the honest way
Trigger: a guest booked through an OTA.
What the automation does: nothing sneaky. It can't and shouldn't scrape an alias. Instead, the property gives guests a reason to share a direct address: a digital registration card, Wi-Fi sign-in, a pre-arrival form when it's sent through permitted channels, or a QR code at reception that opens a "join our guest list" form. Our free QR code generator makes the code; test it on a few phones before printing. The form records exactly what the guest agreed to.
Who checks: the manager approves the form wording and the privacy notice it links to. If you need a starting point for the notice, the privacy policy generator gives you a draft to review with your adviser. The free tools at /tools need a free account.
4. Build segments, not blasts
Trigger: a weekly schedule.
What the automation does: it refreshes a few useful lists, for example:
- Repeat guests who've stayed two or more times and agreed to hear from you.
- Seasonal guests who stayed in the same month last year.
- Direct bookers versus first-time OTA guests who later shared a direct address.
- Lapsed guests who haven't stayed in two years, flagged for review or deletion.
Who checks: the manager picks which segment gets a campaign. Every list excludes anyone suppressed, and anyone without a recorded basis for marketing.
5. Repeat-guest offers with approval
Trigger: the manager chooses a segment and an offer, such as a returning-guest rate for the same week next year.
What the automation does: it drafts the email, personalizes it with the guest's name and last stay month, and holds it for approval. After sending, it updates the guest record and stops further messages for anyone who books or unsubscribes.
Who checks: the manager approves wording, rate and dates every time. Keep personal notes out of marketing copy. "Welcome back, we've saved your favorite quiet room" can feel thoughtful or intrusive depending on the guest, so leave that for the stay itself.
Before the first campaign, check your sending domain with the email deliverability checker and the DMARC checker. Google's email sender guidelines require SPF or DKIM for all senders to Gmail, and SPF, DKIM and DMARC plus one-click unsubscribe for marketing from senders of 5,000 or more messages a day. Running old addresses through the email verifier before a campaign also cuts bounces.
6. Retention and deletion
Trigger: a monthly schedule.
What the automation does: it flags records past your retention period and anonymizes or deletes them once approved, keeping only aggregate figures such as stays per month.
Who checks: the manager. The ICO's guidance on storage limitation says you must not keep personal data for longer than you need it, should have a policy with standard retention periods and should periodically erase or anonymize data you no longer need. Tax and accounting records may have their own minimum periods, so set retention with your accountant.
Consent and privacy rules by region
This is a checklist, not legal advice. Check the rules where your guests live, not only where your hotel is.
- UK. Marketing email to individuals generally needs consent. The ICO's electronic mail marketing guidance describes the "soft opt-in": you can email existing customers who bought, or negotiated to buy, a similar product or service from you, if you gave them a simple way to opt out when you collected their details and in every message. It doesn't apply to prospects or bought-in lists.
- EU. The GDPR applies to businesses outside the EU too when they offer goods or services to people in the EU, under Article 3(2). EU countries also have their own e-marketing rules, so a European guest list needs a recorded basis for each contact.
- US. The FTC's CAN-SPAM guide requires a valid physical postal address in commercial email and says you must honor opt-out requests within 10 business days.
- California. The CCPA applies to for-profit businesses that meet at least one threshold, such as gross annual revenue of $26.625 million or more, according to the California Privacy Protection Agency. Many independent hotels fall below it, but California residents' rights to know, delete and opt out of sale or sharing are worth honoring anyway, and other states have their own laws.
How to start small
- Export and clean once. Pull two or three years of guests from the PMS, merge obvious duplicates and remove anyone who has unsubscribed or complained.
- Fix consent capture going forward. Update the booking engine checkbox and registration card so the wording and date are stored with each guest.
- Automate the checkout sync and the duplicate review list.
- Send one campaign to your repeat-guest segment and watch replies, unsubscribes and bookings.
- Add retention rules before the database grows any further.
Once the database is reliable, the other workflows get easier. Our posts on pre-arrival messaging and upsells, review responses and guest request triage and the hotel direct booking website all build on the same guest records. If you'd like help mapping where your guest data lives today, Make It Flow can talk it through with you.
Frequently asked questions
What is a hotel guest database?
It's a central record of everyone who has stayed at or inquired with your property, with contact details, stay history, preferences and marketing consent. Larger hotels use a dedicated hotel CRM. Small properties can start with their PMS guest profiles plus a well-managed email list.
How do hotels collect guest data?
Mainly through bookings in the PMS and booking engine, registration at check-in, Wi-Fi sign-in, pre-arrival forms and direct inquiries. Each collection point should tell guests what you'll use their details for and record any marketing consent.
Can I email guests who booked through Booking.com or Expedia?
You can message them through the OTA's own channels about their stay. Booking.com, for example, provides an anonymous alias rather than the guest's real address. Add a guest to your own marketing list only once they've given you a direct address and the consent or basis your local rules require.
What is the difference between a PMS and a hotel CRM?
A PMS runs operations: reservations, rooms, check-in, folios and billing. A CRM focuses on the guest relationship over time, with merged profiles, segments and campaigns. Many PMS platforms include basic guest profiles, and some independent hotels connect a separate CRM or email tool for marketing.
How long can a hotel keep guest data?
Under UK and EU data protection law, only as long as you need it for the purpose you collected it, with a written retention policy. Legal records such as invoices may need to be kept for set periods. Set your schedule with your accountant and legal adviser.
Do small hotels need a CRM?
Not always. A property with a few rooms can do well with clean PMS profiles and one email tool, as long as duplicates, consent and unsubscribes are handled properly. A dedicated CRM becomes useful when you have several channels, many repeat guests or more than one person running campaigns.
Sources
- Hospitality Net: Everything the OTA sends you about your guest expires
- ICO: Special category data
- ICO: Storage limitation
- ICO: Electronic mail marketing
- GDPR Article 3: Territorial scope
- FTC: CAN-SPAM Act: A Compliance Guide for Business
- California Privacy Protection Agency: Frequently asked questions
- Google Workspace Admin Help: Email sender guidelines
More guides for your industry
Free checklist (PDF)
Free hotels & b&bs website checklist
28 practical checks for hotels & b&bs: website speed and mobile, Google Business Profile and reviews, email security, booking and enquiry handling, and AI search visibility. Each one says why it matters, and many link to a free tool that checks it.
Written by the MakeItFlow team
We build the website audit these guides are based on. Every fact is checked against the primary sources listed above . How we research and check
Check your own site in 30 seconds
Run a free audit covering speed, SEO, DNS, email authentication and security headers — and get a prioritised fix list.