Edit

Share via

Migrate workstreams to support voice-enabled Copilots

  • Article

Voice-enabled Copilots provide enhanced interactive voice response (IVR) capabilities such as speech and Dual-Tone Multi-Frequency (DTMF) input, context variables, call transfer, speech, and DTMF customizations. To use these capabilities in the voice channel, you must create a new bot in Copilot Studio and add it to a workstream that the Copilot is compatible with.

If you have an existing voice channel deployment, make sure you migrate your existing workstreams for the voice enabled Copilots to work. Any new workstreams that you create are automatically compatible with the Copilots.

Note

  • For new voice configurations, the enhanced voice experience is available out of the box.
  • Data Loss Prevention isn't supported in the enhanced voice experience.

Prerequisites

  • You must have an Azure Communication Services resource connected to your Dynamics 365 Customer Service instance.
  • Your active Azure subscription is in the same tenant as your Dynamics 365 account.
  • Have at least contributor-level permissions to the Azure subscription. To check your role, open your subscription and view the My role column of your subscription on the Azure portal. You'll be able to deploy your Azure Communication Services resource only if you have contributor-level permissions.

How to migrate your voice workstreams

  1. Create and set up an event grid subscription for incoming calls. See Enable call inoming calls, call recording and SMS services.
  2. Update the event subscription in Azure for recording webhook. Copy the value in the Recording Web Hook Endpoint field in the Customer Service admin center > Phone Numbers > Advanced > Manage Azure Communication Services (Preview) and paste it in the Endpoint field.
  3. Create a Copilot bot. When you migrate to the enhanced voice experience, your phone numbers are updated. The existing classic voice bots aren't supported for the updated workstreams. We recommend that you update and rename your new Copilot bots similar to your previous bots. For example, if your classic bot is named as "Returns bot", rename your voice enabled Copilot as "Returns Bot-new".
  4. Run the voice update.
  5. Test the voice update.

Run the voice update

To update to the new voice experience, perform the following steps:

  1. Go to Customer Service admin center and select Channels in Customer support.
  2. Select Manage for Voice update. On the Voice update page, all the workstreams with the associated phone numbers, inbound and outbound profiles, and the corresponding migration update and test status are displayed.
  3. Select the required workstream and then select Run update. You can select multiple workstreams to update at once. The application displays the Replace or remove bots page with the classic bots connected to channels either as the post call survey bot, workstream as the deflection bot, or queues as a bot agent.

    Note

    • We recommend that you migrate all the workstreams that share a common queue and contain a classic bot configured.
    • On the Replace or remove bots page, only those classic bots are displayed that are attached to workstreams in which route-to-queues rules are configured.
  4. Select the voice-enabled Copilot that you created to replace the classic bot in the Replacement drop down. The application doesn't display your existing classic bots in this list.
  5. Select Run update. The application takes at least 15 minutes to sync the changes. The application also refreshes the phone numbers associated with the workstreams in the background to be compatible with the new voice experience. The application displays the status of the update on the Results page.

Note

Azure direct offer numbers synchronize more quickly than direct routing numbers, with calls expected to function within 15 minutes for the former, while calls to the latter can take up to 30 minutes to start functioning after the update.

Test and revert the voice update

The test status field can be used to keep track of testing. If any call to any phone number attached to a profile or a workstream fails after 30 minutes, the application sets the Test status to Failed. You can retry the update or select the Revert option to go back to the original state. There will be at least a 15 to 30 minutes downtime for the changes to sync after the revert. If the revert fails, select Retry revert to try the revert again. If roll back fails, that application displays a critical message to contact Microsoft Support .

See also

Bring your own carrier
Overview of the voice channel
Connect to Azure Communication Services
Connect using a new Azure resource
Set up outbound calling
Set up inbound calling
Integrate third-party IVR systems with voice channel