Configuring an Appointment Chatbot (Task-oriented Robot)

This section uses a simple configuration example to describe how to configure a task-oriented robot.

• Configuration Scenario
  This section describes how to configure a task-oriented robot.
• Adding Business Interfaces
  Business interfaces are encapsulated from third-party interfaces, and are then associated and invoked by the Interface Invoking diagram element. The IVN supports RESTful interfaces.
• Adding Resource Templates
  Resources include static voice files, TTS voice files, and SMS messages. Before orchestrating flows, you need to add the involved resources, including voice and SMS templates, to the system.
• Adding an Intention
  An intention can be understood as a question of a customer. The customer can achieve a certain goal such as seat booking using one or a group of intentions. During IVR flow orchestration, if the semantic recognition service diagram element is selected, the intention template needs to be configured for the semantic recognition diagram element to recognize customer intentions.
• Adding Flows
  A flow represents an IVN task. You need to connect your intentions and voice replies in the entire flow to provide the self-service voice service for customers.
• Importing Flows
  
• Adding Gray Rules
  A gray rule indicates that a publishing rule can be specified when a flow is published so that a customer who meets the rule can experience the flow. A number segment can be specified for the current gray rule, which is used in the test phase.
• Publishing a Flow
  The newly added flow is in draft state. You need to publish the flow for the flow to take effect. To modify a published flow, you need to bring the flow offline, edit the flow, and publish the flow again.
• Configuring a Robot
  After the flow is published, associate your flow with the robot to generate the robot access code. Then, choose Configuration Center > Access Configuration > Called Party to bind the robot access code. Your customer service hotline consists of the access code and extension code.
• Testing a Robot
  You can test your robot to determine whether your configuration is correct.
• Viewing Flow Tracks
  A flow track refers to the flow nodes that a call passes through after the call accesses the flow on the OIAP and the information returned by each node. When an error occurs in the test robot, you can use the test number to view the value change on each node in the flow track and locate the cause of the error.
• Performing Dialog Tests