See What's New at Avochato.

AI Search Overhaul, Inbox Search Enhancements and AvoAI Improvements

June 2, 2025

NEW

This update brings a number of new features and enhancements to searching the inbox!

AvoAI Search

We're excited to expand our image recognition capabilities of AvoAI agents. AI Agents can analyze and understand images in your conversations, making search and context awareness even more powerful.

Note: you can only search for images or attachments received before enabling AvoAI. Please contact us for more information.

Notion image
  • Image Recognition: AvoAI can now securely analyze images shared in conversations. Other attachment types like .pdfs, videos, etc are not evaluated. You must enable AvoAI search to begin analyzing image attachments.
Notion image
  • Enhanced Search: Use the prefix media: to search for specific features detected in images. Ex: searching the inbox for media: cat will find conversations containing photos of cats. A tooltip will appear when you hover over an attachment that was scanned by AvoAI, containing a list of each of the detected features.
Notion image
  • Content moderation: “NSFW” and “Sensitive” attachments will be blurred by default (unsolicited sexual content, images containing personally identifying information, etc).
Notion image

AvoAI Search is enabled by default for all eligible accounts. AI usage fees apply per image.

Images are never processed from “blocked” contacts or for inbox that have disabled inbound attachments.

 

Inbox Search Enhancements: Messages

We’ve overhauled searching the inbox when looking for a specific message.

You still need to use the message: syntax when searching the inbox for messaging containing a specific term.

Notion image

Note: This does not require AvoAI and is available to all customers.

Search Result Highlighting

It's now easier to find messages that get lost in your inbox:

When you search your inbox by message (for example: message: cats or message: "call me"), matching results are highlighted both in the inbox list and conversation feed. Every conversation containing a matching message will display its most recent match in the conversation list. You can add additional search criteria including changing other filters in the inbox.

Notion image

The most recent match appears in your conversation list, and clicking it opens that specific message. As you scroll through a conversation, you'll see all matching results highlighted.

Notion image
 

Advanced inbox searches

You can combine search terms (message: “San Francisco” area_code: 415) as well as apply any other inbox filters (such as ticket status, assignee, etc).

Future Search improvements

While it is not available in this release, we’ve heard your feedback about a simpler search form (especially for searching for messages) that require less syntax to “just work”, and we have more exciting updates coming soon that will make searching easier, including using simpler search syntax and UI elements.

Stay tuned!

AvoAI + Salesforce

Contact Digest Timing

Our “Contact Digest Timing” setting lets you control when to generate Contact Digest, a secure set of data scoped to each active conversation that gets pulled live from your Salesforce instance. The digest gets used when communicating to your contacts or generating suggestions, and is visible under the “Edit Contact” tab for quick reference.

New: We’ve enhanced the Contact Digest feature with some new configuration options. We’ve also updated the description and provided some more disclaimers for users to be aware of how and when the digest works.

Notion image

Two powerful new options that will only generate and use digests in either of the following scenarios:

1. “Only for AvoAI Agent Conversations”: we will automatically generate the Contact Digest when assigning a conversation to an AvoAI Agent. Conversations assigned to Users, as well as Unassigned conversations, will not generate new digests or use existing digests when generating auto-responses or suggestions. Choose this option if: you want your AvoAI Agent to always have access to the digest when answering inbound messages, but your team handles most of your conversations and already has access to the most recent information (ex: while using the Avochato Salesforce Widget or working directly from Salesforce)

2. “Only for User Conversations”: we will automatically generate the Contact Digest when assigning a conversation to a User on your team. Conversations assigned to AvoAI agents, as well as Unassigned conversations, will not generate new digests or use existing digests when generating auto-responses or suggestions. Choose this option if: you want your team to get rich suggestions that are enhanced by your Salesforce data, but you want to restrict your AvoAI Agent from having access to that information when it is responding to a conversation.

These options join our previous two options (”For every conversation”, and “Only when I click Generate”)

To be very clear: we only generate and use the Contact Digest if your inbox has enabled the “use contact fields in responses” flag within your account’s Automation tab.

Notion image

You can also disable the feature entirely to immediately prevent creating or using any Contact Digests, regardless of who is assigned to the conversation.

Notion image

Any digests you generate will automatically expire after 30 minutes.

AvoAI

Sentiment Insights

You can choose to have the bot escale to an agent without sending a message. By default, the AvoAI Agent responds while it looks for someone to assign the conversation to.

Notion image

You can choose to always trigger sentiment whenever we escalate to an agent (off by default, requires Sentiment to be enabled)

Notion image

Note: Periodic sentiment analysis jobs only analyze conversations with enough inbound and outbound activity to qualify for sentiment analysis (typically three messages each from the contact and from an agent, minimum). For example: a long two-way conversation with many inbound and outbound messages that happens to end with an inbound “STOP” would still qualify for sentiment evaluation. Meanwhile, a conversation with many outbounds, such as a conversation containing many broadcast messages to a specific contact who then finally replies “STOP” would not be evaluated for Sentiment due to a lack of inbound messages.

Bug Fixes

AvoAI

  • Sentiment no longer runs when the only inbound is an opt-out message, including STOP keywords or any detected responses to a broadcast that Avochato detects to be revoking consent to receive texts.
  • AvoAI Agents will not try to address a contact by name if their name is “non-human” (ex: missing, numbers, symbols, gibberish)

Inbox

  • Fixed an issue where clicking a notification would not take you to the associated conversation while in certain parts of Avochato
  • Fixed issues with opening and closing the left-hand menu
  • Fixed an issue with the header while viewed in Salesforce
  • Added a close button to close the left-hand nav on mobile devices
  • Fixed some issues with opening a conversation and not being scrolled to the most recent message
  • Scrolling backwards through historical messages should be smoother in general and handle scrolling while receiving new events
  • Fixed issues that randomly prevented scrolling through older messages until refreshing the browser or clearing cookies
  • Fixed crashes when opening conversations without any event history
  • Fixed incorrect ordering of call in-app notifications — notifications should always be presented in the order they were created

Tags

  • Fixed various issues with tag synchronization — removing tags from the Edit Contact page, bulk removing tags from the inbox, and deleting tags from the Tags and Skills page properly syncs to everyone currently using the inbox. You’ll see tags disappear in real time when a teammate or automation removes the tag from that contact or conversation (just like when tags are added to those contacts or conversations).
  • Using the tag removal button on the Edit Contact page should correctly update that specific contact’s list of tags in the Contact list
Did this answer your question?
😞
😐
🤩