> 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-bw2024.03.md). # BW2024.03 Release history for Receptionist for Broadworks BW2024.03. 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 %} ## BW2024.03 {% hint style="warning" %} Published Receptionist for Broadworks bulletin for BW2024.03. 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 changes ### 83321: Managing settings in agent profiles #### Manage Profiles: This feature is designed to streamline user settings management in the Receptionist for Broadworks. This addition allows administrators to create, edit, and remove profiles that bundle various settings, which can then be assigned to different users. #### Key Features: Profile Creation and Management. Administrators can create, edit, and delete profiles via Receptionist for Broadworks. Profiles include Receptionist for Broadworks settings such as joined queues, language preferences, and widget configurations, etc.. #### User Assignment: Admins can assign profiles to individual users. Users with assigned profiles will have consistent settings across logins #### Flexible Configuration: Users without assigned profiles can still customize their individual settings. Profile settings are captured at the time of creation, based on the admin's current configuration. #### Easy Profile Editing: Admins can load, modify, and save profile settings at any time #### Benefits: Streamlined user management for administrators Consistent user experience across multiple logins Flexibility to balance standardized and personalized settings ### List of improvements ### 121655: Search contact notes functionality #### Contact Search via Notes: Users can now locate contacts by searching through the content of notes associated with those contacts. This feature significantly improves the ability to find relevant contacts based on historical interactions or specific details recorded in notes. #### Real-Time Contact Note Updates: Instant Visibility for All Agents: Contact notes created by one agent are now immediately visible to all other agents without requiring a refresh or re-login. Improved Collaboration: This update enhances team collaboration by ensuring all agents have access to the most up-to-date information in real-time. Automatic UI Refresh: The user interface now automatically updates to display new or modified contact notes across different agent accounts. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-4df7c2a10769ec98ac95815533752aff09f85d94%2F1f8ad9a26fddf779.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/1f8ad9a26fddf779.png) ### 117523: Unexpected results on Omnidir when changing company directory #### Issue Resolved: Fixed a bug where changes to the contact search directory (between Enterprise and Group) were not immediately reflected in the platform. #### Problem Details: Changes made in the admin portal to switch between Enterprise and Group directories for contact searches were not taking effect until the cluster was restarted. This was due to the system failing to update its cache after the directory change was made. #### Resolution: Immediate Directory Updates: The system now correctly updates its cache when the directory selection is changed in the admin portal. Changes to the directory selection (Enterprise or Group) take effect immediately without action needed from AnywhereNow support. #### Impact: Administrators can now switch between Enterprise and Group directories for contact searches with the assurance that changes will be applied instantly. Improved system responsiveness to configuration changes, enhancing admin control over contact search functionality. Depending on the choice, the directory will only search in the group directory for contacts, or in the whole enterprise (all groups). When you are not part of an enterprise, you cannot change this setting. The setting is for all users in the same enterprise. ### 121657: External Contacts functionality #### External contacts: The system now supports importing external contacts from Excel files stored on SharePoint. Once configured, the system automatically detects and processes designated Excel files containing contact information. #### Admin Portal Configuration: Administrators can easily configure the import process through a dedicated admin portal. Admins only need to paste the SharePoint link to the Excel file containing external contacts. #### Instant Searchability: Once imported, external contacts are immediately searchable within the platform's contact search bar. External contacts appear alongside internal contacts in search results, where they can also be filtered Detailed description on the functionality can be found in the User Manual. ### 98709: Option to select alternative audio output for ringer In the Receptionist for Broadworks System, the device used for handling calls and the device responsible for ringing during incoming calls are the same. This contrasts with Teams, where you can set your audio devices independently. In the Receptionist for Broadworks, the ringer follows the computer's audio settings. With this new feature, operators can set an alternative audio output for the ringer on “My Calls” under “Audio alerting” in the Preferences. Once selected, the ringer will play on the chosen audio output. This functionality allows operators to avoid constant focus on the Receptionist for Broadworks and be alerted to incoming calls by the designated audio device. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-62898daa53552f3f68e2311508223989b78a6d86%2Fd4308f166e4068d7.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/d4308f166e4068d7.png) {% hint style="info" %} Note Be aware that additional consent may need to be provided to your browser to get access to the microphone when opening the preferences. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-3ee19b708ac38745d868baf0c2c59586ca4e3c0a%2F2829f4e8010d7ee5.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/2829f4e8010d7ee5.png) {% endhint %} ### List of fixes ### 97167: Webex Presence 'Busy' working as expected. The 'busy' presence status is now displayed in the attendant, when switching to 'busy' in the Webex client. As the Webex API only provides the status as "unknown", we interpret this as busy. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-c55329c817d69c1965a9a8abd9211620b8e8d556%2Ff3b7328691187c83.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/f3b7328691187c83.png) ### 109898: Support Directory Privacy for Receptionist Users When Directory Privacy setting is set for a user, as you can see in the screenshot below, the user is not visible in the directory. Because of this, the attendant user was not able to pick up the call from a call center. Now when the privacy setting is set for an attendant user, he/she can pick-up the call from a call center. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-340e57311adedec34d3a06c8260ee882fb65b435%2Fe28c5629d5c510ac.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/e28c5629d5c510ac.png) [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-fa87b3665915e49b1db947b3cc7b8d25218a5905%2Ff4f518eac78187c7.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/f4f518eac78187c7.png) ### 115339: Mail is now sent from the user email address Improved email sending accuracy: Emails will now be sent from the correct sender as specified in the configuration. Enhanced testing capabilities: Administrators can now effectively test email functionality for all configuration options. {% hint style="info" %} Note Administrators should review their email sender settings in the admin portal to ensure the desired configuration is selected. It is recommended to use the test email feature to verify the correct functionality for both personal and default sender options. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-6dee24a3eaadd57d2f40d4696c929506ee541f11%2F4a255fdf4e713646.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/4a255fdf4e713646.png) {% endhint %} ### 121656: Sort Contacts By Priority Sort Contacts by Priority feature #### Smart Sorting: Contacts are now automatically sorted by relevance when you search. #### Prioritized Results: Search results are organized based on where the search term appears in the contact details. #### How It Works: When you type a keyword in the search box, the system will prioritize and display results in the following order: * First Name * Display Name / Complete Name / Last Name * Company Email * Company Primary Phone / Personal Phone Number * Company Alternate Phone * Mobile Phone * Private Phone Number * Pager * Department / Function * Organization * Building Name * Manager Name * Building Address * Location * ID * Contact Type * Other fields / Contact Notes #### Example: If you search for "John", the results will be displayed in this order: * Contacts with "John" in their first name * Contacts with "John" in their display name, complete name, or last name * Contacts with "John" in their company email ... and so on, following the priority list above. #### Benefits: Faster Access: Find the most relevant contacts quickly and efficiently. Improved Accuracy: The most likely matches appear at the top of your search results. Intuitive Sorting: The priority order is designed to match natural search patterns. ### 114390: Mail callback number Email template content should not change while changing the call number to “none” in email template popup. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-72b3a17c265a05e2fb1230f38d3657a2ef4c638e%2F88293e2ecdda1e9a.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/88293e2ecdda1e9a.png) ### 114614: Switching broadworks account in combination with Entra ID / MS Teams In Teams-BW you are simultaneously logged in with a Teams and a Broadworks account. It is possible to log out of the Broadworks account (calling user) and log in with another one. But there was a bug that the device list of the old user would still be displayed and used for some time. This has been fixed and the devices of the signed in user will now be shown and used right away. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-eb23ab434f4a0884a08fc1135365741427e70ca7%2F0457667655da6663.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/0457667655da6663.png) [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-dadf8567e43bad9680cd997e4433ad5b8cd69929%2F2831930751f0f3f9.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/2831930751f0f3f9.png) ### 90101: Saving personal contacts with long name fails silently #### Issue Resolved: Contact Save Functionality: Fixed a critical bug that prevented contacts with names exceeding 50 characters from being saved in the application. #### Problem Details: When users attempted to save a contact with more than 50 characters, the application displayed a message stating, "Your contact has been saved," despite the contact not being saved. This misleading message caused confusion, as users believed their entries were successfully recorded when, in fact, they were not. #### Resolution: Error Notification: The application now correctly identifies when a contact name exceeds the 50-character limit and displays an appropriate error message. Users will receive clear feedback indicating that the contact could not be saved due to character limitations, prompting them to modify their input accordingly. #### Impact: Enhanced user experience: Users will no longer be misled by incorrect success messages and will receive immediate feedback on input errors. Improved data integrity: Ensures that only valid contact entries are saved in the system, maintaining the quality of the contact database. #### User Action Required: Users should ensure that contact names do not exceed 50 characters when entering new contacts. If an error message is displayed, please adjust the contact name to meet the character limit before attempting to save again. #### Additional Notes: This fix improves the reliability of the contact management feature within the application, fostering better user interactions and data handling. We appreciate your understanding and encourage users to provide feedback on any further issues encountered. [![Release note illustration](https://51746954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwg7Zt6UIr1pbalVgSAbn%2Fuploads%2Fgit-blob-aeb77fdcaec4cabea98bbaeeb4485f7678ec937f%2F6fc65e569de1372f.png?alt=media)](https://github.com/AnywhereNow/atlas-docs/tree/main/release-notes/.gitbook/assets/6fc65e569de1372f.png) ### 118299: When saving joined queues it must preserve the unchanged settings The system now correctly handles joined queues with various configurations, including those set as outbound calls queues. Unassignment process for all types of joined queues now functions as expected. ### 120587: Customer does not see new users in adressbooks When customers create new contacts in Broadsoft they are now also shown in the receptionist address books and also visible in MS Teams. [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-bw2024.03.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.