Hospitality · Email
Booking and winback after merge.
+27%
Direct booking, email
2.1×
Winback vs last year
11 wks
Merge to journeys
Sectors / Stay · loyalty · direct
Hospitality.
Booking is a promise. Winback is a relationship. A CRM merge does not make either of those true.
Why here
A function already exists. The week does not.
Hospitality groups run brands, properties, and loyalty on stacks that have been merged more than once. The guest file is large. The journeys are often dead keys and a quarterly blast.
The practice sits there to hold booking and winback as living paths — distinct voices, one system — not to decorate a chain.
Typical missions
- Booking journey after a CRM merge.
- Winback on recency and affinity, not a discount calendar.
- Brand mail that does not collide with transactional stay mail.
The first month
Constraint. What we hold. First 30 days.
Merged CRMs, ghost journeys
- What we hold
- Identity map, booking path, winback logic
- First 30 days
- Dead keys, preference center, first living journey
Three brands, one accident of voice
- What we hold
- Send plan that keeps voices distinct
- First 30 days
- Claims per brand; a stop on collisions
Winback is a quarterly code
- What we hold
- Triggered recency and property affinity
- First 30 days
- Suppress the blast; stand up one honest stream
Hospitality. Shape of the work, not a package menu.
| Constraint | What we hold | First 30 days |
|---|---|---|
| Merged CRMs, ghost journeys | Identity map, booking path, winback logic | Dead keys, preference center, first living journey |
| Three brands, one accident of voice | Send plan that keeps voices distinct | Claims per brand; a stop on collisions |
| Winback is a quarterly code | Triggered recency and property affinity | Suppress the blast; stand up one honest stream |
Nested case
Hospitality · Email
Selected missions, names withheld.
Next
If this is the sector you are in, send the constraint.
A conversation. Not a deck. The mission, the team, the constraint.
Contact us