Receiving and queuing requests from hospitality customers

Patent No. US9436958 (titled "Receiving and queuing requests from hospitality customers") on Mar 15, 2013. The application was issued on Sep 6, 2016.

What is this patent about?

’958 is related to the field of mobile request management and hospitality services. Specifically, it addresses the logistical friction in environments like hotels or large retail complexes where customers need to request specific goods or services, but often lack real-time information about what is available or a direct line to the specific staff members capable of fulfilling those needs.

The underlying idea behind ’958 is to bridge the gap between a customer’s physical location and a business’s internal workflow by using geolocation-triggered service menus. Instead of a static app interface, the system dynamically identifies which business location a user is currently at and serves a customized catalog of requests—such as housekeeping or valet—that are then automatically routed to specialized staff queues based on the specific nature of the request.

The claims of ’958 focus on a server-side architecture that establishes concurrent connections with both customer and staff mobile devices. The system uses a geolocation service to filter and provide a selectable data set of goods or services relevant to the user's specific coordinates, then manages the lifecycle of a request by assigning it to a targeted queue that is pushed directly to the mobile devices of a designated staff group.

In practice, the invention functions as a digital concierge that automates the dispatching process. When a guest enters a hotel lobby, the system recognizes their location and updates their mobile interface with relevant options like room service or maintenance. When the guest submits a request, the system doesn't just send a generic notification; it evaluates the request type and geolocation to place the task into a specific bucket—for example, a 'cleaning' queue—which is then instantly accessible to the housekeeping team on their own mobile devices.

This approach differs from prior solutions by eliminating the need for manual dispatching or centralized switchboards. By utilizing a two-way communication line between the customer and the specific staff group, the system allows for real-time status updates, such as estimated times of arrival (ETA) and direct messaging. This creates a highly responsive environment where service fulfillment is tracked from the moment of the geolocation-based selection through to the final closing of the task in the management queue.

How does this patent fit in bigger picture?

Technical Landscape

In the early 2010s when ’958 was filed, hospitality and service-oriented businesses typically managed customer requests through centralized, stationary systems or manual interpersonal communication, at a time when service discovery was typically implemented using physical directories or telephonic inquiries. When systems commonly relied on fixed-line infrastructure or localized staff dispatching rather than dynamic mobile data synchronization, the real-time distribution of service catalogs to transient mobile devices was often limited by fragmented network protocols. Hardware and software constraints of the era made the seamless integration of location-aware service provisioning and automated, role-based request queuing non-trivial, as mobile applications were often siloed from the backend operational workflows of the service provider.

Prosecution Position

The disclosed invention represents a technical advancement in request management through the architectural integration of mobile location-sensing with a dynamic, rule-based queuing engine. By establishing a direct communication link between a customer's mobile device and a request handler that utilizes real-time location data, the system enables the delivery of context-specific service data that reflects current business offerings. The technical solution shifts from passive request logging to an active distribution model where requests are automatically categorized by type and routed into specialized queues assigned to specific staff groups. This architecture achieves a more efficient load-balancing of service tasks and overcomes the constraint of manual dispatching by implementing automated alert triggers based on queue duration and staff availability thresholds, thereby ensuring responsive fulfillment of location-dependent requests.

Claims

This patent contains 20 claims, with claims 1, 8, and 15 serving as the independent claims. The independent claims focus on a request management system and method that utilizes the geolocation of a customer's mobile device to provide a selectable set of goods or services, receive a request, and then route that request into a specific queue for delivery to a staff mobile device based on the request type and location. The dependent claims serve to further refine the system by specifying features such as business location filtering based on distance, customized branding displays, detailed request metadata including priority indicators, and the specific organizational structure of the fulfillment groups.

Key Claim Terms New

Definitions of key terms used in the patent claims.

Term (Source)Support for SpecificationInterpretation
Geolocation
(Claim 1, Claim 8, Claim 15)
In an example embodiment, receiving requests using a request management system includes establishing a connection with a customer's mobile device and obtaining information about the location of the customer's mobile device. The server provides a set of data describing goods and/or services currently offered by one or more business locations based on this location. The request is added to a queue associated with groups assigned to fulfill the request based on the request type and the geolocation.The physical location of a customer's mobile device used by the server to identify a specific business location and filter the available goods or services offered to that customer.
Queue
(Claim 1, Claim 8, Claim 15)
The system adds the request to a queue associated with one or more groups assigned to fulfill the request based on the request type. Request status can include different stages relating to handling of a queued request, such as approval, pending, accepted, and closed. Alert generator 184 monitors queued pending requests and determines when alert criteria have been met, such as a time duration in which a request has been pending.A stored data structure at the server that organizes pending requests and is associated with specific staff groups for the purpose of tracking and processing fulfillment tasks.
Request type
(Claim 1, Claim 8, Claim 15)
Request type can be any information relating to a type of request. Types of requests can include but are not limited to any request relating to a concierge or hospitality service, such as, reservations & booking help, requests for towels, coffee, shampoo & conditioner, other supplies, valet, maintenance, nearby restaurant information, complaints, or other requests. The request is added to a queue associated with one or more groups assigned to fulfill the request based on the request type.A classification of a customer's submission (such as housekeeping, valet, or maintenance) used by the system to route the request to a specific fulfillment group.
Selectable set of data
(Claim 1, Claim 8, Claim 15)
Receiving requests includes providing to the customer's mobile device a set of data describing goods and/or services currently offered by one or more business locations. Data on images, descriptive text, graphical attributes, user interface elements or data structures can also be provided to facilitate display of interface(s). This allows a customer to interact with current information about offers.A collection of information describing goods or services currently available at a specific business location, which is dynamically determined based on the device's location and presented to the user for selection.
Staff mobile device
(Claim 1, Claim 8, Claim 15)
Summary information including request status and request type information is provided by request handler 182 at server 103 to concierge staff agent 163 at staff user mobile device 162. Data is sent to enable a staff user to view particular requests grouped by request status and request type, to enable a staff user to change a particular request status, and/or to enable a staff user handling a request to input a message to a customer. A staff user (such as a housekeeping team member) receives requests having a request type associated with their group.A mobile computing device used by a specific group of employees (such as housekeeping or maintenance) to receive, view, and update the status of queued customer requests.

Litigation Cases New

US Latest litigation cases involving this patent.

Case NumberFiling DateTitle
2:22-cv-00490Dec 23, 2022Tiare Technology, Inc. V. Dine Brands Global, Inc.

Patent Family

Patent Family

File Wrapper

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.

  • Get instant alerts for new documents

US9436958

Application Number
US13842177A
Filing Date
Mar 15, 2013
Publication Date
Sep 6, 2016
External Links
Slate, USPTO , Google Patents