> 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.md).

# Receptionist for Broadworks

Release history for Receptionist for Broadworks. Review exact versions and applicability notes, 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. Published bulletins are retained for partners, with exact release boundaries and their original configuration prerequisites. Historical features are not claims of current availability.
{% endhint %}

These release notes provide an overview of the new features and enhancements for the indicated release of the Receptionist for Broadworks.

They are intended for partners rather than end-users. After a new release, Receptionist for Broadworks users will see a one-time **What’s New** pop up message highlighting the most important functional changes. The What’s new information, relevant to the attendant user, will also be made accessible from the Help menu.

## Editorial Release Families

| Family                                                                                           | Published releases, newest first                                                                                                                                                                                                                                                       |
| ------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [BW2026.01](/release-notes/receptionist-for-broadworks/receptionist-for-broadworks-bw2026.01.md) | [BW2026.01b](https://atlas.anywhere.now/release-notes/pages/EJWL4KNeQCm4fdU9oDl0#bw2026.01b), [BW2026.01a](https://atlas.anywhere.now/release-notes/pages/EJWL4KNeQCm4fdU9oDl0#bw2026.01a), [BW2026.01](https://atlas.anywhere.now/release-notes/pages/EJWL4KNeQCm4fdU9oDl0#bw2026.01) |
| [BW2025.01](/release-notes/receptionist-for-broadworks/receptionist-for-broadworks-bw2025.01.md) | [BW2025.01](https://atlas.anywhere.now/release-notes/pages/e89K5trPF75lgWiSOajg#bw2025.01)                                                                                                                                                                                             |
| [BW2024.03](/release-notes/receptionist-for-broadworks/receptionist-for-broadworks-bw2024.03.md) | [BW2024.03](https://atlas.anywhere.now/release-notes/pages/mZiSO0fTdf9YjexwfQOx#bw2024.03)                                                                                                                                                                                             |


---

# 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.md?ask=<question>&goal=<user_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.