On this page |
|
Requirements
Let’s see how to configure an Amazon AWS Account according to the following requirements
Panel | ||
---|---|---|
| ||
You need to get an Amazon AWS Account by creating an IAM user with some specific permissions to make it work.
Quality Analysis SECTION | |
⚙️ Configuration
From XCALLY Settings, configure the Cloud Provider. Click on the
button:
Add the Amazon AWS Account:
To retrieve Access Key ID and Secret Access Key, you can open your user Account on Amazon AWS on section IAM > Users > username
And click on Security Credentials
On Access keys you can view the created keys or generate a new one.
If you need to create a new key, you can click on Create Access Key
The system asks you to choose an “access key best practices & alternatives”: you can select Third-party service and then you can Retrieve your access key
You need to copy the secret access key before closing the window because when you click on Done, it will no longer be visible.
To use the Post Call Analytics, from the Settings Menu → go to General → go to Global section and Enable audio split for voice recordings
From the Settings Menu → go to General → go to the Quality Analysis section
Choose the default Language for audio transcriptions
These are Supported languages and features for Transcribe https://docs.aws.amazon.com/transcribe/latest/dg/supported-languages.htmlIndicate the created S3 bucket where your transcriptions and analysis data will be uploaded (bucket refers to Transcribe, Sentiment Analysis and Post call analytics)
Configure the Quality Analysis you want to use:
💡 How it works
Info |
---|
If you want to launch AI features using the New Client Experience explore this documentation |
1- Run Transcribe option, by choosing Region and Language for the transcription process (Language inserted here by default is the same indicated in General Settings)
Info |
---|
You always have the default Account selected but you can change it with another account if for example you have multilingual recordings and you know that with some languages AWS Transcription is best performing. In contrast, other language transcriptions work better with OpenAI. |
When you click on Start Transcription, technically your audio is sent to a bucket configured on AWS, which, when it is ready, takes the audio from this bucket and launches the transcription.
You can see the transcript in the specific tab (Edit Voice Recording):
2- Run Sentiment → you will always see AWS Account (with Region and Language) to choose and see the Sentiment Analysis in the specific tab (Edit Voice Recording):
Sentiment analysis:
Sentiment analysis inspects the call transcript text and returns an inference of the prevailing sentiment (POSITIVE
, NEUTRAL
, MIXED
, or NEGATIVE
) and their corresponding confidence levels.
Sentiment determination returns the following values:
Positive – The text expresses an overall positive sentiment.
Negative – The text expresses an overall negative sentiment.
Mixed – The text expresses both positive and negative sentiments.
Neutral – The text does not express either positive or negative sentiments.
SENTIMENT (first box): The inferred sentiment that Amazon Comprehend has the highest level of confidence in.
POSITIVE, NEGATIVE, NEUTRAL, MIXED: Amazon Comprehend confidence levels for each sentiment.
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Consult Amazon Documentation: https://docs.aws.amazon.com/comprehend/latest/APIReference/API_DetectSentiment.html |
3- Run Post call Analytics (choosing Account with Region and Language) and see the analytics in the specific tab (Edit Voice Recording):
Post-call Analytics sentiment analysis estimates how the customer and agent are feeling throughout the call. This metric is represented as a quantitative value (with a range from -5
to 5
). Quantitative values are provided per quarter and per call.
This metric can help identify if your agent is able to delight an upset customer by the time the call ends.
Post-call analytics: Call overall sentiment score per speaker, with a range from 0
to 5
. XCALLY recalculates Amazon’s metrics (for example, -5
(Amazon) corresponds to 0
(XCALLY), 0
(Amazon) corresponds to 2,5
(XCALLY), 5
(Amazon) corresponds to 5
(XCALLY)).
Time graph sentiment: It displays the overall sentiment per speaker per quarter, with a range from -5
to 5
.
Clicking on one of the four points (call’s quarters) of the line, sentiment scores per speaker are shown.
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Consult Amazon Documentation: https://docs.aws.amazon.com/transcribe/latest/dg/call-analytics-batch.html |
🔧 Troubleshooting
To check if the Redis container is started correctly, you can follow this procedure:
connect to the machine in SSH and launch this command as root user
Code Block |
---|
docker ps |
in the list of active containers, a container using the Redis image (in IMAGE column) and named “bullmq-v1” (NAMES column) should appear.
Moreover you can see that in PORTS column, the host port 21000 is mapped (in this case to internal port 6379 on the container).
Note |
---|
If running the |
Code Block |
---|
curl -u 'public:bs4#)W]h8+VK),RV' --silent --location https://repository.xcally.com/repository/provisioning/Scripts/motionV3_new_feature_update | bash |
Then you need to check the environment variables in the .env file:
Quality Analysis SECTION | XC_QA_QUEUE_WORKERS=10
timings redis port | XC_QA_REDIS_PORT=21000
timings redis db | XC_QA_REDIS_DB=0
timings redis username | XC_QA_REDIS_USERNAME=
timings redis password | XC_QA_REDIS_PASSWORD=
1 hour | XC_QA_REMOVE_FAILED_JOBS_AFTER=3600
7 days | XC_QA_REMOVE_COMPLETED_JOBS_AFTER=604800
Finally as motion user
Code Block |
---|
su - motion |
go to folder cd /var/opt/motion2
and launch this command
Code Block |
---|
npm run initialize |
to apply the changes to the environment variables, but consider that it restarts the API and it can create disservice (so it is recommended to launch it while you are not using the server).