Microsoft Sales Insight has been introduced as a tool for both Dynamics and non dynamics Users for there better sales projection and different sales persona betterment insights.
Simple steps to Configure sales Insight.
sales.ai.dynamics.com
It provides inbuilt connector for Redbox to integrate call data.As an alternative to redbox , here is the metadata/format expected to be uploaded to azure:
In general two steps are prerequisite to the entire setup of sales insight
A)Create a Call Repository
B)Upload Call data
A)Create a Call Repository
Simple steps to Configure sales Insight.
sales.ai.dynamics.com
It provides inbuilt connector for Redbox to integrate call data.As an alternative to redbox , here is the metadata/format expected to be uploaded to azure:
In general two steps are prerequisite to the entire setup of sales insight
A)Create a Call Repository
B)Upload Call data
A)Create a Call Repository
- Sign in to the Azure dashboard.
- On the navigation pane, select All resources, and open the desired storage account.
- From Blob service, select Blobs then + Container.
- Specify the container information, such as name and public access level.
- Select OK.The container is created. To learn more, see Create a container
- From Settings, go to Access keys and note the Connection string of the storage account. This connection string is used to connect Call intelligence to your Azure storage account.
Now you are ready to upload call recordings to the blob container and configure the call data for conversation intelligence.
B)Upload Call data
You can upload the recordings in audio formats, such as MP3 and WAV, in the created call recording repository (blob container) in Azure. Along with the audio format file, you must upload the corresponding metadata file in JSON format.
B)Upload Call data
You can upload the recordings in audio formats, such as MP3 and WAV, in the created call recording repository (blob container) in Azure. Along with the audio format file, you must upload the corresponding metadata file in JSON format.
Review the following requirements for audio and JSON files before you upload:
- The file names for the audio and its corresponding JSON files must be the same. For example, if you name the audio file call-recording-10-dec-2018.wav, the corresponding JSON file should be named call-recording-10-dec-2018.json.
- The file name cannot contain reserved characters, such as !*'();:@&=+$,/?%#[]".
- The length of the file name should be fewer than 260 characters.
- The call recording should be a stereo type recording only.
No comments:
Post a Comment