> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/release-notes/receptionist-for-broadworks/receptionist-for-broadworks-bw2025.01.md). # BW2025.01 Release history for Receptionist for Broadworks BW2025.01. Review exact versions and applicability, not a supported-version matrix. {% hint style="warning" %} These three families form an editorial window, not a supported-version matrix. They cover the five published bulletins listed in the product overview. The Dialogue Cloud Neo N through N-3 policy does not establish support status for this product. The sections below retain changes introduced in each exact release, newest first. They are not cumulative claims. Review each release's consent, permissions, client, and configuration requirements before use. {% endhint %} ## BW2025.01 {% hint style="warning" %} Published Receptionist for Broadworks bulletin for BW2025.01. The feature descriptions and prerequisites below apply to this release. Publication does not establish deployment in every environment or a current support phase. {% endhint %} Welcome to the PeterConnects (part of AnywhereNow) Software Technical Release Bulletin. The purpose of this Bulletin is to update you on the improvements we are making to our software and share with you the latest Change List which has been designed to advise you of all changes made to our products. Our Technical Release Bulletins are the easiest way for you to keep up to date on the latest improvements to the PeterConnects (part of AnywhereNow) product line and how you can leverage these investments for your customers. Whenever applicable, the changes described below are also covered by the user manual. ### List of fixes ### 125171: Number recognition - reverse lookup working as expected #### Issue Description: The reverse lookup functionality for number recognition is working as expected. However, an issue arose when enabling the cache feature. Specifically, when performing a number lookup in F2 and the number was not found in the cache, the system failed to consult the BW backend as a backup source. #### Cause: This issue occurred only when the prefix of the number saved in the cache was not in the same format as the incoming number. In this scenario, the lookup process would not properly fall back to the BW backend for the missing result. #### Resolution: The issue has been identified and corrected. The system now properly consults the BW backend when a result is not found in the cache, even if the number formats do not match exactly. ### 125841: Search is possible when keywords are divided by underscores Search functionality is now supported when keywords are separated by underscores. #### Implementation Detail: Underscores are now properly recognized and considered when breaking down parts of names for cache search purposes. This ensures that searches involving underscores are handled correctly during the cache lookup process. ### 125616: unclickable buttons/uncontrollable call #### Issue Resolution: An issue where buttons became unclickable and calls uncontrollable has been fixed. #### Description: In certain cases, after specific mouse movements, the call became uncontrollable, causing subsequent mouse clicks to have no effect. This issue has now been resolved, ensuring that all mouse interactions function as expected. [Receptionist for Broadworks release overview](/release-notes/receptionist-for-broadworks.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://atlas.anywhere.now/release-notes/receptionist-for-broadworks/receptionist-for-broadworks-bw2025.01.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.