Key Recognition

Appearance

Parameter Description

  • Node Name: name of a node.
  • Description: details of a node.
  • Rule Expression: expression to verify the type of customer input. For example, you can select Validate month input to verify whether the entered month is in the yyyyMM format.
    • Validate mobile number format (with # and *)
      1. * — MAIN branch
      2. # — CURRENT branch
      3. 11-digit mobile number ending with a number sign (#) and starting with 135 to 139, 150 to 152, 157 to 159, 147, 182 to 184, 187, 188, or 198 — ValueCheck branch
      4. 11-digit mobile number ending with a number sign (#) and starting with 1340 to 1348 — ValueCheck branch
    • Validate mobile number format (without # or *)
      1. 11-digit mobile number starting with 135 to 139, 150 to 152, 157 to 159, 147, 182 to 184, 187, 188, or 198 — ValueCheck branch
      2. 11-digit mobile number starting with 1340 to 1348 — ValueCheck branch
    • Validate password format (with # and *)
      1. * — MAIN branch
      2. # — CURRENT branch
      3. 6-digit number — ValueCheck branch
    • Validate password format (with *)
      1. * — MAIN branch
      2. 6-digit number — ValueCheck branch
    • Validate mobile number (with # and *)
      1. * — MAIN branch
      2. # — CURRENT branch
      3. 11-digit phone number — ValueCheck branch
    • Validate mobile number (with *)
      1. * — MAIN branch
      2. 11-digit phone number — ValueCheck branch
    • Validate month input
      1. * — MAIN branch
      2. # — CURRENT branch
      3. Valid month in yyyyMM format — ValueCheck branch
  • Keyboard Input Type: If this parameter is left blank, the month input verification is performed by default (Rule Expression must be set to Validate month input). The entered month must be in the yyyyMM format.
    • keyBoard_phone: input from a phone keyboard. Enter this value when the OpenEye or a mobile phone is used.
    • checkoldpassword: input from a password keyboard.
  • Variable: variable for saving customer input.
  • Context: used to filter intention templates to be matched to improve the matching speed. When Keyboard Input Type is set to checkoldpassword, this parameter is invalid, because semantic recognition is not performed on the keyboard input.

Using the Diagram Element

The Key Recognition diagram element mainly follows the Response diagram element (when Response Mode is set to a mode related to digit collection, such as Interruption by key presses or No interruption after digit collection) to save the pressing content to a variable for further logic processing.

Click the diagram element or drag it to the canvas, and set parameters based on the parameter description.

Typical Application Scenario

The following describes how to use the Key Recognition diagram element to enable customers to select a business to be handled by pressing a key.

  1. Sign in to the AICC and choose Configuration Center > Flow Configuration > Intelligent IVR.
  2. Configure an intelligent IVR flow.

    1. Choose Flow Management > Flow Orchestration and click Add to add a simple flow.
    2. Click + in the Flow Variable area. In the dialog box that is displayed, set the variable name and data type. The default value of the variable will be played to the customer.
      Figure 1 Flow variables to be added
      Figure 2 Flow orchestration example (Key Recognition diagram element)
      Figure 3 Flow orchestration example (Condition Judgment diagram element)
      • Use the response variable FLOW.key0 for the Response diagram element of the Key0 condition branch to reply to the customer that the call fee business is selected.
      • Use the response variable FLOW.key1 for the Response diagram element of the Key1 condition branch to reply to the customer that the data package business is selected.
    3. Save and release the flow.

  3. Choose Chatbot Management and bind the flow to a chatbot.
  4. Choose Chatbot Management. In the last column corresponding to the chatbot, click Test Call. In the test dialog box that is displayed, click Start Call to test the chatbot. If the chatbot answers different businesses based on different keys pressed by the customer, the configuration is successful.

    Figure 4 Testing the chatbot