CA2830711C

CA2830711C - Customer relationship management (crm) audio on hold

Info

Publication number: CA2830711C
Application number: CA2830711A
Authority: CA
Inventors: Matthew Marum
Original assignee: Sugarcrm Inc
Current assignee: Sugarcrm Inc
Priority date: 2013-10-23
Filing date: 2013-10-23
Publication date: 2018-07-10
Anticipated expiration: 2033-10-23
Also published as: CA2830711A1

Abstract

Embodiments of the present invention provide a method, system and computer program product for CRM audio on hold. In an embodiment of the invention, a CRM audio on hold method includes identifying a caller associated with the telephone call received in a call processing gateway, selecting a record in a CRM application pertinent to the caller and inserting the selected record into a variable field of a template. The method also includes text-to-speech (TTS) processing the template into audio and returning the audio to the call processing gateway for playback to the caller while the caller is on hold.

Description

CUSTOMER RELATIONSHIP MANAGEMENT (CRM) AUDIO ON HOLD
Matthew Marum BACKGROUND OF THE INVENTION
[0001] Field of the Invention

[0002] The present invention relates to CRM call processing and more particularly to caller on hold management in a CRM application.

[0003] Description of the Related Art

[0004] In business, beyond the sale of a product or service remains the fundamental management of the relationship between the vendor and the customer. CRM
applications seek to provide a foundation upon which business can manage the relationship with the customer from the moment in time before one becomes a customer to the moment in beyond which one becomes a customer. Modern CRM applications provide this foundation through a collection of well organized database records relating to all aspects of the customers and the products and services provided by the vendor to the customers.
A visual user interface presents a view to the database records so as to assist the business in visualizing the past, present and potentially future state of the relationship between the business and the customer.

[0005] CRM applications often are equipped to manage communications with customers. In the twenty-first century, a common mode of interacting with customers and even potential customers is electronic mail followed closely by instant messaging.

.
_ However, the venerable telephone call remains part and parcel of the business-to-customer relationship. With respect to telephone call processing in CRM, at the outset, what is required is the receipt of a telephone call from the customer to the vendor¨
typically a call center of the vendor. As it is well-understood, however, in many instances, more telephone calls are received in the call center than there are available persons to process the call. Alternatively, oftentimes, a caller is compelled to wait while a call center operator processes a request of the caller. In either instance, the caller is placed on hold.

[0006] Traditionally, when a caller is placed on hold, music is played over the telephone call so as to entertain the caller, and also to provide a mental cue that the telephone call has not been dropped. Alternatively, generic messaging is presented over the call, reminiscent of a paid television programming or an "infomercial". Of course, long hold periods for a caller can be frustrating¨especially when the caller seeks assistance with a purchased product or service, or where the caller is impatient in seeking information regarding a potential purchase of a product or service. The generically provided music for a caller on hold seldom acts to alleviate the impatience experienced by the caller on hold. Further, corporate propaganda pertaining to generic infomercial material certainly does not act to sooth the caller on hold.
BRIEF SUMMARY OF THE INVENTION

[0007] Embodiments of the present invention address deficiencies of the art in respect to caller on hold processing and provide a novel and non-obvious method, system and computer program product for CRM audio on hold. In an embodiment of the invention, a CRM audio on hold method includes identifying a caller associated with the telephone call received in a call processing gateway, selecting a record in a CRM
application pertinent to the caller and inserting the selected record into a variable field of a template.
The method also includes text-to-speech (TTS) processing the template into audio and returning the audio to the call processing gateway for playback to the caller while the caller is on hold.
100081 In another embodiment of the invention, a CRM data processing system can be configured for CRM audio on hold. The system can include a host computing system that includes at least one computer with memory and at least one processor and a database coupled to the host computing system. The system also includes a CRM
application executing in the memory of the host computing system and a call processing gateway processing telephone calls from callers over a public switched telephone network (PSTN). Finally, the system includes a CRM audio on hold module coupled to both the CRM application and the call processing module. The CRM audio on hold module includes program code enabled to identify a caller associated with a telephone call received in the call processing gateway, to select a record in a CRM
application pertinent to the caller, to insert the selected record into a variable field of a template, to text-to-speech (TTS) process the template into audio and to return the audio to the call processing gateway for playback to the caller while the caller is on hold.

, , [0009] Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
[0010] The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:
[0011] Figure 1 is a pictorial illustration of a process for CRM
audio on hold;
[0012] Figure 2 is a schematic illustration of a CRM data processing system configured for CRM audio on hold;
[0013] Figure 3 is a flow chart illustrating a process for CRM
audio on hold; and [0014] Figure 4 is a block diagram showing an exemplary computer system.

DETAILED DESCRIPTION OF THE INVENTION
[0015] Embodiments of the invention provide for CRM audio on hold. In an embodiment of the invention, a call can be received into a call processing portion of a CRM system. A caller associated with the call can be determined by lookup of CRM
contact records. Thereafter, responsive to the placement of the call on hold, a selection of records specific to the caller can be retrieved into memory and text-to-speech processed into audio corresponding to the selection of records. The audio corresponding to the selection of records can be complimented with generic audio of a template and providing context for the selected records. Thereafter, the audio in turn can be presented to the caller while the caller remains on hold. In this way, while the caller remains on hold, the caller on hold at least can receive information pertinent to the caller, such as a list of open cases in the CRM application and a status of those open cases.
[0016] In further illustration, Figure 1 pictorially shows a process for CRM audio on hold. As shown in Figure 1, a call can be established as between a caller 110 and a call processing gateway 120 over a PSTN 130. The call processing gateway 120 can place the caller 110 on hold and the call processing gateway 120 can provide to CRM
audio on hold logic 170 call data 150. The call data 150 can include the identity of the caller 110 and a context of the call. The context of the call can include, by way of example, an expected duration of time during which the caller 110 will remain on hold, a status of one or more records related to the caller 110, a preference of the caller 110 to receive particular information while on hold, a job title or department associated with the caller 110, whether the call originates from a home phone number or business phone number of the caller 110, and the time of day or the date of the call, including whether or not the call has occurred during or after business hours.
[0017] Using the call data 150, the CRM audio on hold logic 170 can select a contextual template 160. The contextual template 160 can include a textual script with variable fields reserved for data specific to different individuals. For instance, the textual script can relate to a status of an open trouble ticket or customer issue record of the caller 110, the textual script can relate to current announcements of products associated with the type of job or department of the caller 110, or the textual script can relate to a knowledgebase article of one or more products associated with the caller 110, to name only three possibilities. Utilizing CRM data 190 retrieved from a CRM system 140, the CRM audio on hold logic 170 can replace the variable fields of the selected one of the contextual templates 160 with the CRM data 190 to produce a completed one of the templates 190. Thereafter, the completed one of the templates 190 can be text-to-speech (TTS) processed and returned to the call processing gateway 120 as speech audio 180.
The speech audio 180 in turn can be played back to the caller 110 while the caller 110 remains on hold.
[0018] The process described in connection with Figure 1 can be implemented in a CRM data processing system. In yet further illustration, Figure 2 schematically shows a CRM data processing system configured for CRM audio on hold. The system can include a call processing gateway 210 configured for telecommunicative linkage to different telephone endpoint devices 220 over a PSTN 230. The call processing gateway , 210 further can be configured for data communicative coupling to a CRM system over a data communications network 240.
[0019] The CRM system 280 can include one or more computers, each with memory and at least one processor, and collectively supporting the execution of a CRM

application (not shown) configured to provide access to CRM data 250. The CRM
system 280 can be coupled to a CRM audio on hold module 300 and can include program code enabled upon execution in the memory of a computer to respond to the receipt of call data from the call processing gateway 210 to select one or more contextual templates 260 based upon one or more template selection rules 270.
[0020] The contextual templates 260 each can include generic text and one or more variable fields into which corresponding records from the CRM data 250 are to be inserted. The rules 270 in turn can include, by way of example, rules that accept as input a context of a call including an identity of a caller, a nature of an expected hold time for the caller, or both. The rules 270 further can specify based upon the context one or more templates 260 to be selected for use by the CRM audio on hold module 300 in producing speech audio for playback to a caller on hold. For example, with respect to an expected hold time for a caller on hold that is short in duration, a template of limited content can be selected, whereas with respect to an expected hold time for a caller on hold that is long in duration, a template of extensive content can be selected.
[0021] Once one or more of the contextual templates 260 has been selected by the program code of the CRM audio on hold module 300 based upon the application of one , , or more of the rules 270, the program code of the CRM audio on hold module 300 can be enabled to retrieve one or more records from the CRM data 250 for an identified caller on hold in order to complete the selected one of the contextual templates 260.
Subsequently, the program code of the CRM audio on hold module 300 can direct the TTS
processing of the complete one or more of the templates 260 in order to produce speech audio.
Finally, the program code of the CRM audio on hold module 300 can be enabled to return the speech audio to the call processing gateway 210 for playback to the caller on hold.
100221 In even yet further illustration of the operation of the CRM audio on hold module 300, Figure 3 is a flow chart illustrating a process for CRM audio on hold.
Beginning in block 310, a caller identity of a call can be received from a call processing gateway for a caller on hold. In block 320, a context for the call can be received and in block 330, a template can be selected based upon the context. In block 340, one or more variable fields can be identified and in block 350, CRM data for the identified caller can be retrieved for inclusion in the selected template according to the variable fields in block 360.
[0023) In block 370, the template with CRM data for the identified caller placed in the variable fields can be TTS processed to produce speech audio. Optionally, the TTS
processing can occur in a remote TTS service receiving the completed template from over a data communications network and returning the speech audio over the data communications network. Finally, in block 380 the speech audio can be provided to the call processing gateway for playback to the caller on hold.

8 100241 Aspects of the present technology have been described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to various embodiments. In this regard, the flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present technology. For instance, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
100251 It also will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a

9 machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
[0026] These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
100271 An illustrative computer system in respect of which the methods herein described may be implemented is presented as a block diagram in Figure 4. The illustrative computer system is denoted generally by reference numeral 400 and includes a display 402, input devices in the form of keyboard 404A and pointing device 404B, computer 406 and external devices 408. While pointing device 404B is depicted as a mouse, it will be appreciated that other types of pointing device may also be used.

, [0028] The computer 406 may contain one or more processors or microprocessors, such as a central processing unit (CPU) 410. The CPU 410 performs arithmetic calculations and control functions to execute software stored in an internal memory 412, preferably random access memory (RAM) and/or read only memory (ROM), and possibly additional memory 414. The additional memory 414 may include, for example, mass memory storage, hard disk drives, optical disk drives (including CD and DVD drives), magnetic disk drives, magnetic tape drives (including LTO, DLT, DAT and DCC), flash drives, program cartridges and cartridge interfaces such as those found in video game devices, removable memory chips such as EPROM or PROM, emerging storage media, such as holographic storage, or similar storage media as known in the art. This additional memory 414 may be physically internal to the computer 406, or external as shown in Figure 4, or both.
[0029] The computer system 400 may also include other similar means for allowing computer programs or other instructions to be loaded. Such means can include, for example, a communications interface 416 which allows software and data to be transferred between the computer system 400 and external systems and networks.

Examples of communications interface 416 can include a modem, a network interface such as an Ethernet card, a wireless communication interface, or a serial or parallel communications port. Software and data transferred via communications interface 416 are in the form of signals which can be electronic, acoustic, electromagnetic, optical or other signals capable of being received by communications interface 416.
Multiple interfaces, of course, can be provided on a single computer system 400.

, .
[0030] Input and output to and from the computer 406 is administered by the input/output (I/O) interface 418. This I/0 interface 418 administers control of the display 402, keyboard 404A, external devices 408 and other such components of the computer system 400. The computer 406 also includes a graphical processing unit (GPU) 420. The latter may also be used for computational purposes as an adjunct to, or instead of, the (CPU) 410, for mathematical calculations.
[0031] The various components of the computer system 400 are coupled to one another either directly or by coupling to suitable buses.
[0032] The term "computer system", as used herein, is not limited to any particular type of computer system; in one preferred embodiment the methods described herein are carried out by one or more servers.
[0033] As will be appreciated by one skilled in the art, aspects of the technology described herein may be embodied as a system, method or computer program product.
Accordingly, aspects of the technology described herein may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system."
Furthermore, aspects of the presently described technology may take the form of a computer program product embodied in one or more computer readable medium(s) carrying computer readable program code.

[0034] Where aspects of the technology described herein are implemented as a computer program product, any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. Thus, computer readable program code for implementing aspects of the technology described herein may be contained or stored in the memory 412 of the computer 406, or on a computer usable or computer readable medium external the computer 406, or on any combination thereof.
[0035] A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
[0036] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radiofrequency, and the like, or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the presently described technology may be written in any combination of one or more programming languages, including an object oriented programming language and conventional procedural programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
[0037] Finally, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises"

, , and/or "comprising", when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
100381 The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the claims. The embodiment was chosen and described in order to best explain the principles of the technology and the practical application, and to enable others of ordinary skill in the art to understand the technology for various embodiments with various modifications as are suited to the particular use contemplated.
[0039] One or more currently preferred embodiments have been described by way of example. It will be apparent to persons skilled in the art that a number of variations and modifications can be made without departing from the scope of the claims. In construing the claims, it is to be understood that the use of a computer to implement the embodiments described herein is essential. Accordingly, claims directed to a method include changes in state of the processor and memory as essential elements of those claims, claims directed to computer program products include a computer readable storage medium as an essential element of those claims, and claims directed to a data processing system (computer) include the data processing system (computer) as an essential element.

Claims

We claim:

1. A customer relationship management (CRM) audio on hold method comprising:
identifying in memory of a computer a caller associated with the telephone call received in a call processing gateway;
selecting by a processor of the computer a record in a CRM application pertinent to the caller;
inserting by the processor of the computer the selected record into a variable field of a template selected according to a context of the call and text-to-speech (TTS) processing the template by the processor of the computer into audio; and, returning the audio from the memory of the computer to the call processing gateway for playback to the caller while the caller is on hold.

2. The method of claim 1, wherein the context of the call is a duration of time the caller is expected to be on hold.

3. The method of claim 1 or 2. wherein the selected record is a case stored in the CRM
application for the caller.

4. The method of claim 1 or 2, wherein the selected record is a status of a case stored in the CRM application for the caller.

5. The method of claim 1 or 2, wherein the template is TTS processed by a remote service.

6. A customer relationship management (CRM) data processing system configured for CRM audio on hold, the system comprising:
a host computing system comprising at least one computer with memory and at least one processor;
a database coupled to the host computing system;
a CRM application executing in the memory of the host computing system;
a call processing gateway processing telephone calls from callers over a public switched telephone network (PSTN); and, a CRM audio on hold module coupled to both the CRM application and the call processing module, the CRM audio on hold module comprising program code enabled to identify a caller associated with a telephone call received in the call processing gateway, to select a record in a CRM application pertinent to the caller, to insert the selected record into a variable field of a template selected according to a context of the call, to text-to-speech (TTS) process the template into audio and to return the audio to the call processing gateway for playback to the caller while the caller is on hold.

7. The system of claim 6, wherein the context of the call is a duration of time the caller is expected to be on hold.

8. The system of claim 6 or 7, wherein the selected record is a case stored in the CRM
application for the caller.

9. The system of claim 6 or 7, wherein the selected record is a status of a case stored in the CRM application for the caller.

10. The system of claim 6 or 7, wherein the template is TTS processed by a remote service.

11. A computer program product for customer relationship management (CRM) audio on hold, the computer program product comprising:
a computer readable storage memory device having computer readable program code embodied therewith, the computer readable program code comprising:

computer readable program code for identifying a caller associated with the telephone call received in a call processing gateway;
computer readable program code for selecting a record in a CRM application pertinent to the caller;
computer readable program code for inserting the selected record into a variable field of a template selected according to a context of the call and text-to-speech (TTS) processing the template into audio; and, computer readable program code for returning the audio to the call processing gateway for playback to the caller while the caller is on hold.

12. The computer program product of claim 11, wherein the context of the call is a duration of time the caller is expected to be on hold.

13. The computer program product of claim 11 or 12, wherein the selected record is a case stored in the CRM application for the caller.

14. The computer program product of claim 11 or 12, wherein the selected record is a status of a case stored in the CRM application for the caller.

15. The computer program product of claim 11 or 12, wherein the template is TTS
processed by a remote service.