Release notes - 3.2.0

Release date: 18/06/2025

Updated Azure Search functionality

We’ve improved how documents are indexed and retrieved in Azure Search. Newly created indexes now support chunk numbering and document IDs, helping to increase accuracy and speed for generative answers.

  • How it works: To enable this, delete and recreate your Azure index to ensure it’s at least version V2. If you’re using an older index version, your setup will continue to work as before, with no changes. New indexes will also use smaller chunk sizes by default—this helps the LLM receive more relevant data, improving answer accuracy and generation speed.

Search timestamp

Bots now understand “now”. We’ve added a timestamp to the base LLM prompt, making generative scenario responses more consistent when handling time- and date-related queries.

  • How it works: You don’t need to do anything—this is included automatically in all LLM prompts for generative bots.

Improvements

  • Embedding character preservation: The embedding service now retains symbols like @, /, $, and _, reducing misinterpretation of questions.

  • Date handling in embeddings: Improved logic to better embed phrases containing dates and punctuation.

Bug fixes

  • Duplicate webhook entries: Fixed a bug where webhook data could be indexed multiple times in some cases.

  • Conflicting datasource states: Resolved an issue where datasources could be marked both “waiting to be deleted” and “waiting to be synced”.

  • Embedding over-cleaning: Fixed an issue where important characters were removed during embedding, leading to inconsistent responses.

  • Extra logging: We’ve added extra logging to our engine service to monitor a bug reported by one of our clients.

Coming next

  • LLM contextualiser: We’ll soon reword user queries for Azure Search based on previous conversation turns—improving precision and recall.

  • Genesys Cloud integration: A native integration for human takeovers is in the works.

What this means for you

If you’re not using generative scenarios or Azure Search, these changes won’t affect your setup. Questions? Reach out to your Oswald support contact—we’re here to help!

Last updated

Was this helpful?