Guest CRM
The guest at the door has been here before. Now you know.
The person checking in tonight booked with you in spring, redeemed a coupon in summer, and paid for both. Kinchaku ties every booking, pass, and payment to one guest record — so your staff recognise a returning guest without anyone having to introduce themselves.
This is the relationship you own, not data you rent from a booking platform. The record lives in your workspace, and it’s yours to keep.
Every booking, pass, and payment writes to one record — so the fifth visit never feels like the first.
Your best guest walks in for the fifth time — and the system greets them like the first.
Every booking, pass, and payment sits in a different tool, and none of them know it’s the same person.
One record, every touchpoint
Every touchpoint, one record
Bookings, passes, payments, and scans all attach to the same guest record — automatically, with nothing to type in twice.
Your staff recognise them
Open the record and the whole history is there: what they booked, what they hold, what they’ve paid. The regular gets greeted like one.
The record is yours
The record lives in your workspace, not a platform you rent. Export it, pipe it through the API, take it with you.
What’s in the record
- Contact details — name, email, phone, and preferred language
- Booking history across every venue in your workspace
- Pass history — every ticket, stamp card, membership, and coupon issued
- Payment history — what they’ve paid, taken through Stripe, Square, Stera, or tance
- Custom attributes you define per workspace — dietary needs, room preferences, company, even a LINE handle
- Tags to segment and filter — regulars, VIPs, lapsed guests, however you sort them
- An external ID to match a guest to your own POS or CRM
Every event that happens to a guest — a booking, a pass scan, a payment, a redemption — attaches to their record automatically. That history is what feeds loyalty & rewards and the reports you act on; both read from the same record.
The relationship is yours
The guest record lives in your workspace — not locked inside a booking platform or an OTA that rents you back your own customers.
Take it anywhere: export the full record to CSV, fire webhook events into your own systems, or pull everything through the public API. Your guests, your data, your call.
Multilingual, by preference
Every guest record carries a preferred language — and your storefront speaks eight: English, Japanese, Korean, Chinese (Simplified and Traditional), Russian, Ukrainian, and Malay. Inbound guests browse, book, and hold passes in their own; the messages you send go out in English or Japanese.
One HQ, many workspaces
Run a hotel group, a restaurant chain, or a retail network? Each workspace keeps its own guest records. HQ runs them all from a single account, switching between properties without logging out — and one workspace’s guests never leak into another’s.
Built for privacy
- Workspace-scoped — one workspace’s guest data never reaches another
- Role-based access per workspace and venue — staff see what their role allows
- Marketing consent tracked per guest, so outreach stays opt-in
- APPI and GDPR considerations surfaced in workspace settings
- Clean deletion paths when a guest exercises their rights
- A full activity log — every guest event on the record, for compliance and dispute resolution
For encryption, access control, and the rest of the posture, see our security & compliance page.
FAQ
What is a guest CRM?
A guest CRM keeps one record per guest and attaches everything that happens to them — bookings, passes, payments, scans — so staff can see the history at the door. Here, that record lives in your workspace, one set of records per workspace.
What's in a guest record?
Contact details and preferred language, plus booking, pass, and payment history. On top of that you can set custom attributes, tags, and an external ID to match a guest to your own POS or CRM.
Can I get my data out?
Yes. Export the full record to CSV, fire webhook events into your own systems, or pull everything through the public API.
Do guest records mix between workspaces?
No. Each workspace keeps its own guest records. HQ runs them all from a single account, switching between properties without logging out.
A returning guest, greeted like a stranger — because the record lived in five tools that never compared notes.
