Capacity Integration Progress
Handling Auto-Close Conversation Setting
In our platform, clients can configure a setting that will auto-close a conversation after x minutes of inactivity after the last message. When this is set, we want to make sure that we handle this use case and end a bot session if one is in progress. Now, if the conversation is inactive for a long enough period to trigger the Auto-Close feature, our system will not only close the conversation on our side, but will send the signal to Capacity to end the bot session as well.
Conversations | Display Opt Out Status
When contacts opt out of receiving text messages from a number, we do not have an obvious visual indicator in Conversations to indicate this status. We still enforce the opt out and do not send messages, but it was not clear to our users that a contact they were attempting to message was opted out.
We have updated our Message Panel view to show several indicators that a contact is opted out and prevent any attempts to even compose a message. The contact's name/number will be highlighted red with a tool tip. The Compose Box will also be replaced with a note that the contact is opted out. This view is also surfaced in the pop out panels that we display in our CCaaS integrations.
Lastly, we also added a check when attempting to create a new conversation with a contact who is opted out. We will now display a message to the user telling them they cannot send messages to an opted out user unless they expressly opt back in.
CRUDy | Internal Support User System
We created a system to allow our internal support team to log into client accounts to troubleshoot and recreate issues that are reported. This was done in such a way that a special user type is created per account that is only visible to our internal team and only accessible via our CRUDy tool.
How to Use
Navigate to a client's account page in CRUDy and scroll down to the Support section.
Click on the Login as Support button.
This will open our app with you logged in as the support user with a temporary token that is good for 30 minutes.
If the session has expired while troubleshooting for longer than 30 minutes, click on the login button again to refresh the token.
Support users are visible in the CRUDy application when searching users. If one has not yet been created for an account, it will be automatically on first click of the Login button.
NOTE: These users will not count against our client's user usage for billing.
Nice CXone | Prevent Service Bus Timeout Errors
We had some optimizations to our Nice code base to prevent service bus timeout errors in our logs.
Bug Fixes
HIGH - Bulk Line Imports in CRUDy Generating Incorrect ZW Webhooks
MEDIUM - Prevent Conversation from Crashing when invalid messages exist