WITHIN AN AUTOMATED GUEST SATISFACTION AND SERVICES SCHEDULING SYSTEM

RELATED APPLICATION

This application claims priority to U.S. Provisional Application No. 62/823,474, filed on March 25, 2019, entitled AUTOMATED GUEST SATISFACTION AND SERVICES SCHEDULING SYSTEM, by Kevin Bidner, the contents of which being 5 incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to hotel management systems, and, more particularly, to managing hotel guest departures within an automated guest satisfaction and services scheduling system. io BACKGROUND

Guest satisfaction is paramount to hotel operations. Sophisticated travelers expect top-notch service and flawless execution of operations during their stay. It is thus important for hotels to monitor guest satisfaction, and to manage expectations and remediation efforts. This is especially true in today’s social media environment, where is ratings and reviews are critical to the success of a hotel.

At the same time, much of a hotel’s success is also based on the ability to efficiently manage and schedule services such as housekeeping. Since guests each have their own schedules, including check-in time, check-out time, and times when they are out of their hotel rooms, scheduling such services can often be a difficult task.

20 Inefficiencies can also be exacerbated when guests leave“Do Not Disturb” signs on their doors or remain in their rooms during housekeeping hours, resulting in the potential for service overstaffing and/or becoming bothersome to a guest’s experience. SUMMARY

The techniques herein are directed generally to managing hotel guest departures within an automated guest satisfaction and services scheduling system. Specifically, the systems and methods described herein may be implemented in a hotel by providing a communication terminal in each guest's assigned room. Such devices may communicate with a server and software system to provide on-demand access to both static and dynamic information and provided content. An interactive interface on the

communication terminals provides coordination between the guest and the hotel to thus manage guest satisfaction and service scheduling, accordingly.

In the present disclosure, for instance, the techniques herein provide a method and system to allow guests to easily manage and schedule their departure (check-out) through the interactive interface. The interface may include various modal notifications regarding check-out options, such as requesting the guest to enter their departure time preferences. The system also facilitates notification of a housekeeping services scheduler, and further allows the hotel to incentivize or monetize different check-out times.

In one particular embodiment, a system herein comprises: a server; and a plurality of communication terminals in communication with the server, each of the

communication terminals having a graphical user interface (GUI) and being associated with a respective room of a plurality of hotel rooms of a hotel; wherein the server is configured to receive registration information when a guest checks into the hotel, the registration information including an identification of the guest and a particular assigned room of the plurality of hotel rooms; wherein the server is configured to identify a particular communication terminal of the plurality of communication terminals that is associated with the particular assigned room; wherein the particular communication terminal is configured to present an interactive interface on a corresponding GUI of the particular communication terminal, the presented interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time; wherein the particular

communication terminal is configured to receive a selection of a particular checkout time and to share the selection of the particular checkout time with the server; and wherein the server is configured to provide the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

In another particular embodiment, a method herein comprises: receiving, at a server, registration information when a guest checks into a hotel, the registration information including an identification of the guest and a particular assigned room of a plurality of hotel rooms of the hotel; identifying, by the server, a particular

communication terminal of a plurality of communication terminals in communication with the server that is associated with the particular assigned room, wherein each of the communication terminals has a graphical user interface (GUI) and is associated with a respective room of the plurality of hotel rooms of the hotel; causing, by the server, the particular communication terminal to present an interactive interface on a corresponding GUI of the particular communication terminal, the presented interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time; receiving, by the server from the particular communication terminal, a selection of a particular checkout time; and providing, by the server, the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

In still another particular embodiment, a method herein comprises: receiving, at a particular communication terminal of a plurality of communication terminals, identification of a guest, wherein the particular communication terminal is associated with a particular room of a plurality of hotel rooms of a hotel, and wherein the guest has checked into the hotel and has been assigned to the particular room; presenting, on a corresponding graphical user interface (GUI) of the particular communication terminal, an interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time; receiving, on the interactive interface, a selection of a particular checkout time; and sharing, from the particular communication terminal, the selection of the particular checkout time with the server to cause the server to provide the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

Other embodiments of the present disclosure may be discussed in the detailed description below, and the summary above is not meant to be limiting to the scope of the invention herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein may be better understood by referring to the following description in conjunction with the accompanying drawings in which like reference numerals indicate identically or functionally similar elements, of which:

FIG. 1 illustrates an example system in accordance with one embodiment;

FIG. 2 illustrates an example system in accordance with one embodiment;

FIG. 3 illustrates an example housekeeping scheduling routine in accordance with one embodiment;

FIG. 4 illustrates an example of housekeeping notification channels in accordance with one embodiment;

FIG. 5 illustrates an example method in accordance with one embodiment;

FIG. 6 illustrates an example method in accordance with one embodiment;

FIG. 7 illustrates an example system in accordance with one embodiment;

FIG. 8 illustrates an example interactive interface in accordance with one embodiment;

FIG. 9 illustrates an example simplified procedure for managing hotel guest departures within an automated guest satisfaction and services scheduling system in accordance with one or more embodiments described herein, particularly from the perspective of a system of a hotel server; and

FIG. 10 illustrates another example simplified procedure for managing hotel guest departures within an automated guest satisfaction and services scheduling system in accordance with one or more embodiments described herein, particularly from the perspective of a communication terminal.

DESCRIPTION OF EXAMPLE EMBODIMENTS

As noted above, guest satisfaction is paramount to hotel operations, as is the ability to efficiently manage and schedule services and resources. For instance, guests have their own expectations and tolerances, as well as their own schedules, including check-in time, check-out time, and times when they are out of their hotel rooms.

Typically, for instance, hotel housekeeping services may staff the personnel needed to clean every occupied room each day, but this could easily result in frequent overstaffing and schedule inefficiencies. With no way to predict which guests might hang a "Do Not Disturb" tag or remain in their room, a hotel must plan for the heaviest workload, and housekeeping personnel must walk the halls several times a day, until all rooms are finished. A room physically occupied by a guest may need to be visited several times, and one last check might be needed to confirm that rooms not to be disturbed earlier in the day are still tagged as "Do Not Disturb."

In addition to overstaffing and inefficiency, a conventional housekeeping model may detract from the guest experience. Even guests who have opted out of housekeeping services may be disturbed by housekeeping personnel knocking on doors when the guest is in the room. Many people would prefer privacy but do not have an appropriate opportunity to inform the hotel of that preference.

Furthermore, hotels would benefit greatly from real-time monitoring of guest satisfaction, in terms of swift remediation efforts as well as to potentially capitalize on positive reviews on associated social media platforms. However, without a system in place to provide effective communication with guests of all different levels of

sophistication and/or attentiveness, many opportunities to correct a problem or to obtain a helpful review go missed.

The techniques herein, therefore, provide a system and method for managing hotel guest departures within an automated guest satisfaction and services scheduling system. In particular, the techniques herein provide a method and system to allow guests to easily manage and schedule their departure (check-out) through the interactive interface. The interface may include various modal notifications regarding check-out options, such as requesting the guest to enter their departure time preferences. The system also facilitates notification of a housekeeping services scheduler, and further allows the hotel to incentivize or monetize different check-out times.

Notably, "LAN" refers to a local area network, which is a computer network that interconnects computers within a limited area, such as a residence, a business, or an office building. Also, "PMS" refers to a property management system, which is a platform that enables a hotel or group of hotels to manage front-office capabilities, such as booking reservations, guest check-in/check-out, room assignment, managing room rates, billing, food and beverage operations, housekeeping and maintenance management, sales and catering, and revenue management.

One medium a hotel may use to deliver on-demand, customized content to hotel guests is a hotel-wide communications network based on placing communication terminals in every hotel room. These communication terminal may be a tablet computing device owned, rented, leased or licensed by the hotel, dedicated to an assigned room and configured with applications specific to guest interaction, as well as basic tablet computing functionality such as a touch screen, speakers and microphones, and network connectivity. Communication terminals may be off-the-shelf tablet computers, custom communications consoles, touch-screen televisions with wireless connectivity, or even systems similar to smart home controllers where a small computing module allows a guest to control audiovisual and other connected devices in their assigned room (e.g., speakers and televisions, lights, curtains, etc.) via the interface and/or voice recognition, optionally with various additional machine learning / artificial intelligence capabilities.

To send customized content to specific communication terminals, a hotel may install a centralized control system for all communication terminals, in the form of a hotel server. The hotel server may be a dedicated server, programmed specifically for the task of determining information for a specific guest and providing appropriate configuration commands to the communication terminals. The hotel server may receive inputs from existing data repositories, such as a PMS, member profile databases, a loyalty rewards program database, other databases available over the Internet, and digital libraries of existing content. Based on inputs received, the hotel server may configure

communication terminals throughout the hotel to load and display on-demand the content specifically targeted toward a guest accessing the communication terminal in their assigned room, particularly as described below.

Referring to FIG. 1, the system 100 in one embodiment comprises a PMS 102, a hotel server 104, one or more guest information databased, such as a guest profile database 110 and a loyalty rewards program database 112, an Internet 114, a hotel LAN 116, communication terminals 118, a guest services entity 120, and an automated scheduler 122. In such an embodiment, the hotel server 104 may include a processor 106 and a memory 108 configured to implement the method disclosed herein. The

communication terminals 118 may alternately or additionally include a processor 106 and memory 108 configured to implement the method disclosed herein.

The PMS 102 may be the administration and accounting system used by the hotel to identify guests, assign rooms at check-in, and store a record of a guest's registration information. The PMS 102 may be a server or database that resides within the hotel or at a remote location. The PMS 102 may have a wired or wireless communications connection to the hotel server 104. Through the communications connection, the PMS 102 may notify the hotel server 104 that a guest has been registered, and transmit pertinent registration information, such as the guest's name and assigned room.

The hotel server 104 may be a server installed in the hotel or remotely in the Cloud that manages the configuration of communication terminals 118 to load customized content. The hotel server 104 may have a wired or wireless connection to the Internet 114, allowing communication with a guest profile database 110 and an online loyalty rewards program database 112. The hotel server 104 may connect to the communication terminals 118 through a hotel LAN 116, or if the hotel server 104 is remotely located, through the Internet 114. The hotel server 104 may signal the communication terminals 118 to provide device addressing and guest room details. The mechanisms that accomplish this are shown in greater detail in FIG. 3. The guest profile database 110 may store information pertaining to guests who have visited the hotel or affiliated hotels in the past. This information may include a guest's preference settings (e.g., wakeup call times, room temperature, and housekeeping services), as well as other information such as personal information (e.g., name, address, demographics, etc.). Access to this database, for example, may allow the interactive interface created for a guest to offer a guest's previous selections as default options in selection menus, among other things.

The loyalty rewards program database 112 may store information pertaining to guests who hold membership in the hotel's customer loyalty program. Customer loyalty information may comprise the guest's name and contact information, a customer loyalty program ID number, and categorization within one or more loyalty tiers (e.g., gold membership or platinum membership). Customer loyalty information may also include details about the guest's history with the hotel, hotel chain, and any other participating partners. For example, the loyalty rewards program database 112 may store a record of nights stayed at the hotel, miles traveled on a partnered airline, or money spent on a loyalty credit card, and the rewards thereby earned. Information from the loyalty rewards program database 112 may be integrated into the interactive interface customized for a guest, such as, for example, in order to offer loyalty rewards program points or privileges as an incentive for forgoing housekeeping services, as described below.

Notably, either of the databases 110 and 112 above may be a public or private database residing at the hotel or at a remote location. In some embodiments, the either of the databases may also be integrated with the PMS 102, allowing the hotel to send information directly to the hotel server 104, with no database query needed.

The communication terminals 118 may be located in each hotel room and may incorporate real-time voice and data communications, with the capability for both unidirectional (one-way) broadcast and bidirectional (two-way) interaction with the guest. As noted above, these devices may be off-the-shelf tablet computers or custom communications consoles, or they may also be smart home-style systems. The communication terminals 118 may accept a control signal from the hotel server 104 indicating how they may boot up. The hotel LAN 116 may be a closed hotel intranet carried over wired or wireless data channels, or any other communications channel in place throughout the hotel. The hotel LAN 116 provides connection between the hotel server 104 and the communication terminals 118.

The hotel server 104 may receive a signal back from the communication terminals 118 indicating a guest's choices, such as with regard to when they wish to schedule housekeeping services, when they desire to check out, or other selections, as described further below. The hotel server 104 may communicate the guest response to a guest services entity 120. This may be an automated scheduler 122 that receives a signal containing the pertinent information and automatically updates a scheduling database or similar application. Alternately, the communication may be in the form of an email to a person or entity, such as those responsible for staffing and planning housekeeping services each day, review platforms, and so on. In some embodiments, the hotel server 104 may update the guest profile database 110 with this information.

Referring to FIG. 2, the system 200 in one embodiment comprises a PMS 102, a hotel server 104, a guest profile database 110, a loyalty rewards program database 112, a content database 210, and a communication terminal in an assigned room, hereinafter “communication terminal 212”. The hotel server 104 may contain logic for a query engine 202, a device address lookup table 204, and a user response handler 208. The communication terminal 212 may include a question gate 206, a communications terminal configuration engine 214, a formatting engine 216, a content selector 218, an interface builder 220, a GUI engine 222, and a device display/user interface 224.

The query engine 202 in the hotel server 104 may receive a guest's name (or other identification, such as a username, account number, etc.) from the PMS 102 upon check in and may send queries to the guest profile database 110 and loyalty rewards program database 112. Results of these queries may include the guest's loyalty tier level, loyalty rewards points accrued, and purchase history related to the loyalty rewards program, as well as a guest's preferences indicated and/or learned during previous stays at the hotel or its affiliated properties or other pertinent information. Query results may be used to generate a guest identification signal that may contain guest and loyalty data in an assigned room to select customized content as indicated by the query results, as described herein.

The hotel server 104 may also receive the guest's assigned room number from the PMS 102. This assigned room number may be sent to a device address lookup table 204 that may provide addressing information needed to signal the correct device (in this case, the communication terminal 212). The device address may be an IP address assigned by the hotel LAN, a MAC address programmed into a network adapter installed in the communication terminal, or some other unique address by which the device can be distinguished over the hotel LAN 116. The device address is sent over the hotel LAN 116 to configure the addressed communication terminal device to boot and configure its interactive interface as directed.

The communications terminal configuration engine 214 may receive the guest identification signal from the hotel server 104. The communications terminal

configuration engine 214 may execute a set of commands instructing the communication terminal in assigned room 212 to start up. The communications terminal configuration engine 214 may also configure the communication terminal in assigned room 212 to display the interactive interface based the guest information provided to it by the hotel server. All communication terminals 118 may have the same content from which to choose, or else may be based on other formatting/content criteria.

Content that a hotel wishes to present to its guests may be stored in a content database 210. This content is available to each communication terminal. Updates to content in the content database 210 may be automatically pushed down to communication terminals, or the communication terminals may be programmed to periodically monitor the content database 210 for added, removed, or modified content. Content may also be updated multiple times in a draft state or "sandbox" area and be sent to communication terminals only when it is approved and published through a content management platform.

The communication terminal 212 may import content from the content database 210. Content transmitted to the communication terminal 212 may be sent to a formatting engine 216. The formatting engine 216 may recognize content tagged as being already compatible with interactive interface requirements. Compatible content may be sent directly through with no modification. Files sent with no tagging or tagging that indicates a possible incompatibility may be ignored.

Formatted content may be customized for a particular guest by passing through a content selector 218. A content selection signal generated by the communications terminal configuration engine 214 based on the content received from the communication terminal 212 may be used to filter the content and construct an interactive interface appropriate for each individual guest.

Selected content may be sent to an interface builder 320. The interface builder 320 may generate a graphical user interface (GUI) using markup code, such as HTML or XML. The GUI may also be implemented as machine logic, such as JavaScript, that may be integrated into a browser or other web-based application installed on the

communication terminals, or as a non-transitory machine logic configuration for operating a computer processor. This interface, when instantiated by the processor may comprise links, buttons, text interface, and graphics. The interactive interface may also provide instructions and functionality allowing the guest to access a Web page or complete a simple form in order to take advantage of an offered (e.g., loyalty-based) reward.

A GUI engine 222 may be used to transmit the interactive interface to a device display/user interface 224. In a preferred embodiment, the device display/user interface 224 may be a touch screen capable of passing a user input signal back to the GUI engine 222. The GUI engine 222 may interpret user input as a menu selection, such as described herein.

Operationally, the techniques herein provide for managing hotel guest housekeeping, satisfaction, and departures within an automated guest satisfaction and services scheduling system. Each component of the system may operate independently or in conjunction with one another, and any hotel system need not implement all of the systems and methods described herein. According to a first component of the automated guest satisfaction and services scheduling system described herein, the techniques herein provide an automated housekeeping scheduling service for a hotel based on guest input and history. Information from a guest record generated at check-in may be used to configure and activate an interactive interface implemented on a communication terminal in the guest's assigned room. Guest registration information may include the guest's name, assigned room, and stay duration. The guest registration information may be provided by a property management system (PMS) used by the hotel to manage guest reservations and other hotel services.

The stay duration information may comprise the guest's time of check-in, as well as the guest's anticipated date and time of check-out. The check-out time may default to the hotel's standard check-out time or may indicate that a late check-out has been requested. If the stay duration includes only one night, the automated housekeeping scheduling system may immediately schedule housekeeping for a time after the stay duration has ended. No additional steps need be followed, unless the stay duration is extended during the guest's stay. Such an extension may include adding one or more additional nights, which may trigger the process for a longer stay duration. An extension may also include an approved request for late checkout, which may immediately reschedule housekeeping for a later time as needed.

For stay durations that include more than one night, the system may use the guest's assigned room information to identify a communication terminal located in that room.

The guest name and/or unique identification number may be used to query a guest profile database, loyalty rewards program database, and other databases that might contain information that may be used to customize a guest's interactions with the communication terminal in their assigned room. In some embodiments, a guest profile database may include guest housekeeping preferences based on the guest's previous interactions when staying at the hotel (e.g., learned and/or set). These may be used to set a default option to be displayed on the communication terminal through the process below, so that the guest may easily indicate a preferred housekeeping services option. Information from a loyalty rewards program database may be used to customize the guest's interactions based on the guest's loyalty rewards eligibility.

Guest registration information may be used to construct an interactive interface that may be implemented on the communication terminal in the guest's assigned room. The interactive interface may be a graphical user interface (GUI) that displays any information the hotel has identified as being of interest to their guests. For the purposes of the method disclosed herein, the interactive interface may include a modal window prompting the guest to select a time frame during which they would prefer housekeeping services be scheduled for their room (e.g., a preferred housekeeping services time slot of lpm-3pm the following day), or to elect to forgo housekeeping services during their stay. This window may remain active on the device display screen until a selection has been made. An incentive may be offered for guests that forgo housekeeping services. The incentive may include loyalty rewards program points for guests who participate in a loyalty rewards program. The incentive may include a voucher for use at a shop or restaurant or other business affiliated with the hotel. Guests may be offered a list of incentives to choose from once they have opted to forgo housekeeping services.

After the interactive interface implementing these customizations has been constructed, the communication terminal in the assigned room may be configured to display the customized interactive interface. The guest may be prompted as described above to select a time frame for housekeeping services or to elect to forgo housekeeping services. The guest may enter their response using the communication terminal touch screen. The guest's response may be communicated to a housekeeping services scheduler. The housekeeping services scheduler may be an automated scheduling application that accepts a signal that includes the assigned room and the guest's preferences and updates a scheduling database accordingly. The housekeeping services scheduler may be a software program that has an integration with the hotel's system, or could be a person who receives guest responses as emails from the automated scheduling system, either individually, or as an aggregated report at the end of the day. The automated scheduling system may also be configured to use the guest response to update the guest housekeeping preferences in the guest profile database. The housekeeping services scheduler may use the signal, email, or other notification the automated scheduling system may be configured to transmit, to staff and plan for upcoming housekeeping services' needs.

Referring to FIG. 3, in block 302, a routine 300 receives registration information when a guest checks into a hotel, wherein the registration information includes the guest's name, assigned room, and stay duration. In block 306, routine 300 identifies a

communication terminal installed in the assigned room. In block 308, routine 300 constructs interactive interfaces, wherein the interactive interfaces are graphical user interfaces (GUIs) for display on the communication terminal in the assigned room. In block 310, routine 300 configures the communication terminal to display the interactive interface indicated for the assigned room. In block 314, routine 300 asks the guest if housekeeping is needed during the stay duration (e.g., and at what preferred time, if so). In block 316, routine 300 receives a response from the guest. In block 318, routine 300 communicates the response to a housekeeping services scheduler (e.g., a preferred time, or forgoing service). In block 320, routine 300 schedules housekeeping services using the housekeeping services scheduler based on the response from the guest.

The automated scheduling system herein may also interface with visual notifications that may be installed for each guest room. For example, a corridor of guest rooms may be configured with a lighted display at each door and proximity sensors mounted along the corridor. The proximity sensors may be infrared sensors. As the sensors sense the approach of a housekeeping cart, the lighted display may light up green to indicate that the specific room requires housekeeping attention and is empty. If the guest has opted out of housekeeping services, the display may remain off. Motion sensors within the room or sensors, such as microphones, in the communication terminal may be configured such that, if a guest presence is detected in the room, the lighted display may light up yellow or red to indicate that housekeeping services may be postponed. In this manner, the automated scheduling system may be used to allow housekeeping personnel to more efficiently perform their tasks without disturbing guests, providing for both more effective scheduling and a better guest experience. Referring to FIG. 4, the housekeeping notification channels 400 that the automated scheduling system may utilize may comprise communication with a room alert controller 404, a signal 416 to an automated scheduler 122, an email 414 to a guest services entity 120, or some combination of these and other elements.

As discussed above, communication terminals 118 in assigned rooms may communicate guest interactions over a hotel LAN 116 with a hotel server 104. These interactions may include responses to queries about when the guest would like to schedule housekeeping services. Such responses may be communicated as a signal 416 to an automated scheduler 122 in order to automatically update a housekeeping planning system. Guest responses may also be used to generate an email 414 reporting guest housekeeping preferences to a guest services entity 120. In an embodiment, the guest responses may be sent to an Application Programming Interface (API) provided by the guest services entity 120. The guest services entity 120 may be a computerized system or a person or entity that schedules staff and plans tasks for upcoming housekeeping work.

In addition to these notifications, the communication terminals 118 or hotel server 104 may interact with a room alert controller 404 to provide the ability to visually alert housekeeping workers as they pass by a room. The room alert controller 404 may be coupled to a microphone 418 and/or light/proximity/motion sensors 408 within a room. The microphone 418 may be part of the communication terminals 118 sensors dedicated to that room. The proximity sensors may be infrared sensors. When a guest indicates a housekeeping services selection (either a time frame for housekeeping services or a desire to not be disturbed), a signal may be sent to the room alert controller 404. Alternatively, the signal may be sent to a central hotel controller that triggers the room alert controller 404.

If a microphone 418 or proximity/motion sensors 408 detect a person within the room, a notification light 406 outside the room may be configured to indicate the person's presence within the room. For security reasons, this system may only display an occupation indicator to housekeeping personnel when they enter the area, as detected by proximity/motion sensors 408 in the corridor. Alternately, the notification light 406 may be configured with a keypad or other device to accept a pressed code or detect the presence of a secure token. In this way, the availability of the room for housekeeping may be verified without the need to knock on doors up and down the corridor.

According to another component of the automated guest satisfaction and services scheduling system described herein, the techniques herein provide particularly for managing satisfaction of guests. For instance, in certain embodiments herein, guests may be asked some variant of“how is your stay going”. If the guest is happy (a positive satisfaction assessment/response), then the techniques herein may route the guest to another screen/menu on the interactive interface of their communication terminal promoting a loyalty program signup. In the guest is unhappy (a negative satisfaction assessment/response), then the techniques herein may either send a report to

management, or may send a report directly into the hotel’s guest response system.

In addition, when an issue is reported or other negative response (a“negative branch”), then the techniques herein may display all or some combination of a) shortcut icons to most frequently reported issues or needed items, b) a chat window to chat directly from the tablet, c) a phone number entry window to have the hotel call the guest direct, and so on.

Conversely, when on a positive branch, a guest may be presented with a loyalty membership promotion, where if they indicate that they are interested in joining the loyalty club, the techniques herein can either send that guest’s name and (if provided) phone number to a hotel employee for follow up, or else that guest may be presented with an online signup website.

FIG. 5 illustrates an example method 500 in accordance with one embodiment of the disclosure. In particular, a PMS lookup of check-in records may occur in block 502 to determine when a guest is checking out. If a multi-day stay, then in block 504 the first question may be regarding housekeeping scheduling preferences, such as described above. For example, the question“when do you want your room made up tomorrow?” may be presented to the guest, with options such as“morning,”“afternoon,”“evening,” or“privacy please” (forgoing services), which may carry an incentive, such as some number of loyalty points, a discount (e.g., $5.00) off a purchase in the hotel lobby food store, and so on. After this first question in block 504 is answered, then the

communication terminal may release the method in block 506 to proceed.

In block 508, whether for a single day stay or after a multi-day stay housekeeping question has been answered, the satisfaction assessment question, such as“how is your stay” may be presented on the interactive interface of the communication terminal in the guest’s room. If the response is positive (i.e., happy guest), then the techniques herein may present the guest with a loyalty membership signup (e.g., promotion) in block 512.

If the guests accepts the promotion, then in block 514 the guest may be presented to a sign-in page, or may receive the phone number of the hotel’s loyalty program to follow up.

On the other hand, in response to a negative satisfaction assessment in block 516, then the techniques herein in block 518 may report the response or else may direct the guest into a‘guestware’ branch of the hotel, possibly offering the guest direct text, live- chat, or to have an operator call the guest. If texting or chatting, this may occur on the communication terminal (e.g., tablet), or else the guest may have the option of entering their phone number and having the hotel support person text or call them on their own mobile phone.

Many other details and options are available in the satisfaction assessment process, including those described below, and those shown and described in FIG. 5 are merely one example configuration made possible by the techniques herein.

According to still another component of the automated guest satisfaction and services scheduling system described herein, the techniques herein provide particularly for managing the departure (checkout) of guests. For instance, in certain embodiments herein, the hotel may present, via the interactive interface of the communication terminals in a guest’s room, various departure time options for the following day. A hotel standard checkout time may exist, which provides the opportunity for early and/or late checkout. Early checkout, on the one hand, may be offered along with an incentive to a guest in order to assist in particularly busy times. Late checkout, on the other hand, may come at a price to the guest requesting it, such as in terms of loyalty points or money. FIG. 6 illustrates an example method 600 in accordance with one embodiment of the disclosure. In particular, on the evening before the guest’s departure (e.g., as detected from a query of the PMS), the hotel may ask what time the guest intends to check out (block 602), such as a standard time, early, or late. In block 604, the hotel may add incentive (e.g., loyalty points or money) for early checkout when they are heavily booked and need to get into the rooms early. Alternatively, in block 606, the hotel may“upsell” late checkout, e.g., a) late checkout at l :00p - $25.00; b) late checkout at 2:00p - $50.00; c) late checkout at 3:00p - $100.00, and so on.

Additionally during checkout, the hotel may also offer the guest an opportunity to provide a review on a review platform (e.g., the hotel’s own or else a third-party platform). The review may be directly linked, or else may prompt a login to the review platform for completion by the guest.

Many other details and options are available in the departure management process, including those described below, and those shown and described in FIG. 6 are merely one example configuration made possible by the techniques herein.

Referring now to FIG. 7, an embodiment of a computer system 700 useful in implementing the methods disclosed herein comprises a central processing unit 702, memory 704, a bus 706, user I/O 708, a network interface 710, an operating system 712, applications 714, and a database 716.

In various embodiments, system 700 may include a desktop PC, server, workstation, mobile phone, laptop, tablet, set-top box, appliance, or other computing device that is capable of performing operations such as those described herein. In some embodiments, system 700 may include more or fewer components than those shown in FIG. 7. However, it is not necessary that all of these generally conventional components be shown in order to disclose an illustrative embodiment. Collectively, the various tangible components or a subset of the tangible components may be referred to herein as "logic" configured or adapted in a particular way, for example as logic configured or adapted with particular software or firmware. In various embodiments, system 700 may comprise one or more physical and/or logical devices that collectively provide the functionalities described herein. In some embodiments, system 700 may comprise one or more replicated and/or distributed physical or logical devices.

In some embodiments, system 700 may comprise one or more computing resources provisioned from a cloud computing provider, as will be understood by those skilled in the art.

System 700 includes a bus 706 interconnecting several components including a network interface 710, user I/O 708, a central processing unit 702, and a memory 704.

Memory 704 generally comprises a random access memory ("RAM") and permanent non-transitory mass storage device, such as a hard disk drive or solid-state drive. Memory 704 stores an operating system 712, and may also store applications 714 used for both general operation and for implementing the methods disclosed herein. Memory 704 may also include a database 716. In some embodiments, system 700 may communicate with database 716 via network interface 710, a storage area network ("SAN"), a high-speed serial bus, and/or via the other suitable communication technology.

In some embodiments, database 716 may comprise one or more storage resources provisioned from a cloud storage provider, as will be understood by those skilled in the art.

User I/O 708 may comprise one or more components allowing human interaction with the computing system 700, such as a monitor, a touch screen display, a mouse, a keyboard, a stylus, or other, similar devices.

Terms used herein should be accorded their ordinary meaning in the relevant arts, or the meaning indicated by their use in context, but if an express definition is provided, that meaning controls.

"Circuitry" in this context refers to electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes or devices described herein), circuitry forming a memory device (e.g., forms of random access memory), or circuitry forming a communications device (e.g., a modem, communications switch, or optical- electrical equipment).

"Firmware" in this context refers to software logic embodied as processor- executable instructions stored in read-only memories or media.

"Hardware" in this context refers to logic embodied as analog or digital circuitry.

"Logic" in this context refers to machine memory circuits, non transitory machine-readable media, and/or circuitry which by way of its material and/or material- energy configuration comprises control and/or procedural signals, and/or settings and values (such as resistance, impedance, capacitance, inductance, current/voltage ratings, etc.), that may be applied to influence the operation of a device. Magnetic media, electronic circuits, electrical and optical memory (both volatile and nonvolatile), and firmware are examples of logic. Logic specifically excludes pure signals or software per se (however does not exclude machine memories comprising software and thereby forming configurations of matter).

"Software" in this context refers to logic implemented as processor-executable instructions in a machine memory (e.g. read/write volatile or nonvolatile memory or media).

Herein, references to "one embodiment" or "an embodiment" do not necessarily refer to the same embodiment, although they may. Unless the context clearly requires otherwise, throughout the description and the claims, the words "comprise,"

"comprising," and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in the sense of "including, but not limited to." Words using the singular or plural number also include the plural or singular number respectively, unless expressly limited to a single one or multiple ones. Additionally, the words "herein," "above," "below" and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. When the claims use the word "or" in reference to a list of two or more items, that word covers all of the following interpretations of the word: any of the items in the list, all of the items in the list and any combination of the items in the list, unless expressly limited to one or the other. Any terms not expressly defined herein have their conventional meaning as commonly understood by those having skill in the relevant art(s).

Various logic functional operations described herein may be implemented in logic that is referred to using a noun or noun phrase reflecting said operation or function. For example, an association operation may be carried out by an "associator" or "correlator". Likewise, switching may be carried out by a "switch", selection by a "selector", and so on.

Additionally, an example of an illustrative interactive interface according to one or more embodiments herein is provided in FIG. 8, which shows elements that may be included in the interactive interface 800 generated for a typical communication terminal 802 located in the room of a guest. Generally, a template used by the interface builder 220 module in the communication terminals 118 may collect content for display or linked access via a number of screen modules. For example, the top of the interface may comprise a branded task bar 804. Beneath that, there may be left sidebar menu 806, center content viewing pane 810, and (optional) right sidebar content 816 areas.

Customized content may be allocated to one or more of these screen areas. For example, general hotel information may be linked from the left sidebar menu 806 and displayed in the center content viewing pane 810. This information may include operating hours for hotel restaurants and services, among other things. The right sidebar content 816 may be based on other content, such as external content, offers, etc., or may be an extension of the left sidebar menu. The particular content associated with the techniques described herein may be presented in either sidebar 806 or 816, as well as in center viewing pane 810 (e.g., as selected to show a larger format of the content in the center content viewing pane when clicked in the sidebar, or else as separate pop-up content without first requiring a sidebar selection). Notably, other variants of the formatting of the interactive interface 800 may be made, and any shown and discussed herein are merely examples for illustration.

Additional and/or alternative embodiments may also be contemplated in accordance with the present disclosure and the techniques described herein. For instance, in one embodiment, tiered checkout times may be shown with various incentives for each (e.g., 8-10a for an incentive/reward, 10-12a no reward, 12-2p with a cost/penalty, etc.). Additionally, a one-touch checkout button may allow a guest to leave the room, checkout, and optionally schedule services at the same time, such as valet, a bellhop for bags, and so on. This may have the option of being at an advanced time (e.g., 15 minutes or other value that may be set or selected by the guest). Also, this checkout button may reset the room to a default through controlled systems, such as shutting off lights, resetting HVAC settings, and so on, either immediately, after a timer, or after sensors detect that no one is in the room any longer. In still further embodiments, the system herein may detect if a guest is still in the room after the scheduled checkout time, and if so may notify the guest (e.g., an alarm) and may offer an update to the late checkout options. Furthermore, in certain embodiments, the incentives and costs mentioned herein may be dynamic, meaning they change based on demand (e.g., higher incentives and/or costs when the hotel is particularly busy and needs the rooms). Still further embodiments may be contemplated herein, and those mentioned are merely examples.

In closing, an illustrative system according to one or more embodiments of the present disclosure may comprise: a server; and a plurality of communication terminals in communication with the server, each of the communication terminals having a graphical user interface (GUI) and being associated with a respective room of a plurality of hotel rooms of a hotel; wherein the server is configured to receive registration information when a guest checks into the hotel, the registration information including an

identification of the guest and a particular assigned room of the plurality of hotel rooms; wherein the server is configured to identify a particular communication terminal of the plurality of communication terminals that is associated with the particular assigned room; wherein the particular communication terminal is configured to present an interactive interface on a corresponding GUI of the particular communication terminal, the presented interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time; wherein the particular communication terminal is configured to receive a selection of a particular checkout time and to share the selection of the particular checkout time with the server; and wherein the server is configured to provide the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

In one embodiment, the particular communication terminal is configured to present costs associated with selection of the one or more later checkout times within the interactive interface. In one embodiment, the costs associated with selection of the one or more later checkout times are one of either static costs or dynamic costs based on demand.

In one embodiment, the plurality of options for selection further comprise one or more earlier checkout times than the hotel standard checkout time. In one embodiment, the particular communication terminal is configured to present incentives associated with selection of the one or more earlier checkout times within the interactive interface, and wherein the incentives are one of either static incentives or dynamic incentives based on demand. In one embodiment, the plurality of options for selection further comprise the one or more earlier checkout times in response to a push from the server based on demand.

In one embodiment, on the date of departure of the guest, the particular communication terminal is configured to present, within the interactive interface, a checking out option, wherein in response to receiving a selection of the checking out option, the communication terminal is configured to share the selection of the checking out option with the server; and the server is configured to provide the selection of the checking out option for the guest for the particular assigned room with the hotel service scheduler. In one embodiment, in response to receiving a selection of the checking out option, the communication terminal is configured to set one or more controlled devices within the particular assigned room.

In one embodiment, on the date of departure of the guest, the particular communication terminal is configured to present, within the interactive interface, a checking-out-soon option indicative of an advance time until the guest is checking out and a selectable request to initiate one or more services from the hotel consisting of: valet services, bellhop services, and disability assistance; in response to receiving a selection of the checking-out-soon option, the communication terminal is configured to share the request to initiate one or more services with the server; and the server is configured to provide the selection of the checking-out-soon option for the guest for the particular assigned room with one or more systems providing the one or more services of the request. In one embodiment, the advance time is selectable by the guest through the interactive interface.

In one embodiment, the communication terminal is configured to detect that the guest is still within the particular assigned room after passage of the particular checkout time, and in response, to notify the guest of the passage of the particular checkout time.

In one embodiment, the particular communication terminal is configured to present, on the interactive interface in response to passage of the particular checkout time, an updated plurality of options for a revised checkout time, the updated plurality of options comprising one or more later checkout times than the particular checkout time and associated costs. In one embodiment, the communication terminal is configured to notify the guest of the passage of the particular checkout time after a threshold time past the particular checkout time based on demand for the particular assigned room.

In one embodiment, on the date of departure of the guest, the communication terminal is configured to present, on the interactive interface, an option for the guest to leave a review regarding the hotel via the interactive interface.

In one embodiment, on a night immediately preceding the date of departure, the communication terminal is configured, in response to the guest not having yet selected the particular checkout time, to force the guest to select the particular checkout time prior to allowing any other functionality of the communication terminal. Additionally, FIG. 9 illustrates an example simplified procedure for managing hotel guest departures within an automated guest satisfaction and services scheduling system in accordance with one or more embodiments described herein, particularly from the perspective of a system of a hotel server 104. For example, a non-generic, specifically configured device (e.g., hotel server 104) may perform procedure 900 by executing stored instructions. The procedure 900 may start at step 905, and continues to step 910, where, as described in greater detail above, a server receives registration information when a guest checks into a hotel, the registration information including an identification of the guest and a particular assigned room of a plurality of hotel rooms of the hotel.

In step 915, the server identifies a particular communication terminal of a plurality of communication terminals in communication with the server that is associated with the particular assigned room, wherein each of the communication terminals has a graphical user interface (GUI) and is associated with a respective room of the plurality of hotel rooms of the hotel.

In step 920, the server causes the particular communication terminal to present an interactive interface on a corresponding GUI of the particular communication terminal, the presented interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time.

In step 925, the server receives, from the particular communication terminal, a selection of a particular checkout time.

In step 930, the server provides the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

The simplified procedure 900 may then end in step 935, notably with the option for addition steps and details as described herein (e.g., wherein costs are associated with selection of the one or more later checkout times, and wherein the costs are one of either static costs or dynamic costs based on demand set by the server; wherein the plurality of options for selection further comprise one or more earlier checkout times than the hotel standard checkout time, and wherein incentives are associated with selection of the one or more earlier checkout times, and wherein the incentives are one of either static incentives or dynamic incentives based on demand set by the server; and so on).

Moreover, FIG. 10 illustrates another example simplified procedure for managing hotel guest departures within an automated guest satisfaction and services scheduling system in accordance with one or more embodiments described herein, particularly from the perspective of a communication terminal 118. For example, a non-generic, specifically configured device (e.g., communication terminal 118) may perform procedure 1000 by executing stored instructions. The procedure 1000 may start at step 1005, and continues to step 1010, where, as described in greater detail above, a particular communication terminal of a plurality of communication terminals receives identification of a guest, wherein the particular communication terminal is associated with a particular room of a plurality of hotel rooms of a hotel, and wherein the guest has checked into the hotel and has been assigned to the particular room.

In step 1015, the terminal presents, on a corresponding graphical user interface (GUI) of the particular communication terminal, an interactive interface querying the guest to select a checkout time from a plurality of options for a date of departure of the guest, the plurality of options comprising a hotel standard checkout time and one or more later checkout times than the hotel standard checkout time.

In step 1020, the interactive interface receives a selection of a particular checkout time.

In step 1025, the particular communication terminal shares the selection of the particular checkout time with the server to cause the server to provide the selection of the particular checkout time for the guest for the particular assigned room with a hotel service scheduler.

The procedure 1000 may then end in step 1030, notably with the ability to complete additional steps, such as, e.g., presenting, on the date of departure of the guest, within the interactive interface, a checking out option; receiving a selection of the checking out option; and sharing the selection of the checking out option with the server, causing the server to provide the selection of the checking out option for the guest for the particular assigned room with the hotel service scheduler.

It should be noted that while certain steps within procedures 900-1000 may be optional as described above, the steps shown in FIGS. 9-10 are merely examples for illustration, and certain other steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments herein. Moreover, while procedures 900-1000 are described separately, certain steps from each procedure may be incorporated into each other procedure, and the procedures are not meant to be mutually exclusive.

Advantageously, the techniques described herein thus provide for managing hotel guest departures within an automated guest satisfaction and services scheduling system. In particular, the techniques herein provide an improved system to solicit and log guest responses to allow for advance planning, scheduling, and overall satisfaction

maintenance, through a system that is convenient enough for guests to participate in without detracting from the guest experience.

While there have been shown and described illustrative embodiments, it is to be understood that various other adaptations and modifications may be made within the scope of the embodiments herein. For example, though the disclosure was often described with respect to hotels, those skilled in the art should understand that this was done only for illustrative purpose and without limitations, and the techniques herein may be used with any temporary accommodation where housekeeping, satisfaction, and departures need to be managed, such as for house rentals, apartment rentals, condo rentals, room rentals, office rentals, and so on. Furthermore, while the embodiments may have been demonstrated with respect to certain communication environments, physical environments, or device form factors, other configurations may be conceived by those skilled in the art that would remain within the contemplated subject matter of the description above. The foregoing description has been directed to specific embodiments. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their advantages. For instance, it is expressly contemplated that certain components and/or elements described herein can be implemented as software being stored on a tangible (non-transitory) computer-readable medium (e.g., disks/CDs/RAM/EEPROM/etc.) having program instructions executing on a computer, hardware, firmware, or a combination thereof. Accordingly this description is to be taken only by way of example and not to otherwise limit the scope of the embodiments herein. Therefore, it is the object of the appended claims to cover all such variations and modifications as come within the true intent and scope of the embodiments herein.