Guest CRM for parks, campsites and accommodation.
Give booking teams useful returning-guest context—contact details, stay history, favourite property and consent status—with archive, restore and erase actions kept under operator control.
Jess Thompson
Returning guest · last stay October 2025.
- jess@example.com
- Favourite property
- Sea View Lodge
- Marketing status
- Consent recorded
- Next arrival
- 19 July · Meadow Pod
- 19–22 Jul 2026
Meadow Pod · upcoming
- 17–20 Oct 2025
Sea View Lodge · completed
- 04–07 Apr 2025
Sea View Lodge · completed
Recognise the guest without rebuilding their context.
The customer snapshot is designed for the reservation workflow: enough history to help the team take the next booking, without positioning Keydesk as an unsupported marketing-automation suite.
- Returning guest snapshot
- Surface the customer context already held in Keydesk while the team takes a new booking.
- Stay history together
- Keep previous stays connected to the customer record instead of searching separate reservation lists.
- Useful preference signal
- Show the favourite property context evidenced in the current customer snapshot.
- Consent status visible
- Keep the recorded marketing-consent status close to the customer details used by the team.
Bring the previous stay into view while taking the next one.
Keydesk’s current Booking Mode evidence shows a customer snapshot with stay count, last stay, favourite property and marketing-consent status before the new reservation is completed.
- 01
Find the returning customer
Bring the existing customer snapshot into the booking flow.
- 02
Use relevant stay context
See the history and favourite-property signal already recorded.
- 03
Confirm the new booking
Keep the new reservation connected to the customer context available in Keydesk.
Archive, restore and erase are different operational decisions.
Keydesk provides the actions. Your organisation still decides when each is appropriate, what linked information is in scope and which records must be retained for another valid purpose.
- Working record
- Available to the booking team for current customer and stay workflows.
- Archive
- Move a customer record out of the active working set when the operator’s process calls for it.
- Restore
- Return an archived record when it should become active again.
- Erase
- Use the erase action only after the operator has confirmed the applicable scope and obligations.
Confirm the exact erase behaviour for customer data, linked bookings and backups during onboarding before relying on one product action as the complete response to an individual-rights request.
Software supports the workflow. The operator makes the data-protection decisions.
Keydesk can make records and actions easier to work with. It does not choose a lawful basis, write your privacy notice, set retention periods or decide whether a rights request applies.
| Workflow | Keydesk support | Operator responsibility |
|---|---|---|
| Customer context | Shows the customer snapshot and connected stay history currently held in Keydesk. | Decide what guest information is necessary, accurate and appropriate to record. |
| Marketing status | Keeps the recorded marketing-consent status visible with the customer. | Choose the lawful basis and PECR route, collect valid evidence and honour objections or withdrawals. |
| Retention workflow | Provides archive, restore and erase actions for customer records. | Set and justify retention periods, run reviews and decide when information is no longer needed. |
| Rights request | Provides record-management actions that may support the operational response. | Recognise and verify the request, search every relevant system, assess exceptions and respond on time. |
A consent badge is evidence to examine—not permission invented by software.
A visible status helps staff avoid treating every email address as a marketing audience. The operator still needs to know what was agreed, when, how, for which channel and how a person can object or withdraw.
- Service communication
- Messages needed to deliver a current booking are not automatically the same as direct marketing.
- Marketing communication
- Check the applicable UK GDPR lawful basis and PECR rule for the method and audience.
- Status maintenance
- Keep changes, objections and withdrawals reflected in the operational process and connected systems.
Build the operating process around authoritative guidance.
These ICO resources explain the principles that sit around a guest CRM. They are external guidance, not features supplied or legal conclusions made by Keydesk.
Guidance reviewed 17 July 2026. Data-protection guidance can change; confirm the current ICO position and obtain professional advice where needed.
Guest CRM and data-workflow FAQ.
What is an accommodation guest CRM?
An accommodation guest CRM connects a customer record with the information needed to recognise and serve that guest across bookings. In Keydesk, the current focus is practical booking context: contact details, stay history, a favourite property signal and recorded marketing-consent status.
Can Keydesk recognise returning guests?
Yes. Booking Mode can surface a returning customer snapshot with previous-stay context while the team takes a new reservation. This reduces repeated questions and keeps the new booking connected to the customer history available in Keydesk.
Does Keydesk record marketing consent?
Keydesk can show marketing-consent status with the customer record. The operator remains responsible for the wording, collection method, lawful basis, PECR conditions, evidence and withdrawal process appropriate to each marketing activity.
Can customer records be archived, restored or erased?
Yes. Keydesk currently includes customer archive, restore and erase actions. Before using an erase action for a rights request, the operator should confirm the request, the data that must be retained, linked records and the precise deletion scope.
Does using a guest CRM make a business GDPR compliant?
No. Software can support record visibility and data-handling actions, but compliance depends on the operator’s purposes, lawful bases, notices, minimisation, accuracy, security, retention, supplier terms, staff processes and handling of individual rights.
Does Keydesk include automated guest marketing campaigns?
This page does not claim automated marketing campaigns or a marketing-automation suite. It describes the customer record, returning-guest context, consent-status visibility and data-management actions currently evidenced in Keydesk.
Bring one real guest workflow. Review the current product honestly.
We’ll walk through returning-customer context and the current record actions, then separate what Keydesk supports from the policy, legal and cross-system work your organisation still owns.
- Returning guest snapshot
- Archive, restore and erase actions
- Transparent current product scope
Be first to hear when beta opens. No spam. Just occasional updates as we build.