KohortKohort
Agentic Hospitality & Travel

Know Who They Are Before You Send Anything

Guest data sits in the property system, the booking channel, the loyalty programme and the campaign tool. Kohort builds the segment from all of them, and keeps the identity when the guest moves.

Coming Soon
01The Problem

The segment was right. The guest was not in it.

Every system held a true fact and drew a reasonable conclusion from it. The campaign tool saw someone who stopped opening email. Nobody put that beside a 34-night stay, a search in a new city and points about to lapse.

A cohort built from one system is a guess. The cost is not a bad email, it is the guest who was leaving for a reason you could have answered.

02The Trace

Four systems. One answer.

What each system knew, and when it knew it.

CRM Lead
Is this guest lapsing, or is something else going on?
Kai · context graph · 4 linked records
12 MarPropertyA guest checks out after a 34-night stay. Folio closed, no issues.
14 MarEmailThey enter the win-back journey for lapsed guests.
19 MarWebThey price extended stays twice, in a different city.
22 MarLoyaltyPoints lapse in 30 days. No notice has gone out.
KOHORT CORRELATES THE FOUR

This guest is relocating, not lapsing, and the win-back offer is the wrong one, 8 days into a 30-day window.

No system holds this. The segment is derived at query time from the four records above.

AUDIENCEmove to relocating · suppress win-back
Before the send, not in next month's report. The audience change is the output, written back through the same Blueprint Kohort read.
03Systems

It reads the stack you already run

No migration, no eighteen-month replatform. Kohort queries your property, booking, loyalty and campaign systems where they sit.

Property & Reservations
Opera CloudOpera Cloud
HotelKeyHotelKey
MewsMews
CloudbedsCloudbeds
Distribution
SabreSabre
AmadeusAmadeus
Booking.comBooking.com
ExpediaExpedia
Customer Data
SegmentSegment
TealiumTealium
mParticlemParticle
Salesforce Data CloudSalesforce Data Cloud
Engagement
BrazeBraze
KlaviyoKlaviyo
IterableIterable
TwilioTwilio
Experience & Analytics
MedalliaMedallia
Adobe Experience PlatformAdobe Experience Platform
AmplitudeAmplitude
MixpanelMixpanel
Revenue & CRM
DuettoDuetto
IDeaSIDeaS
SalesforceSalesforce
Dynamics CRMDynamics CRM

A sample. If a system holds data, a Blueprint can read it. Browse Blueprints

04In Action

The same shape, other questions

One segment is one query. A guest base raises a lot of them.

Cohorts That Cross Systems

SCENARIO

A segment is built from email engagement alone.

QUESTION

Who is in this cohort once stay history, spend and service issues are included?

ANSWER

Kohort builds the segment from every system at once rather than the one that owns the campaign, so a guest who stopped opening email but kept booking is not counted as lapsed.

Identity That Survives a Move

SCENARIO

A long-stay guest relocates and their address, card and phone all change.

QUESTION

Is this a new customer, or the same one with twelve years of history?

ANSWER

Kohort resolves identity across the systems that each hold one fragment, continuously rather than on a periodic file run, so the history follows the person.

Kohort runs on the Korthread platform, reading property, booking, loyalty and campaign systems through Blueprints and answering over Korthread Fabric. See how the platform works

05Early access

Want early access to Kohort?

We’re partnering with a small set of design partners in hotels, travel and extended stay. Book a call to discuss your guest data.

We use cookies to analyze site traffic and improve your experience. See our Cookie Policy for details.