Intelligent outbound robot best practices

1.1 Enterprise real-name authentication

1. After you register your account, follow the instructions in the Enterprise Real-name Authentication guide to complete the enterprise real-name authentication. You will need the following documents:

   • Business License Duplicate

   • Legal Representative ID Certificate

   • Corporate Bank Account Verification

3.1 RAM user authorization

1. Follow the instructions in Create and authorize a RAM account to create a RAM user for operations:

   • Create a RAM user in the RAM console.

   • Attach the OutboundBot product access policy.

   • Apply the principle of least privilege. We recommend using separate permissions for development, testing, and production environments.

     Note

     We recommend using a RAM role to isolate permissions. The main account should retain full administrative privileges.

4.1 Business space creation

Create a Conversation Engine 3.0 space in the Business Management section:

• Notes:

  • The legacy chatbot option only supports a non-commercial version without large model capabilities and has been deprecated. Always select Conversation Engine 3.0 to build your space.

  • We recommend allocating instance concurrency based on the call rate limit of your numbers. For example, if a number is bound to a single business space and has a rate limit of 10, allocate an instance concurrency of 10 to that space. If the same number is bound to two business spaces, you must divide the concurrency. For example, allocate an instance concurrency of 5 to each space.

5.1 Scenario types and configuration

• Note:

  • When building scenarios that use large models, if your flow requires variables, number collection, an API plugin, or the option to transfer to a human agent, you must first define them in the Variable Configuration section.

5.2 Live demo

Experience a live demo at Lingque Scenario Examples.

6.1 Comprehensive testing

Perform voice debugging and testing:

1. Use the voice debugging tool to test TTS and ASR performance.

2. Use the demo link to validate the scenario.

7.1 Number application and binding

To apply for numbers, see the Line Application Process documentation.

1. When you apply for a phone number:

   • Allow 1 to 2 weeks for review and number provisioning.

   • You must provide a clear description of your use case.

2. Bind numbers to a business space:

   • A single number can be bound to multiple business spaces.

   • We recommend creating a number pool and grouping numbers by business type.

7.2 Concurrency configuration

Allocate concurrency in the Business Management section based on your business needs:

• The instance concurrency for a single business space must not exceed the combined call rate limit of all its bound caller ID numbers.

8.1 Task group creation

1. Create an outbound task group

   • Bind a published scenario template and a caller ID.

   • Set a call strategy for the task. The calling schedule must comply with the permitted calling hours of your phone line.

   • Upload a list of called numbers.