CASE STUDY · PENTA HOTELS · HOSPITALITY · SFMC + THYNK
Marketing Cloud activated for European hospitality.
Guest lifecycle
In operation
Data layer
Thynk
SFMC
Lifecycle journeys
Pre-arrival
In-stay
Post-stay
Reactivation
Mapped
Monitored
Handed over
Client
Penta Hotels
Industry
Hospitality
Service area
CRM & Lifecycle (SFMC + Thynk)
Engagement type
Project + retainer
Status
Delivered, in operation
01 — The brief
A European hospitality group running on Thynk for property management and guest data, with the marketing team needing to activate that data into a working lifecycle program in Salesforce Marketing Cloud. Pre-arrival communications, in-stay touchpoints, post-stay follow-ups, and reactivation journeys for lapsed guests — none of which existed in a coordinated way at the start of the engagement.
The ask wasn’t “set up Marketing Cloud” — it was “activate guest data into a real lifecycle program that the in-house team can run after we leave.” Different brief. Different scope.
02 — What we did
01
Platform setup
SFMC instance built from clean foundation. Sender Authentication Package configured. Data model designed to fit the hospitality use case rather than retrofitted from a generic B2C template.
02
Thynk data layer mapping
The integration work that determines whether everything downstream is possible. Guest profiles, booking events, stay history, property attributes — all mapped into Data Extensions with a structure that supports both campaign use and journey triggering. The unsexy plumbing work that has to be right before any of the lifecycle program above it can execute.
03
Lifecycle journeys
Pre-arrival (welcome, check-in instructions, optional upsell), in-stay (concierge touchpoints, mid-stay engagement), post-stay (review request, retention), reactivation (win-back for lapsed guests). Each journey owns its goal, its exit criteria, and its measurement.
04
Deliverability and infrastructure
Sender profiles configured, DKIM and DMARC alignment, inbox placement monitored across providers. The work that nobody finds sexy until the inbox numbers are back where they should be.
05
Documentation and handover
Every component documented — runbook, template library, journey diagrams, escalation paths. Loom walkthroughs of every system. Training for the in-house marketing team. The handover doc you’d actually want to inherit.
03 — How the engagement runs
Fixed-price project for the build. Lighter retainer afterward for ongoing operation — new journey types, template iterations, structural changes as the group’s needs evolve. The internal team owns campaign delivery and day-to-day journey management; we handle structural work and Thynk integration evolution.
04 — What changed
“
Guests get communications timed to their actual stay rather than generic marketing blasts. The marketing team owns the day-to-day, with documented infrastructure underneath that doesn’t depend on tribal knowledge.
The bigger change: this engagement became the template for our productized Hospitality offer. The architecture, the Thynk-to-SFMC mapping, the journey design — Penta was the proving ground that informed how we now sell hospitality SFMC implementations across the category. Other hospitality groups running on Thynk benefit from the work that was done here, even if they never see the original engagement.