# US 2020/0396337 A1 · System and method for hybrid callback management and failure recovery

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2020/0396337 A1
- Document ID: US20200396337A1
- Status: Published application
- Kind: A1
- Application number: 17/011,248
- Filed: 2020-09-03
- Published: 2020-12-17
- Earliest claimed: 2009-01-28
- Assignees: Virtual Hold Technology Solutions, LLC
- Applicants: Virtual Hold Technology Solutions, LLC
- Inventors: Matthew Donaldson Moller; Matthew DiMaria; Shannon Lekas; Kurt Nelson; Nicholas James Kennedy; Kevin Shinseki; Robert Harpley
- Web page: https://patentgrep.com/patent/US20200396337A1

## CPC

- H04M 3/5231: {with call back arrangements}
- H04L 51/02: using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
- H04L 67/306: User profiles
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 67/53: using third party service providers
- H04M 3/5183: {Call or contact centers with computer-telephony arrangements}
- H04M 3/5238: {with waiting time or load prediction arrangements}
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for hybrid callback management and failure recovery, utilizing a callback cloud and an on-premise callback system, allowing brands to utilize a hybrid system that protects against any premise outages or cloud service faults and failures by introducing redundancies and co-maintenance of data key to callback execution.

## Claims

### Claim 1

A system for hybrid callback management and failure recovery, comprising:
a callback cloud service comprising at least a processor, a memory, and a first plurality of programming instructions stored in the memory and operating on the processor, wherein the first programming instructions, when operating on the processor, cause the processor to:
store and maintain global user profiles;
communicate with an on-premise callback system;
maintain relevant agent and brand data from an on-premise callback system;
execute callback requests;
calculate estimated wait times for callbacks; and
an on-premise callback system comprising at least a processor, a memory, and a second plurality of programming instructions stored in the memory and operating on the processor, wherein the second programming instructions, when operating on the processor, cause the processor to:
communicate with a callback cloud service;
send data related to callback objects and agents to a callback cloud service;
receive consumer calls to a brand;
create a callback object upon a consumer requesting a call back from a brand;
schedule a callback with consumers based on consumer availability and agent scheduling;
execute callbacks between consumers and agents at a specified time; and
connect the two parties, when the two first and second called parties are online, and delete the callback object.

### Claim 2 (depends on 1)

The system of claim 1, further comprising a broker server comprising at least a processor, a memory, and a third plurality of programming instructions stored in the memory and operating on the processor, wherein the third programming instructions, when operating on the processor, cause the processor to:
interface with third party contact center services; and
utilize these services in periods of on-premise callback system failure.

### Claim 3

A method for hybrid callback management and failure recovery, comprising the steps of:
storing and maintaining global user profiles, using a callback cloud service;
communicating with an on-premise callback system, using a callback cloud service;
maintain relevant agent and brand data from an on-premise callback system, using a callback cloud service;
executing callback requests, using a callback cloud service;
calculating estimated wait times for callbacks, using a callback cloud service;
communicating with a callback cloud service, using an on-premise callback system;
sending data related to callback objects and agents to a callback cloud service, using an on-premise callback system;
receiving consumer calls to a brand, using an on-premise callback system;
creating a callback object upon a consumer requesting a call back from a brand, using an on-premise callback system;
scheduling a callback with consumers based on consumer availability and agent scheduling, using an on-premise callback system;
executing callbacks between consumers and agents at a specified time, using an on-premise callback system; and
connecting the two parties, when the two first and second called parties are online, and deleting the callback object, using an on-premise callback system.

### Claim 4 (depends on 3)

The method of claim 3, further comprising a broker server comprising at least a processor, a memory, and a third plurality of programming instructions stored in the memory and operating on the processor, wherein the third programming instructions, when operating on the processor, cause the processor to:
interface with third party contact center services; and
utilize these services in periods of on-premise callback system failure.
