Method Of Providing Routing Information To Contact Center
Abstract:
A contact center receives an image and processes the image to identify useful information. From this information, a routing parameter is obtained for use in 5 routing a contact relating to that image to an agent or other resource of the contact center. In this way a received image can be employed to route a contact
Specification
FORM 2
THE PATENTS ACT, 1970 (39 of 1970)
& THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[See section 10, Rule 13]
METHOD OF PROVIDING ROUTING
INFORMATION TO CONTACT CENTER;
NORTEL NETWORKS LIMITED., A
CORPORATION ORGANIZED AND EXISTING UNDER THE LAWS OF CANADA, WHOSE ADDRESS )S 2351 BOULEVARD ALFRED-NOBEL, ST. LAURENT, QUEBEC H4S 2A9, CANADA.
THE FOLLOWING SPECIFICATION
PARTICULARLY DESCRIBES THE INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.
TECHNICAL FIELD
This invention relates to routing of contacts in a contact center. 5 BACKGROUND ART
Contact centers provide for communications between external parties {referred to herein as "customers") and resources of the contact center. These contact center resources are most usually human agents who speak with or message 10 interactively with the customer, but can also be automated resources, such as interactive applications which are responsive to voice or keypad inputs or received messages, artificially intelligent agents, and recorded media playback applications.
Contact centers typically have limited resources, and these resources are typically 15 quite specialised, so that for optimum operation of the contact center, a received contact must be analysed and directed to the most appropriate resource. Since the most appropriate resource may be busy, queuing mechanisms are common in contact centers, but there is nevertheless a need to place contacts in the most appropriate queue according to the information available to the contact center.
20
The term "intrinsic" is used within the art to mean a piece of information associated with a contact which may be used by a contact center to assist in determining a suitably skilled resource of the contact center to handle that contact. Typically, the intrinsics used by a conventional contact center to route a contact may include: 25 - the number dialled by the customer to access the contact center
- the media type being used for the contact (e.g. voice, video, instant messaging, SMS (short messaging service) text messages, email, etc.)
- the customer's own number, IP address, IM or email address, etc.
- stored history and account information relating to the customer
30 - inputs provided by the customer during the contact session, such as responses to interactive voice prompts, menu choices navigated after connecting, etc.
Mediaseek Inc. of Tokyo, Japan, provide an image processing application which can reside on a mobile telephone platform (see www.camreader.ip/enqlish/barcord reader.html). Using the mobile telephone's onboard camera, images can be taken of encoded information, such as a barcode 5 or of a piece of text, and the image processing application processes the image to decode the barcode or text. This decoded information can be used to create an entry in a contact list, to launch an email or a phone call to an encoded address or number, or to launch a web browser to an encoded URL, for example.
10 WO 2006/045729 discloses a mobile telephone equipped with a radio-frequency identification (RFID) chip reader. The RFID reader reads information stored in an RFID chip, and this information is sent to a contact center where it can be used as an intrinsic to help route the contact. The RFID chip may, for example, be located in a billboard advertisement or in a magazine, so that the transmission of
15 information embedded in the RFID chip provides contextual information to the contact center. This system is very limited in its application, being restricted to contacts coming from customers who (a) have a handset equipped with an RFID reader, (b) have encountered an RFID chip which has been read by their handset, and
Documents
Application Documents
| # |
Name |
Date |
| 1 |
1790-MUMNP-2010-FORM 3 (29-09-2014).pdf |
2014-09-29 |
| 2 |
1790-MUMNP-2010-CORRESPONDENCE(29-09-2014).pdf |
2014-09-29 |
| 2 |
1790-mumnp-2010-abstract.doc |
2018-08-10 |
| 3 |
abstract1.jpg |
2018-08-10 |
| 4 |
1790-mumnp-2010-wo international publication report a1.pdf |
2018-08-10 |
| 5 |
1790-mumnp-2010-form pct-ro-101.pdf |
2018-08-10 |
| 6 |
1790-mumnp-2010-form pct-isa-237.pdf |
2018-08-10 |
| 7 |
1790-mumnp-2010-form pct-isa-210.pdf |
2018-08-10 |
| 8 |
1790-mumnp-2010-form pct-ib-373.pdf |
2018-08-10 |
| 9 |
1790-mumnp-2010-form pct-ib-308.pdf |
2018-08-10 |
| 10 |
1790-mumnp-2010-form pct-ib-306.pdf |
2018-08-10 |
| 11 |
1790-mumnp-2010-form pct-ib-304.pdf |
2018-08-10 |
| 12 |
1790-mumnp-2010-form pct-ib-301.pdf |
2018-08-10 |
| 13 |
1790-mumnp-2010-form 5.pdf |
2018-08-10 |
| 14 |
1790-mumnp-2010-form 3.pdf |
2018-08-10 |
| 15 |
1790-mumnp-2010-form 2.pdf |
2018-08-10 |
| 17 |
1790-mumnp-2010-form 2(title page).pdf |
2018-08-10 |
| 18 |
1790-mumnp-2010-form 13.pdf |
2018-08-10 |
| 19 |
1790-mumnp-2010-form 1.pdf |
2018-08-10 |
| 20 |
1790-mumnp-2010-drawing.pdf |
2018-08-10 |
| 21 |
1790-mumnp-2010-description(complete).pdf |
2018-08-10 |
| 22 |
1790-mumnp-2010-correspondence.pdf |
2018-08-10 |
| 23 |
1790-mumnp-2010-claims.pdf |
2018-08-10 |
| 25 |
1790-mumnp-2010-claims(amended).pdf |
2018-08-10 |
| 26 |
1790-mumnp-2010-abstract.pdf |
2018-08-10 |
| 28 |
1790-MUMNP-2009-FORM 13(30-9-2009).pdf |
2018-08-10 |