Translation Service (Released 11/6/2023)

On November 6th, we released the final feature to complete our Translation Service feature in Textel. NOTE: This is a paid add-on feature. It is not one to be given away or activated on accounts for free.

Charges are incurred per translation (not per message). Meaning, the client is charge each time they make a request to translate something regardless of if it was used to send in a message. This would include translations done and stored on inbound messages.

Feature Overview

Outgoing

Anywhere you can compose a message (Conversations, Responders, Blast, etc.), you will see a translate icon. Clicking on the icon will take your typed out message and allow you to translate it into your language of choice. Once you have a translation you want to use, clients can copy the message and paste it in the message box to send. 

Incoming & Message Panel

For already sent messages or incoming messages, there will be the option to translate the message in the message panel. We will auto-detect the language and ask you what language you want it translated to. Once translated, it will show up in the message panel as the translated version for anyone viewing the conversation. There will be a "See Original" link below the message that would allow you to toggle it back to the original version (which would then display a See Translation link to revert back to the translated version).

API

Translation is available via the public API as well. WE have several calls outlined in our updated public API documentation that allow clients to use this feature via API. NOTE: This also makes it possible for us to use the Translation Service in Capacity's Dev Platform.

Auto-Translation Not Included

There is no auto-translate feature. Because of how we are billed for translation usage, we do not have any settings that will automatically translate incoming messages. Because we store translations, once done, in our system, we are only allowing on-demand translation.

Where It Is Available

• Directly in the Textel platform UI.

• Limited availability in the UI for translating composed messages for Nice & Genesys CCaaS. CCaaS agents will be able to translate and view translations for messages that display in the pop-out panel. 

• Available to all integrations via API.

• Not available to the RingCentral MVP integration via UI due to our lack of interface control in their platform.

Capacity Contact Syncing Initiative

One of our Q4 initiatives is to set up infrastructure to enable contact syncing between the Textel and Capacity platforms. This is a key step in surfacing seamless SMS/Inbox features as well as bolstering our Capacity CRM when texting is enabled for a Capacity CRM. In this release (and some previous releases) we have included:

1. Added Capacity Contact Id field to our Textel contacts table

2. Ability to push incoming contact creation events from Textel to Capacity

3. Ability to consume Capacity contact updates (new contacts, new phone numbers, name updates, etc.)

4. Added a new platform API endpoint to allow for updates to a contact's opt status by line

5. Ability to process line deletion events from Capacity

6. Removed support for adding contacts with Alphanumerics on the Textel side

Public API | Send Message Updates

1. Public Send Message API endpoint now allows up to 1600 characters in a single message

2. Public Send Message API endpoint will not provide more detailed error messages instead for 400 bad request when

   1. Images are invalid

   2. Message size exceeded

   3. And other error messages that occur at lower layers of the code

Bug Fixes

1. MEDIUM - Individual Lines could not be selected in reporting but All Lines worked

2. MEDIUM - OwnerUserId was being set to NULL on update of email

3. MEDIUM - Updated Shortcode & Alphanumerics to be included in rate limiting for Blast