Overview

When a Digital Person has the Transcription Skill, the conversation session is stored as a text file in the Customer’s secure Amazon S3 container with the user's requests and conversation responses. The transcript is updated throughout the conversation until the session ends.

This skill is:

  • Built and owned by Soul Machines Ltd.

  • Only supported in English.

  • Powered by the Amazon S3.

Transcription Files

Where to find the transcription files in Amazon S3?

<screenshot of sample transcription>

  • If the Digital Person in sleep mode, there will not be a response line from the Digital Person.

  • The file name is in the format YYYYMMDDTHHMMSS_{SessionID}.txt

Limitations

  • Transcription Skill doesn't work with Translation Skill if added to the same project

  • The Digital Person cannot differentiate between users if added to a MS teams meeting

  • The time stamp is in UTC time zone

Skill Demo

Configurations

Provide the following information in the Transcription Skill configuration screen in Digital DNA Studio. See Adding Skills to your Digital Person for detailed instructions:

Field

Type

Description

AWS REGION

(required)

TEXT

AWS region code based on where your Transcription Skill resource has been created. See this page for a list of region codes.

Note: Make sure to use the region code. For example, you should enter ap-southeast-2 rather than the region name, Asia Pacific (Sydney).

AWS ROLE ARN

(required)

TEXT

Enter the ARN from step 7 below.

Format arn:aws:iam::{Account_ID}:role/{Role_Name}

UNIQUE EXTERNAL ID THAT CONNECTS TO YOUR AWS ACCOUNT

(required)

TEXT

Is the same as the External ID generated in step 3 below.

NAME OF YOUR AWS S3 BUCKET

(required)

TEXT

The name of the s3 bucket you would like the transcription files to be uploaded to

Creating AWS Role for Transcription Skill

  1. Log into your AWS account where the Lex Bot is provisioned.

  2. You will need to generate an External ID that our services will use as a unique identifier to connect to your Lex Bot, the External ID is any unique string that should be a minimum of 16 characters alpha-numeric string.

  3. Go into the IAM tab in the AWS Console and click Roles > Create Role at the top right corner.

  4. In the role creation screen, click Custom trust policy entity type and copy the below code block into the policy field, make sure to replace <Your External ID> with the string generated in step 3 and click Next.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": [
          "arn:aws:iam::858507401646:role/SM_Transcription_Role"
        ]
      },
      "Action": "sts:AssumeRole",
    "Condition": {
        "StringEquals": {
          "sts:ExternalId": "<Your External ID>"
        }
      }
    }
  ]
}

  1. In the Add Permissions screen, find the

AmazonLexRunBotsOnly policy, select it, and click Next.

  1. Ensure to use the below value as the Role Name otherwise the bot will not be reachable using this Role (this is a case sensitive value) and verify that all the other values (Aside from your unique External ID being different) match the code provided in step 4 and click

Create Role.

SM_Transcription_Role

  1. Once the role is created, navigate to the

SM_Lex_Access_Role role under the Roles tab and you will be able to copy the Role ARN.

Content