Who this is for
Group head of guest experience, group communications office, corporate compliance and legal, district managers, corporate systems team and the Suite Profit onboarding architect assigned to the portfolio. Property front-office teams become inbox operators inside the district-manager portfolio inbox rather than autonomous Meta account owners.
Prerequisites
- Meta Business Manager parent account under the group operating entity, with the CIO office as owner.
- Register of every operating entity in the portfolio and which brands / properties each entity owns.
- Corporate directory groups for reception operators, duty managers and district managers, provisioned into the Suite Profit operator console over SCIM.
- Approved brand voice register from the group brand office — one voice preset per brand.
Step 1 — WABA business verification per corporate entity
Meta requires business verification per legal entity. For each Sp. z o.o. in the portfolio, the corporate compliance team uploads a certified KRS extract dated within 90 days, a utility bill, and the entity's NIP registration. Where a single operating entity owns multiple brands, one WABA covers all of them under child business accounts. Where different entities own different brands, a separate WABA is verified per entity. Verification typically takes two to four business days per entity.
Step 2 — Template pre-approval process
The group communications office authors a portfolio template catalogue in the Suite Profit operator console: booking confirmation, pre-arrival D-5, digital check-in D-1, upsell D-1, on-property service, invoice link, post-stay review request and district-manager escalation. Each template exists in English and Polish, with additional languages by brand (German for the Silesian and Trójmiasto brands, French for the Warsaw MICE brand). Templates go into a signed pre-approval workflow before submission to Meta: legal review, brand review, group communications sign-off. Meta review then runs 12 to 48 hours.
Step 3 — Per-brand voice presets
Every brand in the portfolio maps to a voice preset that controls tone, formality and signature block on outbound templates:
- Heritage voice — formal salutations, full property names, restrained emoji use.
- Contemporary voice — warm salutations, single-word signatures, curated emoji palette.
- Business voice — brief, calendar-referenced language for corporate and MICE guests.
- Leisure voice — conversational, referencing local destination touches.
The voice preset is applied automatically per property; front-office operators cannot mix presets by accident.
Step 4 — District-manager portfolio inbox
Every property inbox is stitched into a single district-manager portfolio inbox. District managers see conversations for their cluster of three to six properties in one interface, filtered by property, brand, guest stay stage, sentiment and escalation status. The portfolio inbox surfaces the same conversation to the property front-office operator under their scoped view, so the district manager oversees without duplicating the reception's work.
Step 5 — Escalation queue routing rules
Escalation is governed rather than ad-hoc. The Suite Profit operator console holds a routing tree:
- Reception operator first-response window — 5 minutes 07:00 to 23:00 local, 15 minutes overnight.
- Duty manager escalation if not first-responded inside the window.
- District manager escalation on complaint sentiment or on VIP-tagged guests.
- Group head of guest experience escalation on brand-safety or reputation-risk keywords.
The routing tree is versioned; every escalation event is logged to the Portfolio Reputation Console and available for post-incident review.
Step 6 — KPI alignment on the portfolio dashboard
Every property in the portfolio surfaces the same guest-experience KPIs: opt-in rate at booking, D-5 pre-arrival open rate, response rate, first-response time, resolution time, escalation rate and post-stay CSAT lift. The group head of guest experience uses the dashboard to compare properties on like-for-like terms and to identify districts that need coaching versus districts that need operator load-balancing.
Estimated timeline
For a portfolio of three to fifteen properties, initial rollout runs six to nine weeks: two to three weeks of WABA verification per corporate entity, one to two weeks of template authoring and pre-approval, two weeks of per-brand voice preset configuration and district inbox setup, and a two-week measured pilot on one property per brand before the portfolio-wide switch.