5.19:Tutorials-for-admins/Services/InboundVoiceServiceConfiguration

• 5.19 • 5.3 • 5.8

<translate>= How to Configure Inbound Voice Services= This section outlines the recommended general order of configuring an inbound voice service.

For inbound voice services with virtual queuing (callback option), see also Bright Pattern's Virtual Queue Tutorial.

The following steps suggest the order of actions that you should take when configuring an inbound voice service for your contact center.

Step 1: Create and configure an inbound voice service

Create an inbound voice service, and configure its general settings. See section Services and Campaigns - Properties Tab.

Step 2: Assign teams to the service

Assign agent teams to this service. Note that the service will be created with a default service skill that can be assigned automatically to all members of the associated agent teams. See section Services and Campaigns - Assignments Tab.

Step 3: Create additional skills required for this service

Additional skills are called auxiliary skills. Add any other required agent skills for this campaign.

Step 4: Assign the additional skills to agents of the assigned teams

Assign auxiliary skills to agents as required skill levels.

Step 5: Specify service level thresholds

Set the service level threshold for the service. See section Services and Campaigns - Service Level Tab.

Step 6: Create the scenario for the service

Create the interaction processing scenario for this service. Use text-to-speech to generate the voice messages and prompts, and once they are finalized, record them with a voice talent.

Step 7: Specify dial-out information

Specify the dial-out entries for outbound consultation calls.

Step 8: Set up periodic call recording exports

Set up periodic exports of call recordings. See section Services and Campaigns - Results Tab.

Step 9: Configure caller ID

Configure a caller ID for outbound SMS communications. See section Services and Campaigns - Numbers Tab.

Step 10: Associate scenarios

Associate a scenario with the access number. See section Scenario Entries.

</translate>

< Previous | Next >