A system and method for secure storage and management of transitory data, comprising at least a profile manager, a callback manager, a context analysis engine, and a vault manager, which allows a user to create a data container to store data preferences, which encrypts the data stored within a data container, which creates a password for accessing the data container, which temporarily stores the data container, which manages data container interactions between the system user and a second user, such as a business enterprise, and which establishes default preferences and creates a default container based upon context content data.

A system and method for mobile device active callback integration, utilizing a callback integration engine operating on a user's mobile device that present a callback token for integration through the operating system and software applications operating on the device, wherein interacting with the callback token produces a callback object used to execute a callback incorporating device hardware, context, scheduling, and trust information.

A system and method for a cloud callback platform, comprising at least a profile manager, callback manager, interaction manager, media server, context analysis engine, and context aggregator mechanism, allowing users to call a business, agents in contact centers, or other users who are connected to cloud callback platform, and, failing to connect to the individual they called, or by request, allow for an automatic callback object to be created, whereby the two users may be automatically called and bridged together at a time when both users are available, and a context summary report is sent to one or more user. The system and method implement predictive logic to determine the most successful alternative communication channel to use to bridge the two parties.

A system and method for secure storage and management of transitory data using a blockchain, comprising at least a callback manager, a context analysis engine, a vault manager, and a blockchain manager, which allows a user to create a data container to store data preferences, which encrypts the data stored within a data container, and which stores the encrypted data container in a blockchain. For each block, block reference data may is generated comprising the location of the block and its associated decryption key, and the block reference data is then encrypted with a second encryption key and stored off the blockchain in a separate database. The second key is distributed to involved parties to permit access to and reading of the block reference data. The block reference data is deleted based on self-destruct event triggers or when the involved parties are finished accessing the block reference data.

A system and method for mobile device active callback integration, utilizing a callback integration engine operating on a user's mobile device that present a callback token for integration through the operating system and software applications operating on the device, wherein interacting with the callback token produces a callback object used to execute a callback incorporating device hardware, context, scheduling, and trust information.

System and method for handling a transaction between a waiting party and queuing party include an independent communication system (ICS) managing calls between the waiting party and calling party for handling sensitive data as well as call-attached data. The ICS manages the transaction in different stages and with different levels of sensitivity. Either party is allowed to modify the call or call preferences during the transaction. The ICS works independently from the queuing party calling system.

A system and method for mobile device multitenant active and ambient callback prioritization, utilizing a callback integration engine to generate callback lists for multiple tenants, an environment analyzer, and a prioritization engine operating on a user's mobile device for integration through the operating system and software applications operating on the device, wherein the environment analyzer retrieves and aggregates ambient data related to the mobile device, inputs the aggregated ambient data into one or more machine learning algorithms wherein the algorithms may analyze the input data, the results of the analysis may be used to compute whether a user is available to be prioritized to receive a callback.

A system and method for managing virtual queues. A cloud-based queue service manages a plurality of queues hosted by one or more entities. The queue service is in constant communication with the entities providing queue management, queue analysis, and queue recommendations. The queue service is likewise in direct communication with queued persons. Sending periodic updates while also motivating and incentivizing punctuality and minimizing wait times based on predictive analysis. The predictive analysis uses “Big Data” and other available data resources such as schedule data and historical throughput data for various resources associated with an entity, for which the predictions assist in the balancing of persons across multiple queues for the same event or multiple persons across a sequence of queues for sequential events.

Location determination and telephone number distribution for emergency calls is enabled by a telephony system which maintains multiple pools of telephone numbers. Each pool corresponds to a different region such that the pools of telephone numbers are defined at the region-level rather than at the site-level. The telephony system determines the location of a calling device initiating an emergency call regardless of whether the calling device is at a known site. Based on the determined location of the calling device, one of the pools of telephone numbers which corresponds to that location is selected. The telephony system thereafter distributes a telephone number for the calling device to use for the emergency call from that selected pool of telephone numbers to facilitate an emergency call between the calling device and a local public safety answering point.

Aspects described herein may allow for deploying third-party callback to be performed on a mobile device. For example, the mobile device may configure a third-party callback to be performed after a triggering event is detected by a remote device. The triggering event may relate to a remote device associated with the mobile device. A determination may be made as to whether the mobile device is within a pre-determined proximity of the remote device. If the two devices are in proximity and if the mobile device receives a message that indicates the triggering event has been detected, the mobile device may perform the third-party callback. In this way, a user's need to request services conveniently and accurately is facilitated.