This release brings a host of new features and bug fixes to Avochato, including additional user management functionality, survey usability updates, an “undo send message” option, new Salesforce conversation status syncing, broadcast assignment, and more.

There is a new option for syncing conversation status changes to Salesforce to a dedicated Avochato__Status__c field. When enabled, the conversation status will sync whenever it changes.

Head to Integrations > Salesforce > Settings to turn this setting on, per inbox.

You can now designate a user (or AvoAI agent) to be assigned to all conversations associated with a broadcast. This is optional and defaults to no changes. Specify an assignee, and all conversations touched by this broadcast will get assigned to the user (or bot):

Conversations with contacts that end up being excluded from the broadcast (either due to being opted out, removed from the broadcast before it sends, or due to the contact not receiving the broadcast before it gets cancelled, etc) will not be reassigned.

When an AvoBot gets assigned to a conversation, it will automatically respond to the contact when they reply to your broadcast.

Assignment occurs when the message is attempted — so assignment will happen over time as the broadcast sends sequentially, and will never happen if we don’t attempt to send the message for any reason.

Meanwhile, we have also streamlined the steps 1 and 3 and removed some redundant elements, and fixed a number of issues with the UI.

However, once sent by Avochato, cell carriers will deliver your message and they can no longer be un-sent.

We hope this makes it easier to catch and correct typos or unsend messages that were sent to the wrong person.

Users can enable this optional feature under their profile.

Gravatar Users will still see their Gravatar (if they have one associated with the email they use to sign into Avochato) but otherwise Gravatar support has been deprecated.

These custom profile pictures will be incorporated into the rest of the inbox in the near future, stay tuned.

All users start out as “enabled” when you invite them to your inboxes. However, if you have ever tried to remove someone from an Avochato inbox, you may have felt the pain later of trying to understand historical analytics reports, logs, and other metadata because that user no longer exists in the account.

We’ve added a new feature for Owners to disable users in specific inboxes (or all inboxes) so that you can securely remove a user’s access to Avochato without impacting reporting or other metadata, while minimizing your usage of Avochato seats.

This process is reversible in case the user returns to your organization or you make a mistake, and does not require contacting Avochato support.

From the inbox: Managers and Owners can view the Invite Team tab, find the User, click Actions → click Disable User and hit confirm to disable a user in that specific inbox.

From Organization Management: Owners and users that have access to the Organization Management dashboard can click “Organization Management” → “Users” → lookup the user, then view their list of each inbox they currently have access to. Either Cl

Click on their User Status to toggle their status from “Enabled” to “Disabled” their access in a specific inbox. All of their permissions (can make calls, etc) will be denied automatically as long as they are disabled.

Once a user is no longer enabled in any of your inboxes, we will automatically revoke their seat so you can assign their seat to someone else. This is intended to make seat management easier for larger organizations that clean up users over time but still want records of their historical assignments or analytics data without creating a security concern.

A disabled user can be re-enabled by a Manager or Owner by clicking “Enable User” in the inbox; or by toggling their user status in the Organization Management section.

They will retain all their previous permissions and role. For example, if you disable a Manager, then re-enable them, they are once again a Manager in that inbox with the same settings as before. However, you still need to manually re-enable their Forward Number or Auto-assignment roster (if applicable) if you are restoring their access to an account.

Note: There is no way to mass-re-enable a user - please reach out to Avochato support if you need help with this.

If they previously were not counting towards a seat (ex: they never had a seat, or they were previously disabled in all inboxes and lost their seat), we will attempt to assign a seat to them when they get re-enabled.

A user enabled in at least one inbox will require one of your Organization’s seats to send messages.

The sign in page has received some cosmetic updates.

You can now search and sort Conversations by the activity_at timestamp, which indicates the most recent event in a conversation’s event feed.

Avobots now default to a one second delay - this is configurable to 0 for fully-automated AvoBots, or more seconds for user-in-the-loop use cases. Previously there was no delay - all current AvoBots have been defaulted to zero seconds if not already set by the user. Increase the delay to increase the amount of time to review any messages that the AvoBot will send to a contact. AvoBot messages can also be unsent (if caught fast enough).