Call center IVR system based on FreeSWITCH
By designing business systems and middleware on FreeSWITCH and connecting IVR systems, the problem of insufficient flexibility and scalability of traditional IVR systems is solved, and a highly configurable and easy-to-manage IVR system is realized, adapting to different business scenarios and improving the system Functionality and service quality.
Patent Information
- Application Number
- CN202411564467.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-05
- Publication Date
- 2024-12-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The traditional IVR system is based on proprietary hardware and software, which limits its flexibility and scalability. The direct use of FreeSWITCH is not suitable for all business scenarios. It lacks intuitive business interfaces and support for upper-level applications, making it difficult to achieve highly configurable and easy A call center management system managed and maintained.
A call center IVR system based on FreeSWITCH was designed, including business system, middleware and FreeSWITCH module. The middleware connects the business system and FreeSWITCH module, provides call control and media processing interfaces, supports custom IVR business logic processing processes, and integrates the Third-party storage services and text-to-voice services realize node configuration and action execution.
It realizes a highly configurable, easy to manage and maintain IVR solution, adapts to the needs of different business scenarios, enhances system functionality and service quality, and provides agents with efficient and convenient outbound call tools.
Smart Images

Figure CN119071392A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of call center management systems, and more specifically, to a call center IVR system based on FreeSWITCH. Background Art
[0002] With the rapid development of information technology, call centers, as an important bridge for communication between enterprises and customers, are also constantly evolving and developing. Interactive Voice Response (IVR) systems have become an important tool for enterprises and organizations to interact with customers. Traditional IVR systems are usually built on proprietary hardware and software platforms, which limits their flexibility and scalability. In recent years, the emergence of open source technologies such as FreeSWITCH has made it possible to develop highly complex and customized IVR solutions.
[0003] Therefore, in order to meet the growing demand of enterprises and organizations for efficient call center management systems. FreeSWITCH, as a powerful and flexible open source media switching platform, provides enterprises with a low-cost and high-flexibility option. However, how to achieve high configurability, easy management and maintenance based on FreeSWITCH, and adapt to different business scenarios, has become an urgent problem to be solved.
[0004] Moreover, directly using FreeSWITCH is not suitable for all business scenarios because it lacks intuitive business interfaces and support for upper-layer applications. Therefore, enterprises also need to design a system that can seamlessly connect the underlying capabilities of Freeswitch with the business layer, thereby simplifying the interaction between the business system and Freeswitch. Summary of the invention
[0005] The present invention overcomes the deficiencies of the prior art and provides a FreeSWITCH-based call center IVR system that is highly configurable and easy to manage and maintain.
[0006] The technical solution of the present invention is as follows: The call center IVR system based on FreeSWITCH includes business system, middleware and FreeSWITCH module; the middleware connects the business system and FreeSWITCH module; The business system includes at least two IVR business logic processing flows, each of which includes node configuration, node parsing and execution; the system parses each IVR node in the node configuration in the IVR business logic processing flow according to the preset IVR business logic processing flow and the node configuration therein, and executes the corresponding action; The middleware provides call control and media processing interfaces for the business system. When the middleware is connected to FreeSWITCH, it receives FreeSWITCH events and triggers corresponding business logic processing. The FreeSWITCH module provides routing and interconnection communication protocols for text, audio, video or any other form of media, converting user call information into FreeSWITCH trigger events.
[0007] Furthermore, the middleware also includes a third-party storage service module and a text-to-speech service module.
[0008] Furthermore, the IVR business logic processing flow supports customization.
[0009] Furthermore, the IVR business logic processing flow includes an automatic voice response flow and a key collection flow.
[0010] Further, the node configuration includes one or more of a playback node, a collection button node, an intelligent playback node, a text message node, a transfer seat node, an on-hook node, a judgment node, a message node, a waiting node, a loop intelligent playback node, a non-blocking transfer seat node, a call node, and a dynamic playback node; Playback node: used to play pre-recorded messages or prompts; Collect key node: allows users to input information by keystrokes; Intelligent playback node: plays different messages based on user input or preset conditions; SMS node: used to trigger SMS sending; Transfer to agent node: transfer the call to the designated manual customer service; Hang up node: end the call; Judgment node: determine the next node based on certain conditions; Message node: allows users to leave messages; Waiting node: set a specific waiting time; Loop intelligent playback node: plays information repeatedly according to specific conditions until the exit condition is met; Non-blocking transfer node: transfers calls to customer service without blocking; Call node: establishes a direct call between two or more participants; Dynamic playback node: dynamically generates and plays voice content.
[0011] Furthermore, the common attributes of the node in the node configuration include the node identification ID, the head node HEAD_ID of the IVR business logic processing flow, the node type NODE_TYPE, the action type ACTION_TYPE, the action execution type ACTION_AFTER_TYPE, the next condition NEXT_CONDITION, the next node identification NEXT_NODE and whether ENABLED is enabled; The node ID is used to uniquely identify the node; The head node HEAD_ID of the IVR business logic processing flow indicates which IVR flow the current node belongs to; Node type NODE_TYPE identifies the type and function of the current node; ACTION_TYPE specifies the action type of the current node. This value will be different in different types of nodes. ACTION_AFTER_TYPE indicates that after the current ACTION is executed, there are still actions that need to be executed, but they still belong to the matters of this node; The next condition NEXT_CONDITION is the condition of the node routing. If it matches, the corresponding next node identifier NEXT_NODE is executed; Whether ENABLED indicates whether the current node is effective.
[0012] Furthermore, the middleware provides the following call control and media processing interfaces for the business system: Interfaces for agent outbound call DoubleCall, channel audio playback playbackAudio, call hold holdCall, call hold unholdCall, call release hangupCall, call transfer transferCall, CDR generation, start and end recording, start and stop ASR; The connection between the middleware and FreeSWITCH includes maintaining the connection with FreeSWITCH, notifying FreeSWITCH to execute various instructions, receiving FreeSWITCH events and pushing ASR recognition results; The middleware also includes a connection with a third-party storage service module for storing recording and message files; the middleware includes a text-to-speech service module, which provides a broadcast function for both parties of the call.
[0013] Compared with the prior art, the present invention has the following advantages: The system of the present invention provides an IVR solution that is highly configurable, easy to manage and maintain to meet the needs of different business scenarios. The middleware of the present invention not only provides a rich call control and media processing interface for the business system, but also maintains the connection with FreeSWITCH, and is able to receive FreeSWITCH events to trigger corresponding business logic processing. In addition, the middleware also integrates third-party storage services and TTS (Text-To-Speech) services, further enhancing the functionality and practicality of the system. This solution enhances the overall function and service quality of the system through the middleware, and provides agents with a more efficient and convenient outbound calling tool. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] Figure 1 It is a schematic diagram of the overall framework of the present invention; Figure 2 is an exemplary flow chart of the present invention; Figure 3 An IVR flow chart when the present invention finds conditions that meet the requirements; Figure 4 It is the interaction sequence diagram of the present invention. DETAILED DESCRIPTION
[0015] The embodiments of the present invention are described in detail below, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention and cannot be used as a limitation of the present invention.
[0016] It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as generally understood by those skilled in the art in the field to which the present invention belongs. It should also be understood that terms such as those defined in common dictionaries should be understood to have meanings consistent with the meanings in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless defined as herein.
[0017] The reference numbers of the steps mentioned in each embodiment are only for the convenience of description and have no substantial sequence connection. Different steps in each specific embodiment can be combined in different sequences to achieve the purpose of the invention. The parts not described in detail in this scheme can be implemented by conventional technical means.
[0018] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments.
[0019] like Figure 1As shown, the call center IVR system based on FreeSWITCH includes a business system, middleware and FreeSWITCH module; the middleware connects the business system and the FreeSWITCH module.
[0020] The business system includes at least two IVR business logic processing flows, each of which includes node configuration, node parsing and execution. The system parses each IVR node in the node configuration and executes the corresponding action based on the preset IVR business logic processing flow and the node configuration therein. That is, each IVR business logic processing flow starts with a root node, on which users can add multiple types of IVR nodes, such as playback nodes, collection button nodes, intelligent playback nodes, etc., to build complex interactive logic.
[0021] The middleware provides call control and media processing interfaces for the business system; when the middleware is connected to FreeSWITCH, it receives FreeSWITCH events and triggers corresponding business logic processing.
[0022] The FreeSWITCH module provides routing and interconnection communication protocols for audio, video or any other form of media, converting the user's call information into trigger events for FreeSWITCH.
[0023] As a preferred embodiment, the IVR business logic processing flow supports customization. The IVR business logic processing flow includes automatic voice response flow, key collection flow, etc. The middleware also includes a third-party storage service module and a text-to-speech service module.
[0024] Specific node configurations include playback nodes, collection button nodes, intelligent playback nodes, SMS nodes, transfer nodes, hang-up nodes, judgment nodes, message nodes, waiting nodes, loop intelligent playback nodes, non-blocking transfer nodes, call nodes, and dynamic playback nodes, etc. Each IVR business logic processing flow includes one or several of these nodes.
[0025] The playback node is used to play pre-recorded messages or prompts; Collect key node: allows users to input information by keystrokes; Intelligent playback node: plays different messages based on user input or preset conditions; SMS node: used to trigger SMS sending; Transfer to agent node: transfer the call to the designated manual customer service; Hang up node: end the call; Judgment node: determine the next node based on certain conditions; Message node: allows users to leave messages; Waiting node: set a specific waiting time; Loop intelligent playback node: plays information repeatedly according to specific conditions until the exit condition is met; Non-blocking transfer node: transfers calls to customer service without blocking; Call node: establishes a direct call between two or more participants; Dynamic playback node: dynamically generates and plays voice content.
[0026] Specifically, the nodes in the node configuration all have common attributes, including the node identification ID, the head node HEAD_ID of the IVR business logic processing flow to which it belongs, the node type NODE_TYPE, the action type ACTION_TYPE, the action execution type ACTION_AFTER_TYPE, the next condition NEXT_CONDITION, the next node identification NEXT_NODE, whether ENABLED is enabled, etc.
[0027] The node ID is used to uniquely identify the node; The head node HEAD_ID of the IVR business logic processing flow indicates which IVR flow the current node belongs to; Node type NODE_TYPE identifies the type and function of the current node; ACTION_TYPE specifies the action type of the current node. This value will be different in different types of nodes. ACTION_AFTER_TYPE indicates that after the current ACTION is executed, there are still actions that need to be executed, but they still belong to the matters of this node; The next condition NEXT_CONDITION is the condition of the node routing. If it matches, the corresponding next node identifier NEXT_NODE is executed; Whether ENABLED indicates whether the current node is effective.
[0028] As a preference, the specific playback node is used to play pre-recorded messages or prompts, and the ACTION_TYPE attribute may be tts, audio_file_local_path, or audio_file_remote_link.
[0029] If ACTION_TYPE is tts, then the node only needs to input text content. When the call is routed to the node, the system will play the corresponding voice content according to the text content. If ACTION_TYPE is audio_file_local_path, the node will read the local pre-recorded audio file for playback; If ACTION_TYPE is audio_file_remote_link, the node will first synchronize the remote file to the local according to the link, and then start playing.
[0030] If ACTION_AFTER_TYPE indicates that cases need to be collected after the announcement is completed, NEXT_CONDITION will determine which node to execute next based on the collected keystrokes.
[0031] Collection button node: allows users to input information by pressing buttons. Since collection button is a very common function, although it can also be implemented in the playback node, it is still a separate node type that can be deeply customized. The ACTION_TYPE of this node can be divided into post-playing button and playback button that can be interrupted. The corresponding ACTION_ATTR is a specific attribute setting, such as playback timeout configuration, playback cycle number, button rule, etc. The output of this node is a button, which can be routed to the judgment node, and the traffic can be routed to different nodes according to different buttons.
[0032] Intelligent playback node: plays different voices according to user input or preset conditions. Plays a piece of text or a file. When entering the node for the first time, it plays once and cannot be interrupted. It will not be played again when entering the node again. The file can be filled with a file name or an OSS link. It can receive the key input by the caller to trigger interruption or function keys. It supports key interruption. Text supports setting parameters. It supports voice input and converts the voice into text after receiving the voice. It reports to the business layer of the business system through the ASR interface. The business layer calls the asrDo interface to control the knowledge playback. It supports manual transfer, text messaging, message, knowledge re-listening, knowledge playback reminder, waiting input timeout reminder, interruption reminder, knowledge overtime reminder, etc. When the number of consecutive abnormal inputs exceeds the maximum number of consecutive unmatches configured globally by the IVR, the next node corresponding to the unmatched unmatchs is executed. When the number of consecutive waiting input timeouts exceeds the maximum number of consecutive timeouts configured globally by the IVR, the next node corresponding to the timeout timeouts is executed.
[0033] SMS node: used to trigger SMS sending. When a call is routed to this node, a SendSMS message is pushed to the business layer of the business system.
[0034] Transfer agent node: transfer the call to the designated manual customer service. Push InCall to the business layer of the business system to request an idle agent. The business layer returns BindCall and starts calling the agent. If the business layer returns BindCall and times out or the call to the agent fails, the number of transfers to the agent will increase by 1. After the maximum number of transfers is exceeded, execute the node corresponding to F (failure). The waiting time for the business layer to respond is the transfer waiting time. Supports transfers to skill groups with agent assistants, skill groups without agent assistants, third-party call centers, and back to the cloud switchboard. Supports playing work numbers. When entering this node, InCall will be pushed to the business layer, and the voice specified by the transfer waiting tone will be played. If not specified, the system default music will be played.
[0035] Hang up node: used to end the call. This node will call the hang up command to FreeSWITCH to hang up all terminal channels involved in the current call.
[0036] Judgment node: Determine the next node based on certain conditions. Supports judgment of day of the week, time, date, weekday, whether the incoming call number is a mobile phone number, number of concurrent intelligent voice calls, whether the call is in a queue, etc.
[0037] Message node: allows users to leave messages. When a call is routed to this node, the message prompt tone will be played according to the configuration and the message voice will be recorded. The CDR (Calling Detail Record) passing through this node will contain the field voiceMsg, which indicates the message file path.
[0038] Waiting node: Set a specific waiting time. During the call waiting process, the system will play the specified music. After the waiting timeout period, the system will jump to the next node specified by D. The node action specified by D is the next node executed after normal execution (Done).
[0039] Circular intelligent playback node: plays information repeatedly according to specific conditions until the exit condition is met. Play a piece of text or a file. It will only be played once when entering the node for the first time and cannot be interrupted. It will not be played again when entering the node again. The file can be filled with a file name or a remote file link. It can receive the key input by the caller to trigger interruption or function keys. It supports key interruption. Text supports setting parameters. It supports voice input. After receiving the voice, it converts the voice into text and reports it to the business layer through the ASR interface. The business layer can call asrDo to control the knowledge playback. It supports manual transfer, text messaging, leaving messages, knowledge re-listening, knowledge playback end reminder, waiting input timeout reminder, interruption reminder, knowledge overtime reminder, etc. When the number of consecutive abnormal inputs exceeds the maximum number of consecutive unmatches configured globally by the IVR, the next node corresponding to the unmatched unmatchs is executed. When the number of consecutive waiting input timeouts exceeds the maximum number of consecutive timeouts configured globally by the IVR, the next node corresponding to the timeout timeouts is executed.
[0040] Non-blocking agent transfer node: non-blocking transfer of calls to customer service. When a call enters this node, it pushes InCall to the business layer to request an idle agent. InCall is sent only once. The business layer detects an idle agent and pushes BindCall. The business layer determines whether to continue pushing BindCall based on the agent status. After this node pushes CancelCall to the business layer, the business layer stops pushing BindCall. The business layer returns BindCall to start calling the agent. It supports transfers to skill groups with agent assistants, transfers to skill groups without agent assistants, transfers to third-party call centers, and transfers back to the cloud switchboard.
[0041] Call node: establishes a direct call between two or more participants. This node configures some actions to start the call, such as playing the work number and bridging the two parties in the call (default behavior).
[0042] Dynamic playback node: Dynamically generate and play voice content. Play the text or file specified by the business end asrDo. The file can be filled with the remote voice file link. The business end can specify the key range. The business layer specifies the key range by setting the operType=1 of the asrDo message and the dtmfs field. If the key input by the caller meets the business end specification, it will be returned through the dtmf field of the dtmf message. If it does not meet the requirements, it will return the dtmf null value. It supports key interruption, abnormal input judgment, and input waiting timeout reminder. In abnormal situations, it will be played repeatedly. After the number of consecutive abnormal inputs exceeds the maximum number of consecutive mismatches configured globally by the IVR, the dtmfs null value is returned to the business end, and the next node specified by the specific U is executed. After the number of consecutive waiting input timeouts exceeds the maximum number of consecutive timeouts configured globally by the IVR, the dtmfs null value is returned to the Java end, and the next node specified by the specific T is executed. Among them, the node action specified by U is the next node executed when it is unmatched (Unmatched), and the node action specified by T is the next node executed after timeout (Timeout) or exceeding a certain limit.
[0043] like Figure 2As shown in the figure, take the general service type as an example, and set the service type to be general enough to use each type of IVR node. Specifically, once the program is started by a customer call, all the configurations about IVR in the database DB are loaded into the memory. After the call passes through the voice gateway and enters FreeSWITCH, the IVR service system will obtain the relevant data of the new call through the CHANNEL_CREATE event of the middleware, including key information such as the caller, the called party, and call-id. At this time, FreeSWITCH will dock the call, and the call control will be handed over to the IVR service system IVR Server. The IVR service system IVRServer determines which IVR process the current call should be routed to based on the called party and the current time. Assuming that the current time is 2024-01-01 09:00:00, it will be considered that it is a holiday. The called number and this time information will be used to search the IVR configuration to find the IVR process suitable for the current time period and service.
[0044] Assume that an IVR process that meets the requirements is found. Figure 3 As shown: 1) Enter the root node and start playing the welcome voice. For example: Welcome to call X company.
[0045] 2) Access the judgment node and determine whether the current time is a holiday or working time based on the configuration.
[0046] 3) If it is a holiday or not during working hours, the system will enter the message leaving node. After leaving the message, the system will enter the hang-up process.
[0047] 4) If it is not a holiday and it is during working hours, then enter the key collection node; this node plays a prompt tone, and then starts pressing the phone key. For example: press 1 for robot intelligent Q&A, press 3 for manual Q&A, and say "transfer to manual" or press 0 for manual Q&A. During the Q&A process, you can say "transfer to manual" to exit the Q&A and transfer directly to manual Q&A.
[0048] 5) Enter the key judgment. If it is transferred to manual, then enter the processing logic of the transfer node, send an InCall message to the business layer of the business system, and the business layer sends a BindCall message according to business needs to indicate the target agent information of the transfer. At the same time, the IVR node enters the waiting node, and the caller hears the corresponding waiting music according to the configuration.
[0049] 6) If it is an intelligent question-and-answer node, it will enter the loop intelligent voice node, and the system will start to collect the customer's voice questions and report the results to the business layer through the ASR interface. The business layer controls the answer to the question to be played according to the asrDo interface.
[0050] 7) After the agent answers the call, the caller enters the call node. According to the configuration, the caller will hear: Agent with employee number xxx is at your service. How can I help you? Then, the system bridges the two parties in the call and both parties enter the call.
[0051] 8) After the call is over, the agent hangs up and the caller enters the announcement node. At this time, according to the configuration, the satisfaction survey logic is entered. The caller hears the announcement and presses the button according to the announcement prompt. For example: Please rate the service just now. If you are very satisfied, press 1; if you are satisfied, press 2; if you are dissatisfied, press 3; if you are very dissatisfied, press 4.
[0052] 9) After the playback node ends, it enters the hang-up node. After the hang-up node, a CDR will be generated for the business layer.
[0053] 10) After the hang-up is completed, the SMS node is entered, which pushes SendSMS to the business layer. The business layer will send a text message to the calling customer according to business needs. At this point, the IVR process ends.
[0054] As a preferred embodiment, the specific middleware provides call control and media processing interfaces for the service system, including the following: Interfaces for agent outbound call DoubleCall, channel audio playback playbackAudio, call hold holdCall, call hold unholdCall, call release hangupCall, call transfer transferCall, CDR generation, start and end recording, start and stop ASR; The connection between the middleware and FreeSWITCH includes maintaining the connection with FreeSWITCH, notifying FreeSWITCH to execute various instructions, receiving FreeSWITCH events and pushing ASR recognition results; The middleware also includes a connection with a third-party storage service module for storing recording and message files; the middleware includes a text-to-speech service module, which provides a broadcast function for both parties of the call.
[0055] The details are as follows: 1. The front-end initiates an outbound call request: When the agent needs to make an outbound call to an external customer, the front-end interface will initiate an outbound call request to the business system.
[0056] 2. The business system calls the DoubleCall interface: After receiving the front-end request, the business system calls the provided DoubleCall interface and passes the necessary parameters, such as the calling number (usually the agent number), the called number (that is, the customer number that needs to be called out), and other necessary call line configuration information.
[0057] 3. Parameter verification and session creation: After receiving the call of the DoubleCall interface, the middleware fugle_cc will first verify the incoming parameters to ensure that the information is complete and the format is correct. After the verification passes, the middleware fugle_cc creates a new session to track all related events of this call.
[0058] 4. Assemble and send FreeSWITCH's command to call the agent's sip terminal: The cc module of the middleware fugle_cc begins to assemble the call command required by FreeSWITCH. For example, use the command bgapi originate user / agent number & park() to call the agent's sip soft terminal. Then, the fsCmd module of the middleware fugle_cc sends the above command to FreeSWITCH.
[0059] 5. FreeSWITCH initiates a call: After receiving the call command, FreeSWITCH initiates a call to the designated agent sip soft terminal, and the agent soft terminal starts ringing immediately.
[0060] 6. Event monitoring and response: The fsEvent module of the middleware fugle_cc monitors events sent by FreeSWITCH, including but not limited to channel creation CHANNEL_CREATE, channel processing CHANNEL_PROGRESS, early media CHANNEL_PROGRESS_MEDIA, channel response CHANNEL_ANSWER, channel hangup CHANNEL_HANGUP, etc. When the agent answers the call, the fsEvent module will receive the CHANNEL_ANSWER event, and the conditions for the outbound call are met.
[0061] 7. Calling external clients: After receiving the answering event, the fsEvent module notifies the cc module to continue assembling FreeSWITCH's command to call external clients, such as through the instruction bgapi originate sofia / gateway / xxxxxx&park(), where xxxxxx is the called number to be called. The fsCmd module sends commands to FreeSWITCH again.
[0062] 8. Handle call status changes: The fsEvent module continues to monitor the outbound call status events. If the customer answers the call, the fsEvent module will receive the CHANNEL_ANSWER event and enter the pre-call pre-processing process. If the customer refuses to answer the call or does not answer the call, the fsEvent module will receive the CHANNEL_HANGUP event, and the cc module will enter the post-hangup business processing process.
[0063] 9. Call process management: During a call, the business system can call the startRecord interface to start recording and the startASR interface to start voice transcription as needed. The cc module enters the logic of bridging the call between the two parties. After success, the agent and the customer enter the call. At this time, the playbackAudio interface can be called to provide voice prompts to the customer, or the tts interface can be called to automatically generate text-related voice.
[0064] 10. Call hold and transfer: During a call, the agent can choose whether to put the call on hold. In this case, the holdCall interface needs to be called. To cancel the hold, the unholdCall interface needs to be called. If the call needs to be transferred to another agent, the transferCall interface needs to be called.
[0065] 11. Call end processing: After the call ends, the agent can call the call release hangupCall interface to complete the hangup operation. That is, after the fsEvent module receives the CHANNEL_HANGUP event, it notifies the cc module to enter the business logic after hanging up. If a customer satisfaction survey is required, the channel playbackAudio interface can be called to play the satisfaction key to collect the voice, and enter the hangup process after receiving the DTMF event. The DTMF event is a standard event of FreeSWITCH, which is triggered and reported by FreeSWITCH after receiving the channel key.
[0066] 12. Generate and store CDR data: After the entire call is completed, CDR data is generated and reported to the business layer. In addition, it will trigger the connection with the external storage system to store the recording file generated by this call.
[0067] In summary, the middleware of this solution not only simplifies the interaction between the business system and FreeSWITCH, but also enhances the overall functionality and service quality of the system, providing agents with a more efficient and convenient outbound calling tool.
[0068] The above is only a preferred embodiment of the present invention. It should be pointed out that ordinary technicians in this technical field can make several improvements and modifications without departing from the concept of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.
Claims
1. Call center IVR system based on FreeSWITCH, characterized by: Includes business system, middleware and FreeSWITCH module; the middleware connects the business system and FreeSWITCH module; The business system includes at least two IVR business logic processing flows, each of which includes node configuration, node parsing and execution; the system parses each IVR node in the node configuration in the IVR business logic processing flow according to the preset IVR business logic processing flow and the node configuration therein, and executes the corresponding action; The middleware provides call control and media processing interfaces for the business system. When the middleware is connected to FreeSWITCH, it receives FreeSWITCH events and triggers corresponding business logic processing. The FreeSWITCH module provides routing and interconnection communication protocols for text, audio, video or any other form of media, converting user call information into FreeSWITCH trigger events.
2. The call center IVR system based on FreeSWITCH according to claim 1, characterized in that: The middleware also includes a third-party storage service module and a text-to-speech service module.
3. The call center IVR system based on FreeSWITCH according to claim 1, characterized in that: IVR business logic processing flow supports customization.
4. The call center IVR system based on FreeSWITCH according to claim 1, characterized in that: The IVR business logic processing flow includes automatic voice response process and key collection process.
5. The call center IVR system based on FreeSWITCH according to claim 1, characterized in that: The node configuration includes one or more of the playback node, collection button node, intelligent playback node, SMS node, transfer seat node, hang-up node, judgment node, message node, waiting node, loop intelligent playback node, non-blocking transfer seat node, call node and dynamic playback node; Playback node: used to play pre-recorded messages or prompts; Collect key node: allows users to input information by keystrokes; Intelligent playback node: plays different messages based on user input or preset conditions; SMS node: used to trigger SMS sending; Transfer to agent node: transfer the call to the designated manual customer service; Hang up node: end the call; Judgment node: determine the next node based on certain conditions; Message node: allows users to leave messages; Waiting node: set a specific waiting time; Loop intelligent playback node: plays information repeatedly according to specific conditions until the exit condition is met; Non-blocking transfer node: transfers calls to customer service without blocking; Call node: establishes a direct call between two or more participants; Dynamic playback node: dynamically generates and plays voice content.
6. The call center IVR system based on FreeSWITCH according to claim 5, characterized in that: The common attributes of nodes in the node configuration include node ID, head node of the IVR business logic processing flow, node type, action type, action execution type, next step condition, next step node ID and whether to enable; Node is used to uniquely identify the node; The head node of the IVR business logic processing flow indicates which IVR flow the current node belongs to; The node type identifies the type and function of the current node; Action type specifies the action type of the current node. This value will be different in different types of nodes. The post-action type indicates that after the current ACTION is executed, there are still actions that need to be executed, but they still belong to the matters of this node; The next step condition is the condition of the node routing. If it matches, the corresponding next step node identification is executed; Whether enabled represents whether the current node is effective.
7. The call center IVR system based on FreeSWITCH according to claim 2, characterized in that: The middleware provides call control and media processing interfaces for the business system, including the following: Interfaces for agent outbound calls, channel playback, call hold, call hold cancellation, call release, call transfer, CDR generation, start and end recording, and start and stop ASR; The connection between the middleware and FreeSWITCH includes maintaining the connection with FreeSWITCH, notifying FreeSWITCH to execute various instructions, receiving FreeSWITCH events and pushing ASR recognition results; The middleware also includes a connection with a third-party storage service module for storing recording and message files; the middleware includes a text-to-speech service module, which provides a broadcast function for both parties of the call.
Citation Information
Patent Citations
Intelligent outbound voice robot system and outbound method
CN111131638A
IVR (Interactive Voice Response) process control method, system and equipment and storage medium
CN113329131A
Telephone traffic control method and device, and soft switching system
CN118200445A
Cited By
Middleware module for call center system
CN119071393A
