Multi-Recipient Send - Can Now Select a Contact List
When you go to use our multi-recipient send option to create conversations, you now have the choice to select up to 20 contacts individually or select from an eligible contact list.
For a contact list to be eligible to display in the dropdown for selection, it has to have 20 contacts or less in the list, otherwise it will not display as an option.
Add Contact to List from Edit Contact Modal
When you are editing an individual contact on the contacts page, you can now also modify which contact lists they are a part of, directly within the modal. It makes it easier for the times when you need to make a small adjustment on contacts and do not want to use an import.
Scheduled Messaging
Users of our Conversation product will now have the capability to schedule messages both within a specific conversation or using our Multi-Recipient form to schedule a send up to 20 recipients.
This is specifically limited so that it does not cannibalize our Blast product, but puts us at feature parity with the Zipwhip 1.0 portal.
Clients can also view and edit their scheduled messages to see what is in queue.
CRUDy Update - Import Nice Line Settings
On bulk line imports, now when you specify the integration type as Nice, you can now add two optional columns to the import sheet to allow you to set the POC and the Hide Attachment from URL settings.
You will need to add the following column headers:
Point of Contact Id
Hide Attachment From Url
Accepted values are 0 or 1
Platform Health Items
To make our messaging queues more resilient we have moved message processing queues to using Service Bus instead of Reliable Collections. This is going to help us with scalability and more reliability when certain types of events happen and we need to recover quickly.
Outbound Message Queue to Service Bus
Received Message Queue to Service Bus
Message Status Queue to Service Bus
Bug Fixes
CRITICAL: Message Snippet Errors when loading conversations if the message ends in an emoji at the breakpoint
MEDIUM: Bandwidth Outbound Messages Not Working
MEDIUM: Public API | Send Message Fails When Same MessageId is Provided
MEDIUM: Message Protocol not nullable in message segment entity
MEDIUM: Re-Editing a contact from the message panel throws an error
MEDIUM: Blast Campaign Status Stuck on "Running"
MEDIUM: Report Microservice Needs Nuget Package Update
MEDIUM: Holiday Responder date defaults to 1/1/1970 if the user does not explicitly hit OK in date selector
Security Updates
Forgot Password Should Always Return True
Platform API | Add Validation that Account can Send on Line
DFO (Digital First Omnichannel) Integration Endpoints
In order to integrate with Nice CXone's newest product offering, we had to provide them API endpoints to our legacy 1.5 platform because at the time, our new platform was not ready. However, now that we are close to full roll out, we now have a Public API on the new platform so we have created a new set of endpoints that mimic 1.5 formats so we can do a swap.
Send Message
Get Message
Get Media
Endpoint Updates for Scripting
Allow Customer Header for User Device - Allows for customer header when the User-Agent header isn't present
Change Get Last Persist Value endpoint to a POST
Fixed: SendMessage fails for lines that do not have POC - Deployed independently on 8/17/2022
Endpoint for Billing
GET Nice CXone Blast Accounts - Deliver a count of Nice accounts that have Blast enabled
Ability to Use RingCentral as a Carrier
In an effort to grow our partnership and integration options with RingCentral, we have added them as a carrier in our network. This could be useful in some future opportunities for shared clients and various options to deliver texting solutions to that client base.
We are now in the phase of getting our API integration through their Production "graduation" review, which should happen in the next week.