Embedded Files
Textel Platform Updates
Textel Platform Updates
Blocking Contacts
We have had a few requests from clients (including TMZ) who want to have the ability to block a contact. It is important to note that while we cannot technically block mobile contacts from sending messages to one of our customer's lines, we can suppress them getting notified and receiving the message in their conversation stream. So, our platform will still receive inbound texts from the blocked number, we just will not display them or add them to conversations.
Customers will also not be able to message a blocked number either. We will prevent that in a similar way that we do for Opt Outs.
This feature will be available to all clients who use our conversation interface. To block a contact, simply open the Edit Contact modal for the contact in question and check the "Block incoming messages from this contact" checkbox.
Messages that are received from blocked contacts will still show up in reporting, but will be marked with the Type of Blocked.
Public API | Get Supported Languages Endpoint
In preparation for our Q4 release of the Translation service, we have added a new endpoint to our Public API that allows clients to get a list of the supported languages and their acronyms that will be needed to make API calls to translate to specific languages.
This full feature is not ready to release to clients. We are a few stories away from making all of this customer-facing.
Gensys CCaaS Integration Options
In attempt to accomodate an issue where Genesys is expiring auth tokens for clients who use an external SSO service like Okta, we have provided an alternative path for these clients to authenticate with our platform. We now allow direct login via individual agent/user accounts. NOTE: This is not a recommended approach for clients by default. We recommend our integration user auth pattern, but we are working on providing one of our clients (RunBuggy) with an alternative option for using our integration while we await on Genesys for a resolution.
Genesys | Close Internal Conversation on Chat End
CRUDy | Account Owner User Change Management
We have had several issues where the account owner's email address was changed on the user page but not synced with the account page. Or where the account owner user was deactivated and no ownership transfer was made. Or the account owner user's API permissions were changed on an account that had API permissions.
These inconsistencies often led to a break in the API authentication pattern. To address this we have implemented a few things:
We now link the account owner by ID instead of email. This will eliminate issues if the email is updated in one location but not the other.
We now show a warning on the account owner's page when you attempt to edit the permissions or user's status.
Bug Fixes
MEDIUM | Twilio Line Migration bug - Null Key Exception
MEDIUM | Foundation | User Should Not be Able to Access Line in Another Account
Page updated
Google Sites
Report abuse