What changes when the third property comes in
With one hotel, review management is a marketing topic. The owner or hotel manager replies herself, knows every guest, writes the reply on Sunday afternoon over coffee. With two houses it becomes routine, sometimes late, but still bearable. With three houses the system breaks.
Not first visible in the review stars — visible in the internal time arithmetic. 4 to 6 hours per house of review upkeep per week. At three houses that's 12 to 18 hours. At seven — as some mountain-region collectives in Grisons and Valais know — it's 28 to 42 hours per week. That's a full-time job for something that doesn't directly drive revenue.
This piece delivers the playbook for exactly that situation. Not from a specific customer case (Trophy has no multi-location hotel customers we can publish by name) — but from industry patterns drawn from audits, association data, and observation of Swiss hotel chains.
The multi-location trap
When a collective continues to run the first two houses with the same mechanic as a single hotel, this happens:
- Separate profiles, separate replies. Each house maintains its own photo pool, its own reply templates, its own Q&A answers.
- Escalating upkeep time. What the owner still did at two houses migrates at three either to the location manager (who has other priorities) or stagnates.
- Inconsistent tone. When location A replies in informal Swiss style and location B in formal style, the collective looks unprofessional as soon as a guest checks both profiles.
- Photo quality spread. Location A has a marketing-savvy manager and a nice photo gallery, location B posts smartphone snapshots. It shows.
- Crisis escalation unclear. When a 1-star review with extortion threat comes in, nobody knows who decides — location management, the central GM, or whether legal needs in.
That's the trap. You don't get out of it through "more attention" — only through a clear operations playbook.
What must be centralised
Three things belong unequivocally with central (whether holding, CEO, or a dedicated reputation team):
1. Tone-of-voice guide
A written document binding for all locations:
- form of address (Sie / Du / Lei / formal vous)
- word-choice list with forbidden words ("unfortunately", "of course", "however", "dear Mr/Ms")
- mandatory words ("you're right", "that's on us", "specifically")
- language order (Italian first for Italian reviews, German fallback)
- reply length by review (5–7 sentences for 1–2 stars, 3–4 for 5 stars)
This guide is a living document — reviewed and adjusted every 6 months.
2. Escalation rules
A clear table of who replies to which review:
- 5 stars, no staff name: location management, template, max. 24h
- 5 stars with staff praise: location management, personalised, max. 48h
- 3–4 stars with concrete criticism: location management, individual, max. 72h
- 1–2 stars, factual criticism: location management with central review, max. 72h
- 1–2 stars, personal accusations against staff: central, max. 72h
- 1–2 stars with extortion hint: central + lawyer, max. 48h
- Negative press mention: CEO, immediate
3. Photo library system
Central cloud library with:
- minimum quality standards (resolution, format, lighting)
- mandatory categories per location (exterior, lobby, standard room, deluxe, restaurant, wellness if applicable, team)
- recency rule (no photo older than 18 months)
- professional photo rotation: a photo session per house every 2 years
What must stay decentralised
Not everything belongs at central. Three things continue via the location, otherwise authenticity breaks:
- Staff first names. Anyone mentioning a service team member by name needs to know the name. That runs through location management.
- Local specifics in replies. When a guest writes "the view from room 304 was fantastic", the reply must know that room 304 faces east. Local knowledge isn't scalable.
- Seasonal events and specialties. Location-specific posts (weekend wine pairing, ski-school partnership) stay with the location, because they're only really felt there.
The 6 KPIs to track monthly
Without numbers, it's not an operations topic, it's wishful thinking. Six KPIs per location, captured monthly:
- Number of new reviews (target: 4 to 8 per month per house, depending on size)
- Average star count (trend matters more than absolute number)
- Reply rate (target: over 95% of all reviews)
- Reply latency (target: 90% under 72 hours)
- Review sentiment categories (service, food, room, cleanliness — where do critical clusters form?)
- Escalation cases (number of extortion attempts, fake reviews, flagged reviews)
These six numbers in a 1-page monthly dashboard is enough. Anyone tracking more builds bullshit statistics. Anyone tracking less doesn't know where the collective stands.
Role structure
In a multi-location operation, three roles run in parallel:
- Location management: responsible for review replies in the standard range (3–5 stars), photo delivery to central, local Q&A answers.
- Central reputation team (1 person from 5 houses onward): responsible for escalations, tone-of-voice upkeep, photo library standards, KPI reporting to the leadership team.
- CEO / GM: decides on crisis escalations, runs the quarterly reputation review.
From 3 houses: the central role is part-time (20–40% of a person), which can also be covered via an external agency or a specialised software solution like Trophy.
How much time the playbook saves
With the playbook running cleanly, upkeep time per location drops from 4 to 6 hours to 1 to 2 hours per week — because standardisation automates 70% of reply creation. At three houses, that's 9 to 12 hours saved per week; at seven houses, 21 to 28 hours. That's half to a full staff member's hours.
Pricing bridge to multi-location discount
Trophy offers a multi-location discount from the second location onward. From three or more locations, the reputation team module is added on top, which takes over the central functions from this playbook. Details: packages and pricing.
Sources disclaimer
The playbook is based on industry patterns and Trophy mechanics. No single customer collective is dressed up as a showcase case.