Your best guests are already in there. Now you can find them.

Yes. Postcode look-up is available when adding a customer during a booking, in the customer directory and at Keydesk Direct checkout. It saves typing and, more usefully, keeps addresses in a consistent format so the same guest is easier to recognise next time.

Yes. The customer activity log records which Keydesk user created the customer. That matters most when a duplicate or unusual record appears and you want to trace it back to a person and a moment rather than guess.

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.

Yes, and it does it for you rather than waiting to be asked. Keydesk works out whether a booking belongs to a customer who has stayed before and shows a returning-customer badge on the bookings list, the booking calendar and the booking itself. The booking can show which visit this is for them, and the customer insights include booking count, previous completed stay and lifetime value.

Yes. An administrator creates the tags your business actually uses, in a controlled set of colours so the list stays readable. Tags can be applied from a customer record, from a booking, or to many customers at once, and they then appear on the bookings list, the booking calendar and the booking detail page. Tagging and archiving offer undo where it is safe to do so.

Yes, and it now works across the whole account rather than only the records currently on screen, which is the difference between catching a duplicate and never knowing it existed. Normalised email addresses and phone numbers are also used to match existing customers during Direct checkout and channel imports, so fewer duplicates are created in the first place.

Yes. A CSV export is available for the customer results you have loaded, and reporting exports cover the wider data set. Exported spreadsheets are protected against malicious formula cells, and every report export creates an audit record.

Yes. You can issue a secure link that needs no guest account, and the guest enters who is staying, the ages of any children or infants, and their vehicle registrations and details. Keydesk works out whether the required information is complete, and can send reminder emails for the bookings that are still missing something, on a timing you set. Everything submitted appears on the booking in Admin, where staff can add, edit or remove party members and vehicles themselves.

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.

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.

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.

Not yet. Keydesk sends transactional messages, such as payment notices and stay-detail reminders, and all guest messaging can be switched off account-wide for test and demonstration accounts. Marketing campaigns and a marketing-automation suite are not claimed on this page. What is here is the segmentation you would need to run them: repeat and high-value segments, tags and saved filters.

Email addresses and phone numbers are normalised before they are used to match an existing customer, so a different capitalisation or a differently formatted mobile number does not create a second record. That matching applies to Direct checkout and to guests imported from Pitchup, and profile changes are audited. Marketing consent changes carry their own timestamp and are kept separate from transactional communication.