DQ Core keeps a lightweight guest CRM so your team can recognise and look after regulars. This is separate from the door — see the Guest Lists guide for that.
A guest is a person — a record you can reuse across their visits, attached to bookings and guest list entries.
Note: Guests are shared across your whole company, not tied to a single venue — handy if you run more than one venue under the same business. There's no automatic duplicate-checking on phone or email, so the same person can end up with more than one guest record. If you spot a duplicate, just pick the right one when attaching a guest to a booking.
Tag guests (and menu items, events, and packages) so they're easy to search and so the floor knows how to treat someone — favourite drink, dietary need, VIP status, whatever's useful to your team.
Tags come in a few flavours to help with grouping and colour-coding: taste, music, brand, general, and highlight.
Guest search works by picking one or more tags rather than typing free text — select the tags you want and see everyone who matches, instantly.
Note: Removing a tag from a guest deletes that link completely rather than just hiding it. This is intentional, so a removed tag can never accidentally still show up in a search.
On a guest's profile, DQ Core can also show tags it has worked out on its own from what that guest has ordered and attended — things like "Likes Vodka" or "Regular".
Tagging is a low-stakes, everyone-helps activity — every role can create and assign guest tags. Tagging menu items, events, or packages follows the same access as editing that item (generally Owners/Managers).
Removed a tag but the guest still shows in a tag search. This shouldn't happen since removal is permanent — flag it to a manager if it does.
Can't search by a derived (automatic) tag. By design — only manual tags are searchable.
Duplicate guest record. There's no automatic duplicate-checking; pick the correct guest, or ask a manager to help tidy up duplicates.
