National hospitality group · Email
Booking and winback after the merge.
+27%
Direct booking from email, two quarters
2.1×
Winback reactivation vs prior year
11 weeks
CRM merge to living 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.
| 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
National hospitality group · Email
Selected work of the practice. Brands unnamed.
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