Blockchain for contact center engagement data
A server of a contact center generates an engagement recording and engagement metadata associated with a contact center engagement. The engagement metadata identifies one or more user devices and one or more business servers. The server stores the engagement recording and the engagement metadata in a block of a private blockchain. The block includes a cryptographic hash of a previous block in the private blockchain, the engagement recording, and the engagement metadata. The server provides access to the block to the one or more user devices and the one or more business servers.
1 . A method, comprising:
generating, by a server of a contact center, an engagement recording and engagement metadata associated with a contact center engagement, the engagement metadata identifying one or more user devices and one or more business servers, wherein the one or more business servers comprise a server of a business operating the contact center;
storing the engagement recording and the engagement metadata in a block of a private blockchain, the block comprising a cryptographic hash of a previous block in the private blockchain, the engagement recording, and the engagement metadata; and
providing access to the block to the one or more user devices or the one or more business servers.
2 . The method of claim 1 , comprising:
denying access to the block to a user device that is not identified in the engagement metadata as one the one or more user devices and that is not accessing the block via the one or more business servers.
3 . The method of claim 1 , comprising:
removing personally identifiable information from the engagement recording and from the engagement metadata prior to storing the engagement recording and the engagement metadata in the block.
4 . The method of claim 1 , wherein the engagement metadata comprises at least one of: an engagement duration, a hold time duration, an engagement start time, an engagement end time, an identifier of a contact center agent participating in the contact center engagement, an identifier of a contact center unit associated with the contact center engagement, or a summary of the contact center engagement.
5 . The method of claim 1 , wherein the one or more business servers further comprise at least one of: a server of a customer service provision business, or a server of a business transacting with a user of the one or more user devices.
6 . The method of claim 1 , comprising:
receiving, from a device associated with the one or more user devices, a request to delete at least a portion of the engagement recording; and
deleting the at least the portion of the engagement recording from the blockchain based on the request.
7 . The method of claim 1 , comprising:
storing the private blockchain at multiple nodes of a decentralized computer network.
8 . The method of claim 1 , comprising:
adding a digital signature to the block using a private key of the one or more user devices or the one or more business servers, wherein the digital signature is verifiable using a public key corresponding to the private key.
9 . A non-transitory computer readable medium storing instructions operable to cause one or more processors to perform operations comprising:
generating, by a server of a contact center, an engagement recording and engagement metadata associated with a contact center engagement, the engagement metadata identifying one or more user devices and one or more business servers, wherein the one or more business servers comprise a server of a business operating the contact center;
storing the engagement recording and the engagement metadata in a block of a private blockchain, the block comprising a cryptographic hash of a previous block in the private blockchain, the engagement recording, and the engagement metadata; and
providing access to the block to the one or more user devices or the one or more business servers.
10 . The non-transitory computer readable medium of claim 9 , the operations comprising:
forgoing granting access to the block to a user device that is not identified in the engagement metadata as one the one or more user devices and that is not accessing the block via the one or more business servers.
11 . The non-transitory computer readable medium of claim 9 , the operations comprising:
removing personally identifiable information from the engagement recording prior to storing the engagement recording in the block.
12 . The non-transitory computer readable medium of claim 9 , wherein the engagement metadata comprises at least one of: an engagement duration, an engagement start time, an engagement end time, an identifier of a contact center agent participating in the contact center engagement, an identifier of a contact center unit associated with the contact center engagement, or a summary of the contact center engagement.
13 . The non-transitory computer readable medium of claim 9 , wherein the one or more business servers comprise at least one of: a server of a business operating the contact center or a server of a business transacting with a user of the one or more user devices.
14 . The non-transitory computer readable medium of claim 9 , the operations comprising:
receiving, from a device associated with the one or more user devices, a request to delete a portion of the engagement recording; and
deleting the portion of the engagement recording from the blockchain based on the request.
15 . The non-transitory computer readable medium of claim 9 , the operations comprising:
storing the private blockchain at nodes of a decentralized computer network.
16 . The non-transitory computer readable medium of claim 9 , the operations comprising:
digitally signing, with a digital signature, the block using a private key of the one or more user devices or the one or more business servers, wherein the digital signature is verifiable using a public key corresponding to the private key.
17 . A system, comprising:
a memory subsystem; and
processing circuitry configured to execute instructions stored in the memory subsystem to:
generate, by a server of a contact center, an engagement recording and engagement metadata associated with a contact center engagement, the engagement metadata identifying one or more user devices and one or more business servers, wherein the one or more business servers comprise a server of a business operating the contact center;
store the engagement recording and the engagement metadata in a block of a private blockchain, the block comprising a cryptographic hash of a previous block in the private blockchain, the engagement recording, and the engagement metadata; and
provide access to the block to the one or more user devices or the one or more business servers.
18 . The system of claim 17 , the processing circuitry configured to execute the instructions stored in the memory subsystem to:
deny access to the block to a user device that is not identified in the engagement metadata as one of the one or more user devices and that is not accessing the block via the one or more business servers.
19 . The system of claim 17 , the processing circuitry configured to execute the instructions stored in the memory subsystem to:
identify, within the engagement recording and within the engagement metadata, personally identifiable information; and
remove the identified personally identifiable information from the engagement recording and from the engagement metadata prior to storing the engagement recording and the engagement metadata in the block.
20 . The system of claim 17 , wherein the engagement metadata comprises at least one of: an engagement duration, a hold time duration, an engagement start time, an identifier of a contact center agent participating in the contact center engagement, an identifier of a contact center unit associated with the contact center engagement, or a summary of the contact center engagement.