This application is related to United States Patent Application having Ser. No. 13/803,331 entitled “MOBILE MESSAGE ENABLING ENTERPRISE OFFICE TELEPHONE NUMBERS,” filed Mar. 14, 2013 and United States Patent Application having Ser. No. 14/453143 entitled “CALL CENTER MOBILE MESSAGING,” filed Aug. 6, 2014. This application is also related to United States Patent Application entitled “CALL CENTER A2P-TO-P2P MESSAGE ROUTING CONVERSION,” filed on an even date herewith. The entire teachings and contents of these Patent Applications are hereby incorporated by reference herein in their entireties.
The present invention relates to Person-to-Person (P2P) messaging, call center operations, language translation and routing and enterprise communications with customer mobile devices.
Conventional Person to Person (P2P) messaging includes messaging between two mobile subscribers. Often a customer would like to contact a call center using messaging communications. One challenge is a language barrier when a customer contacts a call center with an SMS or MMS message in a language other than primary language of the call center staff. In this case, the message cannot be read or understood. For example, a message comes into the call center in Spanish, but majority of customer service representatives (CSRs) are conversant in English only. In this case the call center misses an opportunity to service a customer through the customer's selected means of communication.
Methods and devices disclosed herein enable recognition of a language in a message directed to a call center and if the language is a foreign language with respect to the native language of the call center, the message can be automatically forwarded to a customer service representative (CSR) or other person capable of reading, understanding the message and replying to the message. Auto-response to an incoming message acknowledging the incoming message in its native language can also be provided. In one embodiment a call center is SMS/MMS enabled, to receive messages in various foreign languages. In another embodiment, the message is translated either automatically or manually and sent to a CSR.
These features are achieved in accordance with one embodiment by a method including: determining a language capability of enterprise call center and provisioning at least one alternate destination device by registering the at least one alternate destination device in a messaging hub and associating the at least one alternate destination device with associating the at least one alternate destination device with the enterprise call center and language capability. The method further includes establishing a connection between the messaging hub and a message interface, receiving a message directed to the enterprise call center, receiving a message directed to the enterprise, determining the language of the message, determining an alternate destination for the message and diverting the message to the at least one alternate destination. The message interface can be an SMS interface including at least one of an SMS/MMS Gateway, an IP messaging Gateway or a short message service center/multimedia message service center (SMSC/MMSC).
Such a method enables the automatic recognition of messages in foreign languages and routing, to an appropriate machine or person able to understand and interpret the message in the foreign language. In one embodiment, an auto-response acknowledgement of receipt of the message is sent.
In another embodiment, one alternate destination for the message is a language translator and the technique further comprises translating the message and sending the message to a default destination. In a further embodiment, one alternate destination is a call center and the technique further comprises establishing a secure connection between the messaging hub and a call center interface. In yet another embodiment, the alternate destination is a data enabled device and the technique further comprises establishing a secure IP connection between the messaging hub and the data enabled device. The message interface is an SMS interface includes, but is not limited to an SMS/MMS Gateway, an IP messaging Gateway and an SMSC/MMSC.
In another embodiment, determining the language of the message includes determining that the message is in a foreign language and parsing a predetermined number of words to provide input into a language database for identification of the language. In still another embodiment, determining that the message is in a foreign language and identifying the language includes analyzing a character set of text in the message. In another embodiment, determining an alternate destination for the message includes comparing the language capability of an enterprise call center with the determined language of the message.
In another embodiment, determining an alternate destination for the message includes determining a geographical origin of the message and determining the alternate destination based on the geographical origin of the message. In another embodiment, the message is an SMS message or an MMS message.
A messaging hub for routing a foreign language message includes a server connected to a message interface, a database running on the server for registering at least one data enabled device and the language capability of an enterprise call center, an incoming message queue for storing a message and a diverter for directing the message to the at least one data enabled device as an alternate destination for the message. The messaging hub diverter can further include a message language scanner coupled to the incoming message queue.
A non-transitory computer readable storage medium includes executable instructions, which when executed by a computer, cause the computer to: determine a language capability of call center and provision at least one alternate destination device. The provisioning includes registering the at least one alternate destination in the messaging hub and associating the at least one alternate destination with the enterprise call center and a language capability. The computer further establishes a connection between the messaging hub and a message interface, receives a message directed to the enterprise, determines the language of the message, determines an alternate destination for the message and diverts the message to the at least one alternate destination.
It is to be understood that the features of the messaging hub and call center can be embodied strictly as a software program, as software and hardware, or as hardware alone such as within a single processor or multiple processors, or within an operating system or within a software application.
Other embodiments of the invention that are disclosed herein include software programs to perform the steps and operations summarized above and disclosed in detail below. One such embodiment comprises a computer program product that has a non-transitory computer readable medium including computer program logic encoded thereon that, when performed in a computerized device having a coupling of a memory and a processor and a display, programs the processor to perform the operations disclosed herein. Such arrangements are typically provided as software, code and/or other data (e.g., data structures) arranged or encoded on a computer readable medium such as an optical medium (e.g., CD-ROM), hard disk or other a medium such as firmware or microcode in one or more ROM or RAM or PROM chips or as an Application Specific Integrated Circuit (ASIC). The software or firmware or other such configurations can be installed onto a computerized device to cause the computerized device to perform the techniques explained herein. Other configurations include web applications, browsers, IP applications and data enabled device applications as will be explained in more detail.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of embodiments of the invention, as illustrated in the accompanying drawings and figures in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis instead being placed upon illustrating the embodiments, principles and concepts of the invention. These and other features of the invention will be understood from the description and claims herein, taken together with the drawings of illustrative embodiments, wherein
In an exemplary embodiment, a message sent by a customer using a language which is foreign to a call center can be diverted/redirected to an alternate destination that is enabled to more efficiently handle the foreign language instead of just deleting or ignoring the reply. The alternate destination can be an enterprise's call center for handling the reply or possibly an enterprise department which is suited to handle the reply. Alternatively the message is translated and forwarded onto the call center with an indication that follow-on messages may need special handling.
In one embodiment, such features are facilitated by a messaging hub which manages the P2P DID and 800 number traffic of the enterprise and messages directed to the call center. In certain embodiments the messaging hub facilitates SMS communications between consumers and call centers and other departments within an enterprise.
Now referring to
The messaging hub 100 can communicate with customer devices 30 through a mobile network operator (MNO) 23 via an SMS interface 201 (local to messaging hub 100) and SMS interface 20r (remote from messaging hub 100). The SMS interface can include interconnected systems such as short message service center/multimedia message service center (SMSC/MMSC) both local and remote, SMS/MMS Gateways and IP messaging Gateways. The SMS interface 12 is a network element in the network environment 10. One of the SMS interface's 12 purposes is to store, forward, convert and deliver SMS/MMS messages to the MNO 23 and messaging hub 100. The link between the messaging hub 100 and the global messaging infrastructure 22 and the link between the messaging hub 100 and the call center 50 can be secured by the firewall 102 using a virtual private network (VPN) secure IP connection with HTTPS using 128-bit or higher encryption, for example, 1024 bit (3DES-SHA1) encryption. The messaging hub 100 can optionally communicate with a translator 76 (e.g., a machine translation service). It is understood that the functions of the translator 76 can be incorporated into the messaging hub 100.
In operation, the messaging hub 100 in one embodiment provisions the call center 50, an alternative call center 68 and the employee devices 26 as alternate destinations for messages addressed. The messaging hub 100 also establishes a secure connection to the SMS interface 12 to send and receive SMS messages which are processed by MNO 23. The provisioning process is described in more detail below in conjunction with
After provisioning, the messaging hub 100 receives a message from the customer device 30 in response to a query by a customer. After receiving the message, the messaging hub 100 determines whether the message is a foreign language and if so either diverts the message to an alternate destination which can handle the foreign language or translates the message and then forwards the message to the call center 50.
The messaging hub 100 communicates with the call center 50, in one embodiment, over a secure connection 60 (e.g., a VPN connection). The call center 50 generally includes a call director 52 or alternatively other systems for dispatching customer call to CSRs. The call center generally includes multiple workstations 53a-53n for use by the CSRs (collectively referred to as CSR workstation 53). In one embodiment, the messaging hub 100 and call center 50 communicate data, language capabilities, number provisioning information, messages and message thread information over the secure connection 60.
Now referring to
If it is determined that the message 148 is in a foreign language, the message 148 can be sent as a diverted message 144 to one of several alternate destinations including the call center 50, a department 133 associated with a registered alternate destination device 26 equipped to handle the foreign language, an alternate call center equipped to handle the foreign language, another registered alternate destination employee device 26 reached through the SMS interface 20. Alternatively, the message 148 can be sent as a message 142 to a translator 76. Thus the messaging hub 100 provides the ability to have two-way, one-to-one communication responding to a message in a foreign language.
The language scanner 121 scans the message 148 to determine if it is in a foreign language and the diverter decides which alternative destination should be used for diverting the message 148. In addition to scanning the message 148 text, the language scanner 121 can also scan the message 148 to determine a geographical origin of the message 148 to use in the language determination, translation and routing process. The diverter can then select the alternate destination based on language detection and parameters such as the geographical origin.
For example, based on an origin phone number from a country different from the enterprise call center the message 148 could be diverted (if found to be in a foreign language) to a different call center which has the capability of processing messages in that language. The message 148 can be diverted to a telephone number, a Customer Relationship Management (CRM) system, a non-telephone related messaging system or a call center depending on the language. The CRM, non-telephone related messaging system and call center can be integrated into the CRM and connected to the messaging hub 100.
If the messaging hub 100 determines that the message 148 includes words in a foreign language and there is no available call center or other alternate destination to process the message 148, the messaging hub 100 communicates with a translator 76 to translate the message. The translated message 144 can then be delivered to the call center 50 or alternate destination 133 as described below in further detail.
At the call center 50, the call director 52 can direct the translated or diverted message 144 to an assigned CSR (if translated) or to a CSR having the appropriate language skills. The call director 52 has the ability in conjunction with the messaging hub 100 to maintain the integrity of a customer query. In one embodiment, a graphical user interface running on the CSR workstation 53 allows the CSR to receive and compose SMS messages and to view or listen to multimedia attachments.
In one embodiment, the language scanner 121 is implemented as a ‘rules processor.’ It is supplied with relevant key words and phrases of interest which might be included in the SMS/MMS messages transmitted to and received from customers, and if there's a match, process an action which possibly leads to an alternative destination determination. In a specific embodiment the language scanner 121 is implemented as a dynamic IF-THEN-ELSE machine which can re-route a message, dump/trash a message or change priority of a message.
In one embodiment the following rules are used to process the message 148:
If the message is in native language of the call center, pass the message onto standard queues for processing by call center;
If the message is not in native language of the call center, parse several (e.g., a predetermined number) of words to provide input into a language database for identification of language;
Alternatively, the message can be forwarded to a non-call center telephone number (e.g., a department in the enterprise which has foreign language skill to handle the message 148).
To continue the P2P conversation, the CSR can reply with follow-on messages and the messaging hub 100 can store the parameters of the conversation /thread including language processing, translation, assigned CSR, detected the origin (customer DID). These parameters allow the messaging hub 100 to expedite the processing of future messages in the conversation thread.
During operational setup, a call center telephone number (or a block of numbers), origin identities, and numbers for some alternate destination devices are transferred to the messaging hub 100 and registered in the database 126. The call center telephone numbers, and numbers for some alternate destination devices are pushed or published into the database of the various directories, for example a carrier database 129 of the local SMS gateway 201 and/or industry databases 131a-131n of other SMS interfaces in the global messaging infrastructure 22. This allows replies from customers to be delivered to the messaging hub 100 for final delivery to the call center or other alternate destinations. The language capabilities of the enterprise are provisioned as described below in conjunction with step 410 in
Provisioning of the call center telephone numbers (obtained from the call center 50 through call center application 72 (which receives an SMS message 78) or other means, and messaging hub call center application 70 in the messaging hub 100) and alternate destination devices into all the assorted databases, public and private, in the global messaging infrastructure 22 requires recognition and allowance by the mobile operators for mobile messages from non-mobile operator sources to flow through the network. This recognition and allowance is provided in advance of provisioning of call center telephone numbers. As a result of provisioning by the messaging hub 100, the call center telephone numbers reside and are registered in databases that are queried by the SMSC/MMSCs and other mobile industry elements.
In
In step 430, a secure connection is established between the messaging hub and the call center interface. In one embodiment, the alternate destination device is a call center interface which can connect to multiple devices for text messaging. In step 440, a message directed to the enterprise is received. Processing continues in step 510 described below.
Now referring to In
In step 520 an alternate destination for the message is determined including in step 522 by comparing the language capability of the enterprise call center with the determined language of the message. Additional information can be used in determining an alternate destination for the message including determining a geographical origin of the message and determining an alternate destination for the message includes determining a geographical origin of the message and determining the alternate destination based on the geographical origin of the message. Additionally, parsed and translated key words such as ‘complain,’ buy,“return,”order' and ‘change’ can be used to select a department or specific call center representative as the alternate destination for the received message. Another technique for determining the alternate destination for the message in step 524 includes scanning the message, determining a geographical origin of the message Step 524 further includes determining the alternate destination based the geographical origin of the message. The geographical origin can also be used as an input in the language determination process.
In step 526, it is determined that there is no language capability to handle the message in the foreign language so the message must be translated if possible. In a further embodiment, the technique includes scanning the message, determining a source including telephone number of the message, accessing additional information about the source and determining an alternate destination based on the additional information. For example the enterprise might have information about a customer including a preferred language for messaging communication. This information could be supplied during customer registration or updated after a previous conversation where a language was associated with a corresponding telephone number.
Now referring to In
In step 640, an association between the telephone number of the origin of the diverted message and the alternate destination can be optionally stored. This allows the alternate destination to be reused to support further P2P conversations originating from a source (e.g., customer) whereby additional messages from the source can be diverted to a call center destination or a company department based on previous communications. In one embodiment, in step 650, the message is sent to the selected alternate destination or the call center 50. If the message is sent to the call center 50, the message can be directed to a specific CSR.
In another embodiment, in step 660, the message is translated and in step 670 the message is sent to the call center or other default destination. The message can be translated automatically or with manual (human translator) intervention.
Although the example and embodiments are described above with respect to SMS/MMS messaging, the present invention is not limited to SMS/MMS messaging. The methods disclosed herein can apply to other messaging environments as well as mixture of SMS/MMS with other messaging environments. Ongoing conversation threads can use a mixture of messaging environments. Alternatively, an entire conversation could include no SMS messaging. For example the conversation could occur entirely using Facebook Messenger, and switch between Facebook Messenger and more granular apps within Facebook Messenger.
While configurations of the system and method have been particularly shown and described with references to configurations thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention. As an example, the order of processing steps in the flow charts is not limited to the order shown herein. Accordingly, the present invention is not limited by the example configurations provided above.
Number | Name | Date | Kind |
---|---|---|---|
6415250 | van den Akker | Jul 2002 | B1 |
6449483 | Akhteruzzaman et al. | Sep 2002 | B1 |
6591103 | Dunn et al. | Jul 2003 | B1 |
6690932 | Barnier et al. | Feb 2004 | B1 |
6757365 | Bogard | Jun 2004 | B1 |
7002970 | Veschi | Feb 2006 | B1 |
7010312 | Zechlin | Mar 2006 | B1 |
7197035 | Asano | Mar 2007 | B2 |
7263076 | Leibovitz et al. | Aug 2007 | B1 |
7275104 | Martinez et al. | Sep 2007 | B1 |
7343168 | Valloppillil | Mar 2008 | B2 |
7380022 | Tell et al. | May 2008 | B2 |
7446655 | Jha et al. | Nov 2008 | B2 |
7499704 | Bonner | Mar 2009 | B1 |
7564958 | Contractor | Jul 2009 | B1 |
7606568 | Gallagher et al. | Oct 2009 | B2 |
7693535 | Dunko | Apr 2010 | B2 |
7716297 | Wittel et al. | May 2010 | B1 |
7734908 | Kung et al. | Jun 2010 | B1 |
7860525 | Parkkinen et al. | Dec 2010 | B2 |
7865198 | Shin | Jan 2011 | B2 |
7940896 | Prozeniuk et al. | May 2011 | B2 |
8463304 | Lauer et al. | Jun 2013 | B2 |
8520833 | Pettay et al. | Aug 2013 | B1 |
8561118 | Flynn-Ripley et al. | Oct 2013 | B2 |
8570906 | Croak et al. | Oct 2013 | B1 |
8578261 | Gupta et al. | Nov 2013 | B1 |
8694031 | Lew et al. | Apr 2014 | B2 |
8788599 | Harju et al. | Jul 2014 | B2 |
8890685 | Sookman et al. | Nov 2014 | B1 |
8918085 | Lew et al. | Dec 2014 | B2 |
8989712 | Doulton | Mar 2015 | B2 |
8989713 | Doulton | Mar 2015 | B2 |
9271129 | Lew et al. | Feb 2016 | B2 |
9286378 | Larakhovsky et al. | Mar 2016 | B1 |
9356907 | Lew et al. | May 2016 | B2 |
9456317 | Kornafeld | Sep 2016 | B2 |
9710982 | Matthews, III et al. | Jul 2017 | B2 |
20030101244 | Lockridge et al. | May 2003 | A1 |
20030185379 | OConnor et al. | Oct 2003 | A1 |
20030232623 | Balasuriya et al. | Dec 2003 | A1 |
20040076144 | Ishodoshiro | Apr 2004 | A1 |
20040109452 | Takihiro et al. | Jun 2004 | A1 |
20040137923 | Lang | Jul 2004 | A1 |
20050032518 | Rajan | Feb 2005 | A1 |
20050148353 | Hicks et al. | Jul 2005 | A1 |
20050149335 | Mesbah et al. | Jul 2005 | A1 |
20050181805 | Gallagher | Aug 2005 | A1 |
20050233733 | Roundtree et al. | Oct 2005 | A1 |
20050277407 | Ahn et al. | Dec 2005 | A1 |
20050288045 | Yang et al. | Dec 2005 | A1 |
20060025173 | Kamdar | Feb 2006 | A1 |
20060074628 | Elbaz | Apr 2006 | A1 |
20060075052 | Oostendorp | Apr 2006 | A1 |
20060123360 | Anwar et al. | Jun 2006 | A1 |
20060142012 | Kirchhoff et al. | Jun 2006 | A1 |
20060148495 | Wilson | Jul 2006 | A1 |
20060259473 | Li et al. | Nov 2006 | A1 |
20070026901 | McKay | Feb 2007 | A1 |
20070032225 | Konicek et al. | Feb 2007 | A1 |
20070066318 | Danzeisen et al. | Mar 2007 | A1 |
20070073585 | Apple et al. | Mar 2007 | A1 |
20070082664 | Landschaft et al. | Apr 2007 | A1 |
20070167178 | Al-Harbi | Jul 2007 | A1 |
20070190978 | White et al. | Aug 2007 | A1 |
20070203850 | Singh et al. | Aug 2007 | A1 |
20080032679 | Purontaus | Feb 2008 | A1 |
20080037456 | Chen | Feb 2008 | A1 |
20080043969 | Shi | Feb 2008 | A1 |
20080045250 | Hwang | Feb 2008 | A1 |
20080096588 | Waytena et al. | Apr 2008 | A1 |
20080114862 | Moghaddam | May 2008 | A1 |
20080140850 | Gade et al. | Jun 2008 | A1 |
20080172496 | Middleton et al. | Jul 2008 | A1 |
20080182563 | Wugofski et al. | Jul 2008 | A1 |
20080192908 | O'Keefe | Aug 2008 | A1 |
20080198987 | Daly | Aug 2008 | A1 |
20080263137 | Pattison et al. | Oct 2008 | A1 |
20080270556 | Bamford | Oct 2008 | A1 |
20080293404 | Scherzer et al. | Nov 2008 | A1 |
20090003312 | Velazquez et al. | Jan 2009 | A1 |
20090005005 | Forstall et al. | Jan 2009 | A1 |
20090017789 | Thomas et al. | Jan 2009 | A1 |
20090031232 | Brezina et al. | Jan 2009 | A1 |
20090063280 | Wurster et al. | Mar 2009 | A1 |
20090154434 | Tanaka et al. | Jun 2009 | A1 |
20090156179 | Hahn et al. | Jun 2009 | A1 |
20090156202 | Reiss et al. | Jun 2009 | A1 |
20090164564 | Willis | Jun 2009 | A1 |
20090186634 | Sureka | Jul 2009 | A1 |
20090201916 | Caron et al. | Aug 2009 | A1 |
20090249478 | Rosener et al. | Oct 2009 | A1 |
20090319914 | Roseway et al. | Dec 2009 | A1 |
20100029273 | Bennett | Feb 2010 | A1 |
20100035640 | Lew et al. | Feb 2010 | A1 |
20100037277 | Flynn-Ripley et al. | Feb 2010 | A1 |
20100124905 | Pratt et al. | May 2010 | A1 |
20100161722 | Jeon et al. | Jun 2010 | A1 |
20100262668 | Piett | Oct 2010 | A1 |
20100287215 | Lasensky | Nov 2010 | A1 |
20110045828 | Madan et al. | Feb 2011 | A1 |
20110070868 | Scholz et al. | Mar 2011 | A1 |
20110142211 | Maes | Jun 2011 | A1 |
20110195722 | Walter et al. | Aug 2011 | A1 |
20110238766 | Lew et al. | Sep 2011 | A1 |
20120165048 | Zhu | Jun 2012 | A1 |
20120221962 | Lew et al. | Aug 2012 | A1 |
20120226759 | Lew et al. | Sep 2012 | A1 |
20130078990 | Kim et al. | Mar 2013 | A1 |
20130080898 | Lavian et al. | Mar 2013 | A1 |
20130194135 | Farnham | Aug 2013 | A1 |
20130196697 | Lew et al. | Aug 2013 | A1 |
20130219262 | Becker et al. | Aug 2013 | A1 |
20130252649 | Siomina | Sep 2013 | A1 |
20130298037 | Matthews et al. | Nov 2013 | A1 |
20130310089 | Gianoukos et al. | Nov 2013 | A1 |
20140106701 | Silver et al. | Apr 2014 | A1 |
20140143435 | Jung et al. | May 2014 | A1 |
20140179260 | Malin | Jun 2014 | A1 |
20140198796 | Lew et al. | Jul 2014 | A1 |
20140269679 | Gillis et al. | Sep 2014 | A1 |
20140364082 | Baddeley et al. | Dec 2014 | A1 |
20150082198 | Destagnol et al. | Mar 2015 | A1 |
20150113082 | Lew et al. | Apr 2015 | A1 |
20150143224 | Kennedy | May 2015 | A1 |
20150149560 | Lee | May 2015 | A1 |
20150223271 | Penix et al. | Aug 2015 | A1 |
20160135020 | Moshir | May 2016 | A1 |
20170006161 | Riahi | Jan 2017 | A9 |
Number | Date | Country |
---|---|---|
2397730 | Jun 2006 | GB |
2431820 | May 2007 | GB |
2007015075 | Feb 2007 | WO |
Entry |
---|
European Search Report for corresponding European application No. 09805443.0, dated Dec. 11, 2013, total pp. 8. |
International Search Report and Written Opinion dated Dec. 7, 2011 in corresponding International Application No. PCT/US2011/037190. |
International Search Report for International Application No. PCT/US2009/052715 dated Sep. 24, 2009. |
International Search Report and the Written Opinion for International Application No. PCT/US2016/029667, 3 Pages, dated Aug. 5, 2016. |
International Search Report and the Written Opinion for International Application No. PCT/US2016/029665, 5 Pages, dated Aug. 11, 2016. |
International Search Report, PCT/US2016/029667, dated Aug. 5, 2016, pp. 3. |
Number | Date | Country | |
---|---|---|---|
20160321245 A1 | Nov 2016 | US |