Every page in the main Ender Turing workspace carries a help menu in the main navigation. It is the single place to go when you are stuck, want to check whether a feature exists, or need a person from the Ender Turing team to look at a problem. A few standalone pages that open on their own — such as a shared report export or a direct file download link — have no navigation strip and so no help menu.

Most entries open an external destination in a new browser tab — the public Help Center, the Ender Turing support portal, your email client, or the API documentation. Two entries stay inside the product: See What's New opens a popup with the highlights of the recent releases, and Live chat with Support opens a chat window on top of the page you are already on. Either way, Ender Turing stays open on the page you were using, so you never lose your place.

Opening an entry never changes your data, settings, or configuration, with one small exception: the What's New popup notes in your browser how recent the updates you have already seen are, so that it does not open by itself again. What you can do after you arrive is a different matter — the API documentation can send real requests to your installation, so read API Documentation before you use it.

The main navigation is the narrow icon strip down the left edge of the screen. The help menu is the question-mark-in-a-circle icon in the lower group of icons, beside the notifications and profile icons.

Click the icon and the menu opens to the right. Click any entry to open it; click elsewhere on the page to close the menu without opening anything.

The help menu itself is available to every signed-in user. Agents, reviewers, team leaders, and administrators all see the same icon in the same place, and the first four entries — See What's New, Help Center, Submit a Support ticket, and Contact ET Team — behave identically for everyone.

Two entries are conditional:

There is no read-only or reduced version of the menu — an entry is either present or absent. The one entry that can appear without being usable is API Documentation, because seeing it and opening it are governed by different permissions; see API Documentation below.

See What's New opens a popup titled What's New that summarises the recent Ender Turing releases, without leaving the page you are on. It is available to every signed-in user; no role or permission controls it.

The popup can reach you two ways:

Both routes show exactly the same thing: every release the popup currently carries. Nothing is hidden because you have read it before, so opening it manually is always safe and always shows the full set.

Ender Turing normally publishes updates twice a month, and the popup carries the releases published in roughly the last month — the 31 days before the highlights were collected. In practice that is usually the last two releases. If publishing has paused long enough that nothing falls inside that period, the popup keeps the newest release anyway, so it is never empty for that reason alone. Anything older lives behind See all updates.

Each release is a separate group, headed Release highlights with its own Released date, so you can always tell which update a change belongs to. The newest release comes first.

Within a release group, each change is one compact row showing:

Rows are listed in the order the release notes present them, and the popup carries every structured change in the releases it holds, not a shortened selection.

All rows start collapsed. Click a row to expand it and reveal a bullet list of details and, where one exists, a Learn more button that opens the related documentation in a new browser tab. Only one row can be open at a time across the whole popup — expanding a row in one release group collapses whatever was open in another. Click the open row again to close it. A row with nothing further to show does not expand.

When several releases are shown, the list of releases scrolls inside the popup while the title, See all updates, and the close button stay in view. On a narrow screen, such as a phone, the popup fills the screen instead of floating over the page.

See all updates at the top right opens the complete public Ender Turing changelog in a new browser tab. Use it when you want older releases than the popup holds.

Close it with the × button in its top-right corner or by pressing Escape. Closing changes no data or settings — the only thing recorded is how recent the updates you have now seen are, which is what stops the popup opening by itself again. This applies whether you opened it automatically or from the menu; opening it manually never causes an older release to reappear later.

Two details are worth knowing:

If you opened the popup from the menu, keyboard focus returns to the help icon when it closes.

The popup is available in English, Ukrainian, German, Polish, Russian, Czech, and Spanish. If your interface language is one of those, each release is shown in it when a translation exists for that release, and falls back to English when it does not — so a mixed set is possible, with an older release translated and a very recent one still in English. Every other interface language shows the popup in English. Changing your interface language while the popup is open switches the text immediately.

Two states are worth recognising. While the content is still being fetched you see a short Loading updates… message. If no releases have been loaded — for example, on a freshly built installation, or when the release notes could not be fetched at all since you opened Ender Turing — the popup opens with No updates are available right now. Once releases have loaded, a refresh that fails leaves the popup showing what it already had rather than emptying it; a refresh that succeeds always replaces the content. Neither state means something is broken, and See all updates still works in both cases.

The release highlights are packaged into Ender Turing when the build your organisation runs is produced, rather than fetched live each time you open the popup. What you see is the set of releases that was available to that build, which can already trail the public changelog by a day or more — the highlights are collected periodically, and a build keeps the last set that was collected successfully. A newly published update therefore appears in the popup only after your installation is updated to a build that includes it. This matters most for self-hosted installations, which are updated on their own schedule.

The same applies to the one-month window: it is measured from the moment the highlights were collected, not from the moment you open the popup. On an installation that has not been updated for a while, the releases you see can all be older than a month.

Because of this, the popup is a snapshot of recent announcements rather than a list of what is available in your installation. An announced feature is not necessarily switched on for you — check the documentation for the feature, or ask Support, before relying on it.

The public changelog behind See all updates does not have this delay — it is always current. If you are checking whether a change has been announced at all, that link is the authoritative source.

Start with Help Center. It hosts the full product documentation, and the search bar there is usually faster than describing a problem to a person. Search for the label you see on screen — the article titles use the same wording as the interface.

Use See What's New when something in the product looks different from what you remember, or before you report a change as a bug. The release highlights are the quickest way to confirm whether a behaviour changed on purpose.

When documentation does not resolve the issue, you have three ways to reach a person:

The support team can only work from what you send. A ticket that answers these questions up front usually skips a round of clarifying replies:

API Documentation opens the interactive API reference generated from your own installation, so it always matches the version you are running. You can browse the available endpoints and see the expected request and response shapes for each one.

The page also has a Try it out button on every endpoint, and it is not a sandbox. A request you send from there runs against your live installation, signed in as you and limited only by your own permissions — exactly as if an integration had made the call. The reference lists endpoints that create, change, and delete records, including conversations, users, and integration settings, and there is no confirmation step and no undo. Do not treat the method label as a safety signal either: some endpoints marked GET still store something or start background processing as a side effect of returning their answer. Read each endpoint's own description before you send anything, use Try it out only where you have confirmed what the call does, and do your testing on a test installation rather than a production one.

Two different conditions govern this entry, and they are not the same:

Most administrative roles hold both, so the entry works as expected. But because the conditions differ, a role that has Integrations Configuration without Conversations Base will see the entry and then be refused when the page loads. If that happens to you, it is a permission gap in your role rather than a broken link — ask an administrator to review your role in Roles & Permissions.