|
|  Get related patents on CD |
| United States Patent | 7389240 |
| Link to this page | http://www.wikipatents.com/7389240.html |
| Inventor(s) | Nygren; Blair E. (Coppell, TX), Whisenhunt; William O. (Copell, TX), Shah; Abhay S. (Irving, TX) |
| Abstract | A system for implementing a recording plan based upon the presence of a
client includes a client monitor and a plan manager. The client monitor
generates a presence message signifying the presence of a client on a
network associated with the system. The presence message comprises a
presence type and a client identity. The plan manager receives the
presence message from the client monitor and, in response, retrieves a
plan template based upon the client identity and the presence type. The
plan manager creates a recording plan associated with the client based at
least in part upon the plan template. |
| |
|
Title Information  |
|
|
|
|
|
|
| Publication Date |
June 17, 2008 |
|
|
|
|
|
| Filing Date |
February 8, 2002 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Title Information  |
|
|
References  |
|
|
| *references marked with an asterisk below are user-added references |
|
U.S. References |
|
|
| Add a new US reference: |
| | Reference | Relevancy | Comments | Reference | Relevancy | Comments | 6850895 Brodersen et al.
Feb,2005 |      Your vote accepted [0 after 0 votes] | | 6801618 Nygren et al.
Oct,2004 |      Your vote accepted [0 after 0 votes] | | 6763104 Judkins et al.
Jul,2004 |      Your vote accepted [0 after 0 votes] | | 6707904 Judkins et al.
Mar,2004 |      Your vote accepted [0 after 0 votes] | | 6673104 Barry
Jan,2004 |      Your vote accepted [0 after 0 votes] | | 6640145 Hoffberg et al.
Oct,2003 |      Your vote accepted [0 after 0 votes] | | 2003/0126001 Northcutt et al.
Jul,2003 |      Your vote accepted [0 after 0 votes] | | 6574661 Delano et al.
Jun,2003 |      Your vote accepted [0 after 0 votes] | | 6542602 Elazar
Apr,2003 |      Your vote accepted [0 after 0 votes] | | 2003/0023675 Ouchi et al.
Jan,2003 |      Your vote accepted [0 after 0 votes] | | 6442567 Retallick et al.
Aug,2002 |      Your vote accepted [0 after 0 votes] | | 2002/0071529 Nelkenbaum
Jun,2002 |      Your vote accepted [0 after 0 votes] | | 6389400 Bushey et al.
May,2002 |      Your vote accepted [0 after 0 votes] | | 6356880 Goossens et al.
Mar,2002 |      Your vote accepted [0 after 0 votes] | | 2001/0012356 McDuff et al.
Aug,2001 |      Your vote accepted [0 after 0 votes] | | 6263049 Kuhn
Jul,2001 |      Your vote accepted [0 after 0 votes] | | 6134530 Bunting et al.
Oct,2000 |      Your vote accepted [0 after 0 votes] | | 6058163 Pattison et al.
May,2000 |      Your vote accepted [0 after 0 votes] | | 5963911 Walker et al.
Oct,1999 |      Your vote accepted [0 after 0 votes] | | 5946375 Pattison et al.
Aug,1999 |      Your vote accepted [0 after 0 votes] | | August 1998
Aug,1999 |      Your vote accepted [0 after 0 votes] | | | | | |
|
|
|
|
U.S. References |
|
|
Foreign References |
|
|
|
|
|
|
Foreign References |
|
|
Other References |
|
|
| Add a new Other reference: |
| Post related web sites and other references in this section |
| | Reference | Relevancy | Comments | Ronni T. Marshak, "IBM's FlowMark Object-Oriented Workflow for Mission-Critical Applications," Workgroup Computer Report, vol. 17, No. 5, XP
000568699, May 1994, 11 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | David Hollingsworth, "The Workflow Reference Model," Document No. TC00-1003, Workflow Management Coalition, Jan. 19, 1995, 55 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | Kerry W. Hassler et al., "Revolutionizing Definity.RTM. Call Centers in the 1990s," AT& T Technical Journal, Jul./Aug. 1995, 10 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | PCT International Search Report in International Application No. PCT/US 03/01759, dated Nov. 14, 2003, 7 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | International Search Report in International Application No. PCT/US 03/01684 dated Jun. 2, 2003, 8 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | International Search Report in International Application No. PCT/US 03/01685 dated Jun. 4, 2003, 8 pages. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | Dix, John; Teaming With Technology; Network World, vol. 11, No. 2; pp. SS8-SS16; ISBN: 00887-7661, Jan. 20, 1994. Jan. 10, 1994. cited by other
. Jul,2008 |      Your vote accepted [0 after 0 votes] | | Dix, John; Teaming With Technology; Network World, Jan. 10, 1994; http://www.findarticles.com. Nov. 6, 2006. cited by other. Jul,2008 |      Your vote accepted [0 after 0 votes] | | |
|
|
|
|
Other References |
|
|
|
|
|
References  |
|
|
|
|
|
|
|
|
|
|
|
Public's "Guesstimation" of Royalty Value
| |
|
|
|
|
|
|
|
|
|
|
|
|
Market Review  |
|
|
Technical Review  |
|
|
Claims  |
|
|
What is claimed is:
1. A system for implementing a recording plan based upon the presence of a client, comprising: one or more processing units; a client monitor operable to, when executed by
at least one of the one or more processing units, generate a presence message signifying the presence of a client on a network associated with the system, wherein the presence message comprises a presence type and a client identity; and a plan manager
operable to, when executed by at least one of the one or more processing units: receive the presence message from the client monitor; retrieve a plan template in response to receiving the presence message, wherein the plan template is retrieved based
upon the client identity and the presence type; and create a recording plan associated with the client based at least in part upon the plan template.
2. The system of claim 1, wherein the network comprises at least one of a voice network and a data network, wherein the presence type indicates the presence of the client on at least one of the voice network and the data network.
3. The system of claim 1, wherein the plan template comprises a plurality of recording parameters, trigger information, and participant information.
4. The system of claim 3, wherein the recording parameters define a number of recordings to be made for a plan period.
5. The system of claim 3, wherein the recording parameters further define a recording pattern according to which the recordings are made during the plan period.
6. The system of claim 3, wherein the recording parameters further define a type of recordings to be made.
7. The system of claim 3, wherein the trigger information comprises a plurality of trigger conditions used to initiate recording of at least one of a voice session and a data session conducted by the client.
8. The system of claim 1, wherein the plan manager is further operable to retrieve client information based upon the client identity, in response to receiving the presence message, and to create the recording plan further based upon the client
information.
9. The system of claim 8, wherein the plan template indicates a plan period and the client information indicates client availability for at least a portion of the plan period.
10. The system of claim 9, wherein the plan manager is further operable to assign a priority to the recording plan based at least in part upon the client availability.
11. The system of claim 1, wherein the recording plan comprises a plurality of trigger conditions used to initiate recording of at least one of a voice session and a data session conducted by the client.
12. The system of claim 11, wherein the trigger conditions are based upon computer telephony interface (CTI) events.
13. The system of claim 11, wherein the trigger conditions are based upon keyboard entries at a computer associated with the client.
14. The system of claim 11, wherein the trigger conditions are based upon an application launched at a computer associated with the client.
15. The system of claim 1, wherein the recording plan comprises recording instructions.
16. The system of claim 15, wherein the recording instructions define a number of recordings to be made for a plan period.
17. The system of claim 16, wherein the recording instructions define a recording pattern according to which the recordings are made for the plan period.
18. The system of claim 17, wherein the recording pattern comprises at least one of a random pattern, a first available pattern, a manual pattern, and a dispersion pattern.
19. The system of claim 1, further comprising a record manager communicatively coupled to the plan manager, wherein the recording plan comprises at least a voice recording plan, and the plan manager is further operable to communicate the voice
recording plan to the record manager.
20. The system of claim 19, further comprising a trigger manager communicatively coupled to the plan manager, wherein the voice recording plan comprises a plurality of trigger conditions, and the plan manager is further operable to communicate
the voice recording plan to the trigger manager.
21. The system of claim 20, wherein the trigger manager generates a record command in response to detecting at least one of the trigger conditions, and wherein the record manager records a voice session conducted by the client, in response to
the record command.
22. The system of claim 19, wherein the record manager records a voice session conducted by the client, according to the voice recording plan.
23. The system of claim 22, further comprising a session manager communicatively coupled to the record manager, wherein the record manager communicates a request message to the session manager and records the voice session according to the
voice recording plan if it receives an authorization communicated by the session manager.
24. The system of claim 1, further comprising a client manager operating on a computer associated with the client, wherein the recording plan comprises at least a data recording plan, and the plan manager is further operable to communicate the
data recording plan to the client manager.
25. The system of claim 24, wherein the client manager records a data session conducted by the client, in response to detecting at least one trigger condition associated with the data recording plan.
26. The system of claim 25, further comprising a session manager communicatively coupled to the client manager, wherein the client manager communicates a request message to the session manager and records the data session according to the data
recording plan if it receives an authorization communicated by the session manager.
27. The system of claim 1, further comprising: a record manager communicatively coupled to the plan manager; and a client manager operating on a computer associated with the client; wherein the recording plan comprises a data recording plan
and a voice recording plan, and the plan manager is further operable to communicate the voice recording plan to the record manager and to communicate the data recording plan to the client manager.
28. The system of claim 27, wherein the record manager records a voice session conducted by the client, according to the voice recording plan.
29. The system of claim 28, further comprising a session manager communicatively coupled to the record manager, wherein the record manager communicates a request message to the session manager and records the voice session according to the
voice recording plan if it receives an authorization communicated by the session manager.
30. The system of claim 29, wherein the session manager generates a record command in response to the request message communicated by the record manager, and wherein the client manager records a data session conducted by the client in response
to the record command.
31. The system of claim 27, wherein the client manager records a data session conducted by the client, in response to detecting at least one trigger condition associated with the data recording plan.
32. The system of claim 31, further comprising a session manager, wherein the client manager communicates a request message to the session manager and records the data session according to the data recording plan if it receives an authorization
communicated by the session manager.
33. The system of claim 32, wherein the session manager generates a record command in response to the request message communicated by the client manager, and wherein the record manager records a voice session conducted by the client in response
to the record command.
34. The system of claim 1, further comprising a trigger manager, wherein the recording plan comprises a master recording plan, and the plan manager is further operable to communicate the master recording plan to the trigger manager.
35. The system of claim 34, wherein the trigger manager generates a record command in response to detecting at least one trigger condition associated with the master recording plan, and further comprising a record manager that records a voice
session conducted by a client in response to the record command.
36. The system of claim 1, wherein the network comprises a voice network and further comprising a call manager operable to: determine that the client has logged into the voice network; and communicate a message to the client monitor
identifying the client.
37. The system of claim 36, wherein the voice network comprises a computer telephony interface (CTI) server and the call manager determines that the client has logged into the voice network in response to receiving a CTI event message.
38. The system of claim 1, wherein the network comprises a data network and further comprising a client manager operating on a computer associated with the client and operable to: determine that the client has logged into the data network; and
communicate a message to the client monitor identifying the client.
39. A system for implementing a recording plan based upon the presence of a client, comprising: a memory operable to store a plurality of plan templates and client information; and a processor coupled to the memory and operable to: receive a
presence message signifying the presence of a client on a network associated with the system, the presence message comprising a presence type and a client identity; retrieve a plan template from the memory in response to receiving the presence message,
wherein the plan template is retrieved based upon the client identity and the presence type; and create a recording plan associated with the client based at least in part upon the plan template.
40. The system of claim 39, wherein the network comprises at least one of a voice network and a data network, wherein the presence type indicates the presence of the client on at least one of the voice network and the data network.
41. The system of claim 39, wherein the plan template comprises a plurality of recording parameters, trigger information, and participant information.
42. The system of claim 39, wherein the processor is further operable to retrieve client information based upon the client identity, in response to receiving the presence message, and to create the recording plan further based upon the client
information.
43. The system of claim 42, wherein the plan template indicates a plan period and the client information indicates client availability for at least a portion of the plan period.
44. The system of claim 39, wherein the recording plan comprises a plurality of trigger conditions used to initiate recording of at least one of a voice session and a data session conducted by the client.
45. The system of claim 39, wherein the recording plan comprises recording instructions.
46. The system of claim 45, wherein the recording instructions define a number of recordings to be made for a plan period.
47. The system of claim 46, wherein the recording instructions define a recording pattern according to which the recordings are made for the plan period.
48. The system of claim 47, wherein the recording pattern is at least one of a random pattern, a first available pattern, a manual pattern, and a dispersion pattern.
49. The system of claim 39, wherein the recording plan comprises a voice recording plan and the processor is operable to record a voice session conducted by the client, according to the voice recording plan.
50. The system of claim 39, wherein the recording plan comprises a data recording plan and a computer associated with the client is operable to record a data session conducted by the client, according to the data recording plan.
51. A method for implementing a recording plan based upon the presence of a client, comprising: receiving a presence message signifying the presence of a client, the presence message comprising a presence type and a client identity; retrieving
a plan template in response to receiving the presence message, wherein the plan template is retrieved based upon the client identity and the presence type; and creating a recording plan associated with the client based at least in part upon the plan
template.
52. The method of claim 51, wherein the presence type indicates the presence of the client on at least one of a voice network and a data network.
53. The method of claim 51, wherein the plan template comprises a plurality of recording parameters, trigger information, and participant information.
54. The method of claim 51, further comprising retrieving client information based upon the client identity, and wherein the step of creating comprises creating the recording plan further based upon the client information.
55. The method of claim 54, wherein the plan template indicates a plan period and the client information indicates client availability for at least a portion of the plan period.
56. The method of claim 51, wherein the recording plan comprises a plurality of trigger conditions used to initiate recording of at least one of a voice session and a data session conducted by the client.
57. The method of claim 51, wherein the recording plan comprises recording instructions.
58. The method of claim 57, wherein the recording instructions define a number of recordings to be made for a plan period.
59. The method of claim 58, wherein the recording instructions define a recording pattern according to which the recordings are made for the plan period.
60. The method of claim 59, wherein the recording pattern is at least one of a random pattern, a first available pattern, a manual pattern, and a dispersion pattern.
61. The method of claim 51, wherein the recording plan comprises a voice recording plan and further comprising recording a voice session conducted by the client, according to the voice recording plan.
62. The method of claim 51, wherein the recording plan comprises a data recording plan and further comprising recording a data session conducted by the client, according to the data recording plan. |
|
|
|
|
Claims  |
|
|
Description  |
|
|
CROSS-REFERENCE TO RELATED APPLICATIONS
This application is related to and filed concurrently with U.S. patent application Ser. No. 10/071,555 filed Feb. 8, 2002, entitled "System and Method for Implementing Recording Plans Using a Session Manager" issued as U.S. Pat. No.
6,801,618 on Oct. 5, 2004, and pending U.S. patent application Ser. No. 10/072,431 filed Feb. 8, 2002, entitled "System and Method for Processing Work According to an Active Work Model". These applications have been commonly assigned to e-talk
Corporation.
TECHNICAL FIELD OF THE INVENTION
This invention relates generally to communication systems, and more particularly to a system for implementing recording plans using a presence-based plan manager.
BACKGROUND OF THE INVENTION
Call centers provide a wide array of services through sessions that may include both a voice session and a data session. In a call center environment, it is important to record, store, and communicate voice and data sessions efficiently. Prior
call center systems provided rigid schedules against which voice and/or data sessions were recorded for a particular service representative. A drawback to this approach is that the work schedule of a particular service representative may not be
consistent with the recording schedule that is established. This may cause the call center to dedicate hardware and/or software resources unnecessarily.
SUMMARY OF THE INVENTION
In accordance with the present invention, a system and method for implementing a recording plan using a presence-based plan manager are provided that substantially eliminate or reduce disadvantages or problems associated with previously developed
communication systems and methods.
According to one embodiment, a system for implementing a recording plan based upon the presence of a client includes a client monitor and a plan manager. The client monitor generates a presence message signifying the presence of a client on a
network associated with the system. The presence message comprises a presence type and a client identity. The plan manager receives the presence message from the client monitor and, in response, retrieves a plan template based upon the client identity
and the presence type. The plan manager creates a recording plan associated with the client based at least in part upon the plan template.
According to another embodiment, a system for implementing a recording plan comprises a first record manager, a second record manager, and a session manager. The first record manager generates a first message that comprises a request to record a
first session according to a recording plan, wherein the first session is conducted by a client associated with the recording plan. The session manager is communicatively coupled to the first record manager and the second record manager. The session
manager generates a second message for communication to the first record manager. The second message comprises an authorization to record the first session. The session manager further generates a third message for communication to the second record
manager. The third message comprises a command to record a second session.
Depending on the specific features implemented, particular embodiments of the present invention may exhibit some | | |