Line Intelligence - Carrier Tracking Updates
Last release, we wrapped up all of the functionality of the Line Intelligence feature. However, in this release we have added a couple of enhancements to the feature in light of some recent carrier events that will make the data we collect more useful. Within the same data response that we get about the type of phone number, we also get what carrier that phone number is on. We have updated our code to now capture the carrier information along with the Text Enabled status and display that on the Contacts page.
Store Carrier Type from Line Intelligence Response - This will take the carrier informationt hat comes back from the API call and do some mapping and ultimately store it in the database. If the carrier was something other than the big three (ATT, T-Mobile, Verizon) or some of our carrier aggregator partners like Zipwhip/Bandwidth/Twilio, we lumped it into "Other".
Add Carrier Type to Contacts Page & Export - We added a column to the Contacts page to display the Carrier Type as well as added this and the Text Enabled Status columns to the contact export.
CRUDy | Account Lines & Users Added to Account Page
Now, for easy access we have added a Lines section and a Users section to the Account Detail pages in CRUDy. This will reduce the number of steps you need to take to quickly see which lines or users are in an account.
These collapsible sections can be found underneath the Product Permissions section on an Account's page.
Public API | Bulk Save Contacts Endpoint
We have created a new endpoint that allows you to bulk save multiple contacts in one call.
Translation Service | API Layer with Usage Tracking
In this release, we are pushing out the platform API layer of the Translation Service that will be used to power the front end UI as well as the Public API endpoints. In addition, we created the tracking for usage so that when we roll out billing, we can understand exactly how many times a given client has used the feature.
Platform Health | Improve Automated Testing
We improved our automated testing coverage across 9 of our core areas of the platform. This testing coverage will help us improve the quality of our code and what is being deployed, prior to the manual QA testing step. Areas where automated test coverage was improved include:
Sending messages
Contact saving/adding
Scheduling blasts
Responder actions
Conversation search performance
and several more.