Users with a valid gmail address or GSuite credentials can sign directly into Avochato using our desktop and mobile web experience. This sign-in mechanism is available to all customers on all plan types.

Click the “Continue with Google” be redirected to sign in to your Google account and then redirected back to Avochato.

This will only work if your GSuite or gmail account matches your Avochato user.

Click the “Continue with Salesforce”, you’ll then be redirected to sign in to your Salesforce account and then redirected back to Avochato.

Note: In order to sign in with Salesforce, your organization must connect at least one of your Avochato inboxes to Salesforce via Integrations > Salesforce, and your user(s) must be synced between Salesforce and Avochato. Unsynced users will not be able to authenticate.

Avochato does not currently support SCIM and all users in your organization that you wish to access Avochato must be invited manually via the Invite Team page. Users in your organization who have not been invited to any inboxes in your Avochato organization will not be able to sign into Avochato via Google.

If you do not have an Avochato account, you can now Sign Up with Google.

Click “Sign up with Google” to authorize creating a new Organization associated with your gmail address.

If your Gmail is already tied to an existing Avochato account, you’ll be redirected into your Avochato inbox after successfully authorizing via Google Single-Sign On.

We’ve fixed an issue where the sign-in button remained greyed out when using a password manager (such as 1Password or LastPass) to populate the email and password.

All AvoBots and AgentAssist features now use the latest ChatGPT-4o model by default.

Custom prompts are now optional when setting up an AvoBot - you can go live with your AvoBot immediately and setup custom prompts later.

If you do not setup any custom prompt(s), a standard default internal prompt will be used instead.

Reminder that AvoBots and AgentAssist can be used separately or together - having one disabled does not impact the other.

Auto-Suggestions now appear a little less frequently and will only automatically suggest a response when you’ve received a recent inbound message.

You can still request a new suggestion at any time by clicking the “Suggest a response” button.

If the conversation/contact is unowned, and that tag happens to be a routable skill, we will properly route the conversation to an available agent who has the associated skill. If the message creates or re-opens a conversation, it will immediately route the conversation using skill routing.

For inboxes using Skill Routing, any Inbound event will trigger skill routing for any unassigned conversations (previously, routing only happened when convos were created or reopened due to an inbound message, and only for widget chat submissions).

This "fix" may cause changes in behavior that users might have gotten used to, but is how skill routing is intended to function.

It does not impact inboxes that have disabled Skill Routing or have no agents on the Auto Assignment Roster.

This creates use-cases where customers can trigger routing via inbound keywords (see above), including mid-conversation for any conversations that are unassigned, and more.

While skill routing is enabled, existing skills on the contact will be factored into the routing decision. (Previously only tags on the conversation, which could only ever get applied by live chat widget submissions)

Ex: if a contact that has the "support" tag for whatever reason, and their conversation was closed or unassigned, we will route to an agent with the "support" skill, even if the inbound message itself does not trigger a skill keyword associated with “support”.

Any keywords that are not currently active, due to your inbox’s office hours, not trigger skill routing.

Inbound live chat submissions and messages now properly check agent availability when received. Previously, they would ignore the agent's status.

When the current owner is unavailable or missing, the conversation will be reassigned according to the inbox's settings. This behavior also applies to inbound messages that trigger skill routing.

We’ve moved most of all configuration settings for skill routing under the Tags section, including the entire "Enable Skill Routing" subsection.

There are breadcrumbs in the settings page where the skill routing section used to be under "Convo MGMT" to guide you to the new location.

Skills are now visible in the Auto Assignment roster as well as the Org Users list, but they aren't editable there.

Additionally, a number of quality of life improvements have been made to creating and managing skill tags.

We’ve standardized the thumbnails for MMS attachments including PDFs, CSVs, .txt files etc that are received by the inbox.

Images and Videos will also have a new standardized height and width when shown in a conversation (but can still be clicked on to expand the file to its full resolution).

We’ve made it a little easier to add a list of contacts to a broadcast - users can now drag and drop a CSV file directly onto the audience list to start adding contacts to your broadcast (not available on mobile).

Previously you had to click “add audience”, then “add by csv”, then drag and drop the file, then hit submit. Enjoy.

Context: The "Group Activities" feature batches multiple activities to sync to Salesforce in a single API request, reducing API credit usage. This power-feature is optional but can make a big difference when syncing large activity volume to Salesforce.

Contact syncing now triggers automatically whenever a group of messages is synced to Salesforce from any inboxes while the "Group Activities" feature is enabled. Note: enabling this feature while “Group Activities” is disabled has no effect.

With this update, we now sync contact records for all contacts associated with these batched activities at the same time. This ensures Contact records stay current, particularly when using Surveys or other automations that update contact information with each message. It's especially useful when contact information must remain consistently up-to-date.

Authorized users can toggle this setting under Integrations > Salesforce > Settings on a per-inbox basis, and defaults to on.

While this feature can be disabled for individual inboxes, we recommend keeping it enabled when using “Group Activity” syncing.