IP Library Granted Patent US 10,346,635
Granted Patent B2
US 10,346,635 · App. 15/169,317 · Granted Jul 9, 2019

System and method for data management and task routing based on data tagging

Inventors: Praphul Kumar (Aldie, VA); Rajesh Ramchander (Gaithersburg, MD); Herbert Willi Artur Ristock (Walnut Creek, CA); Romiben Patel (South Riding, VA)
G06F21/6245G06F16/285G06F21/6218H04M3/5175H04M2203/401H04M2203/402H04M2203/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,346,635
App. No.
15/169,317
Granted
Jul 9, 2019
Kind
B2
Abstract

Systems and methods are shown for managing call center data in accordance with one or more sets of compliance rules involving receiving data pertaining to an interaction, determining a set of compliance rules relevant to the received data, tagging the received data to identify the relevant set of compliance rules, and utilizing the data tagging, applying the relevant set of compliance rules to handling the received data. Examples also involve receiving an interaction request, obtaining the data tagging for data corresponding to the received interaction request, using the data tagging for the data corresponding to the received interaction request to obtain the corresponding relevant set of compliance rules, using the corresponding set of compliance rules to identify agents eligible to access the data corresponding to the received interaction request, and routing the received interaction request to one of the eligible agents based on a defined routing strategy.

Claims (48)

1. A system for managing call center data in accordance with one or more sets of compliance rules, the system comprising:

a processor; and

a memory, wherein the memory stores instructions that, when executed by the processor, cause the processor to:

receive first and second data pertaining to respectively first and second interactions;

determine at least one of the sets of compliance rules relevant to the received first and second data;

tag the received first data with a first identifier based on a relevant set of compliance rules;

identify a first geographic location based on the first identifier tagged to the first data;

based on the identifying of the first geographic location:

store the received first data in a first data storage device located in the first geographic location;

identify a first agent determined to be located in the first geographic location; and

route the first interaction to the identified first agent;

tag the received second data with a second identifier different from the first identifier based on the relevant set of compliance rules;

identify a second geographic location different from the first geographic location based on the second identifier tagged to the second data; and

based on the identifying of the second geographic location:

store the received second data in a second data storage device located in the second geographic location; and

route the second interaction to a second agent in the second geographic location.

2. The system of claim 1 , where the instructions further cause the processor to:

use the first identifier tagged to the first data to identify and obtain a corresponding relevant set of compliance rules; and

control access to the first data in accordance with the corresponding set of compliance rules.

3. The system of claim 2 , where the controlling access to the first data further comprises requirements defined in the corresponding set of compliance rules relating to at least one of limiting access to a user or group of users, requiring a user authentication protocol, decryption for the data, geographic limitations for the data, use limitations for the data, and transmission requirements for the data.

4. The system of claim 1 , wherein the first identifier tagged to the first data identifies the first data as pertaining to a particular individual.

5. The system of claim 4 , wherein the instructions further cause the processor to receive a request to remove data pertaining to the particular individual and, responsive thereto, search data storage for data pertaining to the particular individual who is the subject of the removal request, and remove the data pertaining to the particular individual.

6. The system of claim 1 , wherein the instructions further cause the processor to analyze content of the received first data and tag the received first data based on the analysis of the content.

7. The system of claim 1 , where at least one of the sets of compliance rules relevant to the received first data pertains to a jurisdiction relevant to the received first data, wherein the instructions that cause the processor to tag the received first data include instructions that cause the processor to identify the jurisdiction relevant to the data.

8. The system of claim 1 , wherein the instructions that cause the processor to tag the received first data include instructions that cause the processor to tag the first data based on at least one performance criterion.

9. A method for managing call center data in accordance with one or more sets of compliance rules, the method comprising:

receiving first and second data pertaining to respectively first and second interactions;

determining, by a processor, at least one of the sets of compliance rules relevant to the received first and second data;

tagging, by the processor, the received first data with a first identifier based on a relevant set of compliance rules;

identifying, by the processor, a first geographic location based on the first identifier tagged to the first data;

based on the identifying of the first geographic location:

storing, by the processor, the received first data in a first data storage device located in the first geographic location;

identifying, by the processor, a first agent determined to be located in the first geographic location; and

routing, by the processor, the first interaction to the identified first agent;

tagging, by the processor, the received second data with a second identifier different from the first identifier based on the relevant set of compliance rules;

identifying, by the processor, a second geographic location different from the first geographic location based on the second identifier tagged to the second data; and

based on the identifying of the second geographic location:

storing, by the processor, the received second data in a second data storage device located in the second geographic location; and

routing the second interaction to a second agent in the second geographic location.

10. The method of claim 9 further comprising:

using the first identifier tagged to the first data to identify and obtain a corresponding relevant set of compliance rules; and

controlling access to the first data in accordance with the corresponding set of compliance rules.

11. The method of claim 10 , where the controlling access to the first data further comprises requirements defined in the corresponding set of compliance rules relating to at least one of limiting access to a user or group of users, requiring a user authentication protocol, decryption for the data, geographic limitations for the data, use limitations for the data, and transmission requirements for the data.

12. The method of claim 9 , wherein the first identifier tagged to the first data identifies the first data as pertaining to a particular individual.

13. The method of claim 12 further comprising receiving a request to remove data pertaining to the particular individual and, responsive thereto, searching data storage for data pertaining to the particular individual who is the subject of the removal request, and removing the data pertaining to the particular individual.

14. The method of claim 9 , where the method further comprises analyzing content of the received first data and tag the received first data based on the analysis of the content.

15. The method of claim 9 , where at least one of the sets of compliance rules relevant to the received first data pertains to a jurisdiction relevant to the received first data, wherein the tagging the first data includes identifying the jurisdiction relevant to the data.

16. The method of claim 9 , where tagging the received first data further involves tagging the received first data based on at least one performance criterion.

Assignments (4)
NOTICE OF SUCCESSION OF SECURITY INTERESTS AT REEL/FRAME 040815/0001 Recorded Feb 3, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: GOLDMAN SACHS BANK USA, AS SUCCESSOR AGENT
Reel/Frame 070498/0001 →
CHANGE OF NAME Recorded May 13, 2024
From: GENESYS TELECOMMUNICATIONS LABORATORIES, INC.
To: GENESYS CLOUD SERVICES, INC.
Reel/Frame 067391/0105 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 13, 2019
From: KUMAR, PRAPHUL; RAMCHANDER, RAJESH; RISTOCK, HERBERT WILLI ARTUR; PATEL, ROMIBEN
To: GENESYS TELECOMMUNICATIONS LABORATORIES, INC.
Reel/Frame 048587/0697 →
SECURITY AGREEMENT Recorded Dec 5, 2016
From: GENESYS TELECOMMUNICATIONS LABORATORIES, INC., AS GRANTOR; ECHOPASS CORPORATION; INTERACTIVE INTELLIGENCE GROUP, INC.; BAY BRIDGE DECISION TECHNOLOGIES, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 040815/0001 →
Continuity (1)
Related Publication 20170344754A1 · Nov 30, 2017
Cited By (21)
US 12,190,330 US 12,204,564 US 12,216,794 US 12,259,882 US 12,265,896 US 12,277,232 US 12,288,233 US 12,299,065 US 12,314,426 US 12,353,405 US 12,381,915 US 12,412,140 US 12,425,321 US 12,536,329 US 12,556,519 US 12,591,828 US 12,609,938 US 12,641,108 US 12,688,324 US 12,694,044 US 12,718,167