Purposes

Hospitality is the human operating system of the property. Its purpose is to make excellent service intentional and repeatable without making it feel standardized. Guests should feel recognized, relaxed, understood, and cared for, while the team remains natural, confident, and human.

The intended outcomes are:

• Guests feel like people, not reservations, room numbers, or transactions.
• The stay feels easy. Guests do not have to manage the property, chase requests, repeat themselves, or learn unnecessary procedures.
• Service feels personal without feeling invasive, scripted, formal, or overdone.
• The team anticipates needs, follows through on commitments, and resolves problems without drama.
• Guests leave feeling connected to the property, the people, and the place.

Principles

The Experience We Are Trying to Create

Luxury is not formality. It is freedom from unnecessary decisions, uncertainty, waiting, friction, and the feeling that the guest must manage the hotel. We want a guest experience that is highly attentive but unpretentious, locally grounded, and comfortable enough that genuine relationships can develop.

Service Principles and Non-Negotiables

• Guest first. When reasonably possible, pause operational work to acknowledge and assist a guest. We staff and organize the property so hospitality is not treated as an interruption.
• Thoughtful, not theatrical. We care about details because they improve how the guest feels, not because they look impressive in a standards manual.
• People, not room numbers. Guests should feel individually recognized. We learn who they are, how they like to be addressed, and what matters to them.
• No scripts. Team members are trained, knowledgeable, and practiced enough to have normal conversations. We teach judgment and examples, not memorized lines.
• Use names naturally. Learn correct names, spelling, pronunciation, and preferred form of address before arrival when possible. Use names when it feels natural, not repeatedly or mechanically.
• Anticipate, but do not hover. Notice likely needs and act when the answer is obvious. When a preference is uncertain, offer rather than assume.
• Situational awareness matters. Read body language, energy, timing, weather, group dynamics, and context. A tired guest may need a drink and a quiet room, not a tour.
• No assumptions. Important commitments, reservations, transportation, maintenance fixes, and other guest-impacting details are confirmed rather than left to chance. Trust, then verify.
• High say/do ratio. If we say we will do something, it happens within the promised timeframe. If timing changes, tell the guest before they have to ask.
• Own the outcome. The person who receives a request owns it until it is completed or clearly handed to another team member who has accepted responsibility.
• No is a last resort. If a request is reasonable, safe, legal, and feasible, look for a way to make it happen. If it cannot be done, explain why and offer the closest useful alternative.
• Share the why. Guests appreciate context. Avoid vague explanations such as 'policy' or 'safety issue' when a clear, useful explanation can be given.
• Friction is a service failure. Reduce unnecessary forms, signatures, instructions, waiting, transfers, repeated questions, and procedures that exist mainly for internal convenience.
• Personalize. Remember preferences, interests, special occasions, and prior requests when they help improve the stay. Do not collect information simply because it is available.
• Privacy and discretion are part of hospitality. Guest names, room information, schedules, preferences, problems, and personal details are shared only when needed to serve the guest.
• One team, one guest experience. Guests should not see departmental boundaries. Avoid 'that's not my area' or making the guest find the right person.
• Create connections to place. Good hospitality helps guests understand the local culture, food, people, customs, and landscape without turning the stay into a lecture or a rigid itinerary.
• Sustainability without guilt. Build sustainable choices into the operation. Do not make guests feel selfish for asking for normal service.
• Every detail communicates. Lighting, music, scent, temperature, signage, tone of voice, uniforms, staff posture, and visible clutter all affect how a guest interprets the property.
• Make information easy to use. Guest-facing instructions and printed materials should be clear, concise, visually pleasing, and readable without effort.
• Know when to step back. Hospitality includes giving guests privacy, quiet, and room to enjoy their own group. Attention is not the same as constant presence.

What We Do Not Want

• Scripted or sales-like interactions.
• Stiff, overly formal, or obsequious service.
• Staff hovering when guests want privacy.
• Staff disappearing when guests need help.
• Guests having to ask twice for the same thing.
• Excuses, blame, or internal problems being pushed onto the guest.
• Staff clustering, whispering, or holding operational conversations in guest spaces.
• Overuse of guest names.
• Generic 'luxury' gestures that are expensive but not personally meaningful.
• Rigid processes that matter more than the guest outcome.
• Guilt-based sustainability messaging.
• Overpromising in an effort to please.

Roles & Ownership

All team members own the guest experience. Management owns service consistency, escalation, and recovery. Department or workstream ownership determines who executes a task, but it does not determine who is allowed to care for a guest.

Every Team Member

• Acknowledge guests warmly and naturally.
• Notice needs, problems, and opportunities to help.
• Take ownership of requests and either complete them or make a clear handoff.
• Protect guest privacy and dignity.
• Record useful guest preferences or information in the approved guest record when appropriate.
• Escalate rather than guessing when a request is outside personal authority, expertise, or safety limits.

Host / General Manager

• Own the overall guest relationship and the consistency of the hospitality experience.
• Know the group, its key personalities, priorities, sensitivities, and open issues.
• Coordinate across teams so the property presents one coherent experience.
• Set the tone for host presence, conversation, discretion, and judgment.
• Own escalated complaints, service recovery, and exceptions that exceed normal team authority.
• Ensure unresolved requests and concerns are handed off between shifts.
• Make sure guest feedback is converted into operational learning.

Department and Workstream Owners

• Deliver the underlying product or service to the agreed standard.
• Tell the host team early when a commitment may slip.
• Provide accurate information so the guest is never given false confidence.
• Close the loop when a guest-impacting issue has been resolved.
• Identify recurring causes of guest frustration and fix the system, not only the individual incident.

On-Call Host

• Provide the property-specific level of after-hours coverage for urgent guest needs.
• Keep the approved urgent communication channel audible and monitored while on duty.
• Know when an issue can wait until morning and when it requires immediate action or escalation.
• Document important overnight issues for the next handoff.

Owners / Leadership

• Define the hospitality philosophy and the boundaries within which the team can use judgment.
• Set service-recovery and compensation authority.
• Resource the property so the service standard is realistically deliverable.
• Review recurring guest issues, feedback, and service failures for system-level improvement.

How We Operate

Guest Knowledge Before Arrival

Booking, itinerary, payment, transportation, and pre-arrival logistics belong in the Guest Journey, Sales & Marketing Playbook. Hospitality needs enough context before arrival to recognize the guests and serve them naturally from the first interaction.

• Know guest names, spelling, pronunciation, and preferred form of address when available.
• Know the primary group contact and any other people who are likely to coordinate decisions.
• Know confirmed special occasions, meaningful interests, sensitivities, and preferences that are relevant to the stay.
• Know any guest concerns or prior service issues that could affect the experience.
• Understand preferred communication style when known, including guests who want frequent interaction and guests who prefer quiet.
• Share only the information each team member needs. A guest briefing is not an invitation to gossip.

Arrival and the First Minutes

• The guest should arrive at a property that looks ready. Avoid visible scrambling, last-minute cleaning, staff confusion, or operational clutter.
• Acknowledge and greet guests immediately, even if the person who will complete the welcome is occupied.
• Use names naturally and make introductions without turning the arrival into a formal receiving line.
• Read the group's energy. If guests are tired, hot, hungry, distracted, or eager to settle in, respond to that before giving information.
• Handle immediate needs first: comfort, restroom, water or beverage, food if needed, luggage, and the ability to settle in.
• Avoid a traditional hotel check-in feeling when the property model allows it. Administrative requirements should be completed in advance or handled with minimal friction.
• Give only the orientation the guest needs at that moment. Additional information can be provided later.
• Confirm any time-sensitive plans for the day so the guest feels confident that the team is already on top of them.

Everyday Guest Interaction

• When passing a guest, make eye contact and acknowledge them unless doing so would clearly interrupt a private moment.
• When reasonable, pause the task at hand for a short interaction that leaves the guest feeling seen rather than ignored.
• Match the guest's energy. Some guests want conversation; others want a smile and space.
• Keep conversation natural. Build a broad range of topics beyond repeated questions such as 'Where are you from?' and 'What are you doing today?'
• Engage on a peer-to-peer human level while maintaining professional boundaries.
• Do not monopolize a guest's time. Know how to end a conversation gracefully.
• Do not cluster with other employees, whisper, complain, or discuss operations where guests can see or hear it.
• Use personal phones and staff devices discreetly in guest areas.
• Never make a guest feel that a request is a burden or that they are interrupting the team.

Personalization and Preference Memory

The hierarchy is preference first, observed behavior second, assumption last.

• Record useful preferences as they emerge during the stay, including beverage preferences, communication preferences, hobbies, interests, special occasions, and routines.
• Distinguish a stable preference from a one-time choice. A guest who ordered one drink yesterday may want something different today.
• Use remembered preferences to reduce friction, not to show the guest how much data has been collected about them.
• Confirm when the cost of being wrong is meaningful or when the guest may reasonably want variety.
• Share useful preferences discreetly across the team so service feels continuous rather than dependent on one employee.
• Keep guest notes factual, respectful, and service-related.
• Remove or avoid information that is not useful to serving the guest.

Anticipating Needs

• Watch for obvious needs created by weather, temperature, timing, activity, body language, and prior requests.
• Act proactively when the desired outcome is clear and low risk.
• Offer rather than assume when preference is uncertain.
• If a guest previously reported a problem, check back after the fix instead of assuming the issue is resolved.
• Notice when guests are waiting, searching for something, carrying items, looking uncomfortable, or trying to figure out how something works.
• Do not interrupt sleep, work, private conversations, or quiet time simply to demonstrate attentiveness.

Guest Communication

• Guest communication should come from a real person or clearly identified host team, not an impersonal no-reply identity whenever practical.
• Provide one obvious, easy way for guests to reach the team for requests and questions.
• Use group messaging for information that is relevant to the whole party and one-to-one messaging for personal, sensitive, or individual requests.
• Acknowledge a request promptly even when the full answer or solution will take time.
• Make ownership clear internally so multiple team members do not send conflicting or duplicate replies.
• If the promised timing changes, tell the guest before the guest has to follow up.
• Close the loop. Confirm that the request was completed and that the outcome worked for the guest.
• Keep messages concise, natural, and useful. Avoid excessive broadcasts and unnecessary operational detail.
• Move sensitive information out of group channels.
• Define property-specific after-hours and urgent communication coverage so guests know how to get help.

Requests and Unusual Requests

• Listen for the outcome the guest actually wants rather than responding only to the literal wording of the request.
• If the request is reasonable, safe, legal, and feasible, look for a way to accomplish it.
• If the answer is uncertain, escalate before saying no.
• If the request cannot be fulfilled, explain the specific reason in useful terms.
• Offer the closest practical alternative rather than ending the conversation with a refusal.
• Coordinate across teams without making the guest manage the handoff.
• Do not make commitments that exceed your authority or that the property cannot reliably deliver.
• Confirm completion and check that the solution actually solved the guest's problem.

Difficult Situations and Guest Boundaries

• Service does not require tolerating threats, harassment, unsafe behavior, illegal requests, or conduct that compromises another guest or employee.
• Stay calm, clear, and respectful. Do not argue, shame, or escalate emotionally.
• Set a direct boundary when a request or behavior is inappropriate, then involve management when needed.
• Maintain professional boundaries throughout the active guest relationship. Employee conduct rules belong in the Team & Management Playbook.
• Move sensitive or confrontational conversations away from other guests whenever possible.
• In a safety-related situation, safety takes priority over normal service preferences. Explain the reason when doing so is appropriate.
• Document serious incidents and follow the Safety, Security & Compliance Playbook.

Delights and Unexpected Moments

A delight is most effective when it feels personal, timely, and easy. It does not need to be expensive.

• Use something learned about the guest to make a small moment better.
• Look for natural opportunities connected to an activity, meal, conversation, celebration, weather change, or local experience.
• Prefer specific gestures over generic gifts.
• Do not create a spectacle for guests who prefer privacy.
• Do not use a surprise to compensate for an unresolved operational failure. Fix the failure first.
• Avoid gestures that create an expectation the team cannot repeat for the rest of the group.
• Keep a property-specific ideas library, but use it as inspiration rather than a checklist.

Problem Resolution and Service Recovery

• Receive the problem without defensiveness. Let the guest finish explaining the impact.
• Acknowledge what happened and apologize sincerely when the property fell short.
• Take ownership of the next step. The guest should not need to repeat the story to multiple people.
• Fix the underlying problem as quickly and discreetly as possible.
• Give a realistic timeframe and update the guest if it changes.
• Use recovery gestures or compensation when appropriate and within the property's authority limits. The fix matters more than the gesture.
• Follow up after the resolution to make sure the guest is satisfied.
• Record meaningful service failures and recovery actions so the next shift has context.
• Debrief recurring issues. A problem that repeats is an operating-system problem, not a series of isolated guest incidents.
• Never blame another employee, vendor, department, or the guest.

Privacy and Discretion

• Never share guest names, room information, schedules, personal details, or private requests unless the recipient needs the information to serve the guest.
• Do not discuss guests casually with other guests, friends, or people outside the property.
• Keep staff conversations about guests and operations out of public spaces.
• Do not post, photograph, tag, or otherwise publicize guests without explicit permission.
• Treat guest profiles and notes as confidential operating information.
• Write guest notes in factual, respectful language that would not be embarrassing if read by the guest.
• Use private communication channels for sensitive matters.

Hosting and Connection to Place

• We are knowledgeable hosts rather than transactional service providers.
• Help guests understand local customs, timing, food, traditions, history, and practical norms when the context is useful.
• Make personal introductions to trusted local people when it genuinely improves the experience.
• Encourage discovery without overscheduling the guest.
• Participate socially when your presence helps a group feel comfortable or connected, then step back when the group is engaged on its own.
• Explain local constraints or differences without making the guest feel foolish for not knowing them.
• The goal is not simply to show guests the destination. It is to help them understand it.

Atmosphere, Ease, and Micro-Details

• Use lighting, music, scent, fires, and other ambient elements intentionally to support the mood of the space and time of day.
• Keep guest-facing information concise and readable. For physical signs, cards, menus, and instructions, Borgo Santolina uses 14-point type as a practical minimum unless the design clearly supports equivalent readability.
• Minimize paper and wet signatures when a digital process is easier for the guest. Offer a printed version when a guest prefers it.
• Do not make guests decode internal terminology, staffing limitations, or property systems.
• Small irritations compound. Fix confusing signs, awkward instructions, unclear access, recurring waiting points, and other friction even when no single guest formally complains.

Departure and Farewell

• Departure should feel like the end of a stay with people who know the guest, not a checkout transaction.
• Before the final departure rush, give the primary guest an easy opportunity to share feedback in person and surface anything unresolved.
• Address fixable concerns before the guest leaves when possible.
• Make the goodbye sincere and personal. Team members who formed a relationship with the group should participate when appropriate.
• A farewell gift or note should be personal enough to feel connected to the stay, not a generic luxury amenity.
• Guests should leave feeling appreciated and, when authentic, missed.

Handoffs and Continuity

• A guest request is not handed off until another person has accepted ownership.
• A good handoff includes the guest, the request, relevant context, the promised timing, and anything already tried.
• Shift changes must include open guest requests, unresolved problems, important preferences, and sensitive situations that could affect service.
• Do not force the guest to repeat information the team already has.
• Avoid duplicate outreach from multiple employees.
• Present one answer to the guest. Resolve internal disagreement before communicating whenever possible.

Sustainability and Guest Choice

• Make sustainable operations the default where they do not reduce the guest experience.
• Do not use guilt-based signs or imply that normal service requests are environmentally irresponsible.
• When a genuine choice is useful, explain it neutrally and let the guest decide.
• Do not use sustainability as an excuse for cost-cutting that creates a visibly worse guest experience.

Quality & Training

Training Philosophy

Hospitality training should build judgment, awareness, confidence, and consistency. The goal is not to make every employee sound the same. Team members should understand the principles well enough to respond naturally to different guests and situations.

Core Training

• Hospitality philosophy and the intended guest feeling.
• Guest-first culture and how to balance guest interaction with operational work.
• Guest names, pronunciation, recognition, and natural name use.
• Situational awareness and reading verbal and nonverbal cues.
• Natural conversation and small-talk skills without repetitive questions.
• Preference gathering, guest-profile notes, and privacy.
• Anticipating needs without assuming or hovering.
• Handling requests, unusual requests, and saying no appropriately.
• Problem resolution, apology, service recovery, and follow-up.
• Guest communication standards across in-person, phone, email, and messaging.
• Professional boundaries, difficult situations, and escalation.
• Local knowledge and how to explain the destination with confidence.
• Clear, accessible guest-facing communication.
• Property-specific communication channels, escalation paths, and recovery authority.

Scenario Practice

• A guest arrives exhausted and clearly does not want an orientation.
• A guest asks for something the team has never been asked to do before.
• A request will take longer than originally promised.
• A guest reports a maintenance problem that another team member says has already been fixed.
• A guest is angry about something the property cannot fully control.
• A guest wants lively conversation while another member of the party clearly wants quiet.
• A staff member overhears a sensitive personal detail that could be useful to service but should remain private.
• A guest repeatedly pushes a professional boundary.
• The team knows a guest's usual preference but the guest may reasonably want something different today.
• A special occasion becomes known only after the stay has begun.
• Two team members respond differently to the same request.
• A guest appears to be waiting or confused but has not asked for help.

Daily Quality Controls

• Before a stay, ensure the team knows names, key preferences, primary contact, important sensitivities, and relevant special occasions.
• At each handoff, review open requests and unresolved guest issues.
• Maintain a simple view of open guest requests so ownership and promised timing are visible.
• Managers should observe real guest interactions and coach from actual examples.
• Check that important guest problems received a follow-up after resolution.
• Capture recurring friction points and route them to the playbook or system that owns the root cause.
• The cadence and format of staff meetings belong in the Team & Management Playbook.

Service Quality Standards

Define a small set of observable standards rather than relying only on subjective ideas of 'great service.' Useful measures include:

• Guests do not need to repeat requests.
• Every open request has a clear owner.
• Promised timelines are met or proactively updated.
• Service-recovery cases receive follow-up.
• Guest preferences are used accurately and discreetly.
• Privacy breaches are treated as serious incidents.
• Guest feedback consistently describes the team as warm, helpful, natural, and attentive.
• Recurring complaints decline because underlying causes are corrected.

Coaching and Continuous Improvement

• Coach quickly, privately, and specifically after real interactions.
• Praise judgment and follow-through, not only polished presentation.
• Do not punish employees for surfacing problems early.
• Use guest feedback as evidence, not as the only source of truth.
• Debrief significant recoveries and unusual requests so the team learns from them.
• Update this playbook when a better standard becomes clear. Detailed recurring tasks should live in the property's task or operating system rather than turning the playbook into a task list.

Property-Specific Notes

The principles above should remain stable. Each property should document the local decisions needed to make them executable.

Required Property Decisions

• Primary guest communication channels and how guests initiate contact.
• After-hours and emergency communication coverage.
• Guest-message response expectations.
• Service-recovery authority and compensation limits by role.
• Who owns guest profiles and where preferences are recorded.
• Arrival and departure rituals.
• Tipping policy and how it is explained.
• Local cultural expectations and language standards.
• The property's approach to staff social interaction with guests.
• Known privacy-sensitive guest situations and escalation procedures.
• Key ambient standards such as music, lighting, scent, fires, and quiet hours.
• Any accessibility and readability standards for guest-facing materials.
• Property-specific delight ideas and approved discretionary resources.

Borgo Santolina Reference Implementation

• Exclusive-use, fully hosted model. The team treats the group as guests of the property rather than a collection of separate room reservations.
• No traditional check-in experience. Required administrative work is completed before arrival.
• No tipping. The experience should not create moments in which guests feel they need to calculate or manage gratuities.
• WhatsApp Business is the primary guest-messaging channel, with a shared host-team inbox, group communication for the party, and one-to-one communication for individual requests.
• Guest-first staffing. Team members are expected to pause operational work for natural guest interaction when reasonable.
• Names are learned before arrival, including pronunciation when needed, and used naturally rather than repeatedly.
• Hosts interact as knowledgeable, confident humans. They may join conversation or social moments when useful, without becoming the center of the guest's experience.
• Important external commitments and guest-impacting details are re-confirmed rather than assumed.
• The atmosphere is intentional, including music, lighting, scent, fireplaces, and fire pits when appropriate.
• Guest-facing physical materials are designed for easy reading, with 14-point type as a practical minimum for signs, cards, menus, and instructions.
• Sustainability is built into the operation without guilt-based messaging to guests.