Connecting contact center resources using DLT for IOT solutions
Multiple vendors often contribute a portion of their hardware and/or software to a customer to enable a particular feature. When issues occur, a contact center for more than one vendor may be required to perform an action in order to identify a resolution to the issue and apply the resolution. By coordinating multiple contact centers with smart contracts via a distributed leger, rules may be developed for the creation of blocks for notifications, escalations, tasks, and other actions or informational notifications to resolve the issue. Additionally, the blockchain may serve as a permanent record provide a history of actions taken, by whom, and when.
1. A system for managing multi-owner issue resolution, comprising:
a network interface to a network;
a server, comprising a microprocessor that accesses machine-readable instructions from a non-transitory memory and executes the machine-readable instructions to cause a microprocessor to:
receive a data structure from a monitoring component via the network interface;
access a smart contract from a distributed ledger comprising evaluation code;
evaluate the data structure with the evaluation code to produce a local qualification decision approving or denying entry to the distributed ledger;
receive, from the network, a number of peer qualification decisions from a number of peer systems;
upon obtaining a majority of decisions, comprising the local qualification decision and the number of peer qualification decisions, to approve, create a plurality of workflow blocks comprising at least a portion of the data structure and appending the plurality of workflow blocks to the distributed ledger, wherein at least one of the plurality of workflow blocks comprises machine-readable workflow instructions; and
cause the machine-readable workflow instructions within the at least one of the plurality of workflow blocks to execute.
2. The system of claim 1 , wherein the data structure is received from the monitoring component, further comprising:
the monitoring component receiving an operational attribute of a system component, wherein the monitoring component comprises a microprocessor executing machine-readable instructions; and
wherein the monitoring component, upon determining the operational attribute indicates an issue, causes the microprocessor to further execute machine-readable instructions to create the data structure and submit the data structure to the number of peer systems and the server.
3. The system of claim 1 , wherein the microprocessor further executes the machine-readable instructions to cause the microprocessor to provide, via the network interface, the data structure to the number of peer systems and, in response, receives the number of peer qualification decisions.
4. The system of claim 1 , wherein the microprocessor, further executes the machine-readable instructions to cause the microprocessor to, upon a failure to obtain the majority of decisions, comprising the local qualification decision and the number of peer qualification decisions, to approve, creating a service ticket and routing the service ticket to a service support application.
5. The system of claim 1 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, notifies at least one of the number of peer systems to perform a task.
6. The system of claim 5 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, determines that at least one task requires an action of at least one of the number of peer systems.
7. The system of claim 6 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, further comprises machine-readable workflow instructions comprising, in response to determining that at least one task requires the action of at least one of the number of peer systems:
create a subsequent block comprising machine-readable workflow instructions comprising indicia of the at least one task; and
append the subsequent block to the distributed ledger.
8. The system of claim 5 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, determines that a time threshold for resolution of the at least one task has expired.
9. The system of claim 1 , wherein the microprocessor further executes the machine-readable instructions to cause the microprocessor to:
receive data identifying one the plurality of workflow blocks;
create a subsequent block comprising the data; and
append the subsequent block to the distributed ledger.
10. A method for managing multi-owner issue resolution, comprising:
receiving a data structure from a monitoring component via a network interface to a network;
accessing a smart contract from a distributed ledger comprising evaluation code;
evaluating the data structure with the evaluation code to produce a local qualification decision approving or denying entry to the distributed ledger;
receiving, from the network, a number of peer qualification decisions from a number of peer systems;
upon obtaining a majority of decisions, comprising the local qualification decision and the number of peer qualification decisions, to approve, creating a plurality of workflow blocks comprising at least a portion of the data structure and appending the plurality of workflow blocks to the distributed ledger, wherein at least one of the plurality of workflow blocks comprises machine-readable workflow instructions; and
causing the machine-readable workflow instructions within the at least one of the plurality of workflow blocks to execute.
11. The method of claim 10 , wherein receiving the data structure further comprises:
receiving, by the monitoring component, an operational attribute of a system component, wherein the monitoring component comprises a microprocessor executing machine-readable instructions; and
determining whether the operational attribute indicates an issue; and
in response to determining the operational attribute indicates an issue, creating the data structure and submitting the data structure to the number of peer systems and a server.
12. The method of claim 10 , further comprising providing the data structure to the number of peer systems and, in response, receiving the number of peer qualification decisions.
13. The method of claim 10 , further comprising:
upon a failure to obtain the majority of decisions, comprising the local qualification decision and the number of peer qualification decisions, to approve, creating a service ticket; and
routing the service ticket to a service support application.
14. The method of claim 10 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, notifies at least one of the number of peer systems to perform a task.
15. The method of claim 14 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, determines that at least one task requires an action of at least one of the number of peer systems.
16. The method of claim 15 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, further comprises machine-readable workflow instructions comprising, in response to determining that at least one task requires the action of at least one of the number of peer systems:
create a subsequent block comprising machine-readable workflow instructions comprising indicia of the at least one task; and
append the subsequent block to the distributed ledger.
17. The method of claim 14 , wherein the machine-readable workflow instructions within the at least one of the plurality of workflow blocks, upon execution, determines that a time threshold for resolution of the at least one task has expired.
18. The method of claim 10 , further comprising:
receiving data identifying one the plurality of workflow blocks;
creating a subsequent block comprising the data; and
appending the subsequent block to the distributed ledger.
19. A system for managing multi-owner issue resolution, comprising:
means to receive a data structure from a monitoring component via a network interface to a network;
means to access a smart contract from a distributed ledger comprising evaluation code;
means to evaluate the data structure with the evaluation code to produce a local qualification decision approving or denying entry to the distributed ledger;
means to receive, from the network, a number of peer qualification decisions from a number of peer systems;
means to, upon obtaining a majority of decisions, the majority of decisions comprising the local qualification decision and the number of peer qualification decisions, to approve, create a plurality of workflow blocks comprising at least a portion of the data structure and appending the plurality of workflow blocks to the distributed ledger, wherein at least one of the plurality of workflow blocks comprises machine-readable workflow instructions; and
means to cause the machine-readable workflow instructions within the at least one of the plurality of workflow blocks to execute.
20. The system of claim 19 , further comprising:
means to receiving, at the monitoring component, an operational attribute of a system component, wherein the monitoring component comprises a microprocessor executing machine-readable instructions; and
means to, upon determining the operational attribute indicates an issue, create the data structure and submit the data structure to the number of peer systems and a server.