A computer program product for prioritizing order fulfillment at a retail sales facility, including the steps of: a) receiving purchase request information at a retail sales computing device that includes identifying information and order information for the first customer, b) receiving location information for the first customer, c) processing the received location information for the first customer together with location information of the retail sales facility to predict an estimated time of arrival (ETA) for the first customer at the retail sales facility, d) scheduling a time interval for acquiring updated location information for the first customer, and e) placing the identifying information, order information and ETA for the first customer in an order fulfillment queue for all current customers. Entries in the order fulfillment queue are ordered in increasing ETA order, whereby order fulfillment activities can proceed according to the order of order requests in the order fulfillment queue. ETA is continuously updated for each customer, and thereby the order for fulfilling customer orders in the order fulfillment queue. For example, if a customer's distance from the retail sales facility increases (for example, due to a mistaken turn), that customer's order will drop to a later-served position in the queue. The location information for the first customer includes GPS-based location information of the first customer that is captured by a GPS device associated with a mobile computing device of the first customer. The location information for the retail sales facility includes GPS-based location information of the retail sales facility. The ETA prediction is performed using the GPS-based location information of the first customer and the GPS-based location information of the retail sales facility.

Methods to reduce agent effort and improve customer experience quality through artificial intelligence. The Agent Assist tool provides contact centers with an innovative tool designed to reduce agent effort, improve quality and reduce costs by minimizing search and data entry tasks The Agent Assist tool is natively built and fully unified within the agent interface while keeping all data internally protected from third-party sharing.

An example patient scheduling system can include: at least one processor; and system memory encoding instructions which, when executed by the at least one processor, cause the system to: provide a schedule for a patient, the schedule defining care items associated with the patient; allow for acceptance of a patient care activity; and notify a caregiver and the patient of changes to the patient care activity.

Techniques and system configurations for use of cached data to generate and present a schedule or other availability information for delivery and service scheduling of a product are disclosed herein. In an example, electronic operations used for offering cached availability information in a user interface include: obtaining service information to identify a service for a product (such as installation or removal) that can accompany, precede, or follow, delivery of a product; obtaining customer information to identify a geographic location to perform the service for the product; retrieving, from a cached data store, availability information to perform the service for the product based on the geographic location and the service information; and presenting the availability information to perform the service in association with the delivery of the product. With this technique, a calendar or schedule can be produced from cached data, without requiring multiple requests to a scheduling system.

A system for managing a local area shopping network is disclosed. The plurality of subsystems includes an order request subsystem, configured to receive a request of a product order from registered/unregistered (a customer can be guest customer) customers. The plurality of subsystems includes a parameter determination subsystem configured to determine a delivery area, a delivery schedule for sellers and determine product pickup area for the customers/buyers based on their preference and location. A buyer may decide for delivery only, in that case there is no pickup area/perimeter. The plurality of subsystems includes a product transaction subsystem. The product transaction subsystem is configured to identify (all sellers. If there are none that meet criteria then it is blank) one seller from the list of the registered sellers based on received request of the product order and establish a direct communication link with the customer. The product transaction subsystem is configured to complete the delivery of the order to the registered customers upon accepting the received request. (sellers do delivery and not the application) Customers and sellers are connected in a single platform, and transaction is facilitated.

A method of ranking criticality of upcoming customer meetings may comprise receiving, via a network interface device, for a plurality of customers, a meeting deadline date, a meeting frequency value, and a previous sales factor rate indicating revenue or a percentage of previous meetings that resulted in revenue to a user, determining, via a processor, for the plurality of customers, a past due percentage value by dividing the number of days elapsed since the meeting deadline date by a number of days within the meeting frequency value, and determining, for each of the plurality of customers, a criticality ranking by weighting the past due percentage value with the previous sales factor rate. Displaying, via a graphical user interface (GUI), the plurality of customers, listed in order of the criticality ranking, from highest to lowest, for scheduling of upcoming meetings in order of criticality.

The described technology relates to integrating events electronically scheduled in enterprise web applications and other event applications. A capability is provided for events created by an enterprise web application and events from other external event streams to be presented in a consolidated calendar in the enterprise web application. Capabilities are also provided for sharing the calendar among enterprise users and non-enterprise users, and for efficiently generating the shared calendar.

The described technology relates to integrating events electronically scheduled in enterprise web applications and other event applications. A capability is provided for events created by an enterprise web application and events from other external event streams to be presented in a consolidated calendar in the enterprise web application. Capabilities are also provided for sharing the calendar among enterprise users and non-enterprise users, and for efficiently generating the shared calendar.

Disclosed are systems, methods, and non-transitory computer-readable storage media for setting a reminder triggered by a target device. A requesting device sends a request to a server to set a notification triggered by a target device. The request includes parameters, such as a location and a condition that define when the notification is triggered. The server sends instruction to the target device to set the notification based on the parameters. When the condition such as arrival is met by the target device in relation to the location the target device sends a message to the server that the notification has been triggered. The target device can set a geo-fence to determine the position of the target device in relation to the location, and the requesting user can dictate the size of the geo-fence. The server sends a message to the requesting device that the notification has been triggered.

Method, apparatus and computer program product for generating a channel calendar in a group-based communication system are described herein. The apparatus is configured to at least generate a channel calendar identifier associated with a group-based communication channel in the group-based communication system, receive a calendar sharing request associated with the channel calendar identifier from a client device, retrieve the calendar object and calendar object metadata set based on the channel calendar identifier, and cause rendering of the calendar object for display via a user interface of the client device.