Guests change reservations, ask about amenities and make requests through AI agents connected to property systems, while staff handle recovery and personal touches.
Agentforce lets hotels, resorts and venue operators give guests an agent that does more than answer FAQs. Connected to reservation and property management systems, it can modify dates, add a room request, confirm a late checkout within policy, book a spa or dinner time and answer questions about parking or pets. For sales teams, agents can qualify group and event inquiries and prepare them for a sales manager. Complaints, service recovery and guests who simply want a person are handed to staff with the conversation context, so the guest never repeats themselves.
Hospitality service is judged by how it feels, not just whether the answer was right. Guests tolerate automation for simple logistics but expect a person when something goes wrong or when they are celebrating. Operations are also fragmented: properties may run different systems, brands and franchise arrangements, and rates and availability change constantly. Agentforce fits when agents handle transactional requests through live connections to reservation and property systems, carry the brand's voice through carefully written instructions and recognize emotional moments that call for staff. Multi-property groups add a routing question, since a guest message may need to reach a specific property's front desk rather than a central team that cannot act on it.
Guests change arrival dates, add nights, switch room types or add a guest. An agent can check availability and rate rules in the reservation system, explain any price difference and make the change once the guest confirms. Cancellations follow the booked rate's policy, and exception requests route to reservations staff who decide on waivers. Every change is written back to the reservation so the front desk sees it at arrival.
Before a stay, guests ask about early check-in, cribs, accessibility needs, dietary restrictions and celebration setups. An agent can record requests on the reservation, book available add-ons and tell the guest honestly which requests are confirmed and which depend on availability. Property teams then see those requests in their daily arrivals reports. Requests that need a property decision, such as a guaranteed connecting room, go to the front office.
Wedding, meeting and group requests arrive with incomplete details. An agent can collect dates, a headcount range, room block needs, space requirements and budget, then create an opportunity for the right sales manager. It does not quote group rates or hold space, which depend on revenue management decisions that people make. Inquiries arriving after the sales office closes still get a prompt, useful reply.
During a stay, guests message about towels, noise or a broken air conditioner. The agent creates a task for housekeeping or engineering at the correct property and keeps the guest updated. When the tone signals frustration or a complaint is serious, it hands off to the duty manager, who decides on any recovery gesture. Reports on these requests also show engineering which rooms generate repeat issues.
Hospitality agents need a guest profile that survives across stays and properties, which often means Data Cloud unifying reservation, loyalty, point of sale and survey data. The property management system and central reservation system remain authoritative for stays, rates and inventory. In Salesforce, decide how properties are represented, since routing, knowledge and staff queues all depend on it. Service requests should be classified by department so housekeeping, engineering and front desk tasks land correctly. Knowledge must be property-specific, because pool hours, parking rules and pet policies differ, and an agent answering from brand-level content will misinform guests.
Provides in-house guest, room and folio details and receives the service tasks and requests the agent records during a stay.
Supplies availability, rate rules and booking records, and processes agent-initiated modifications within the changes each rate permits, including deposits and cancellation terms.
Receives qualified group and event inquiries, or syncs with Salesforce opportunities, so sales managers can check space and propose terms.
Agent instructions should reflect how the property speaks to guests, whether formal, playful or somewhere between. Test responses with front office leaders, avoid overly apologetic or robotic phrasing and make sure the agent never promises amenities or upgrades that staff cannot deliver.
Complaints, special occasions, accessibility concerns and loyalty members with elevated status often deserve a person. Define triggers that move these conversations to staff quickly, and make sure each property has someone monitoring handoffs during the times guests are actually messaging.
In branded portfolios, guest data may be shared among brand, owner and management company under specific agreements. Settle who owns guest profiles and conversation data, what each property may see and how agents behave across brands before designing a shared agent.
Yes, within reason. An agent can offer available upgrades, packages or dining reservations when they relate to the guest's request, using offers set by revenue management. Keep offers relevant and occasional, because an agent that pushes add-ons in every message irritates guests. Let property staff adjust which offers the agent may present. Track which offers guests accept, by property, to refine them.
The answer turns on what each system exposes. Many modern property and reservation systems provide APIs that agents can use through actions or MuleSoft. Older on-premise systems may limit what agents can do in real time. We assess integration options early, because they determine which guest tasks an agent can actually complete. Where real-time access is limited, agents can still collect requests for staff to complete.
Usually one agent framework with property-specific knowledge and routing works best. Guests experience a consistent brand, while answers about amenities, policies and local details come from each property's own content. Group sales may run as a separate agent, since its audience and questions differ from those of transient guests. Central teams maintain the framework while properties own their content.
Agents can respond in multiple languages, which helps properties that serve international travelers. Knowledge articles should still be reviewed in the main languages your guests use, since translated policy terms can introduce errors. Handoff paths should reach staff who speak the guest's language wherever that is possible. Test key policies, such as cancellation terms, in each language before launch.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.