Release date: October 13, 2026
Release 26.17 makes SightCall Xpert Knowledge easier to trace and more consistent. You can now see what happens to the content your organization contributes, tutorial names match across views, and you have more ways to reach your knowledge. These changes are available for tenants with Xpert Knowledge enabled.
Contribution Tracking
The Knowledge Workspace in VISION Console now has a Contributions tab next to the Library. Admins and Agents who already have access to the Knowledge Workspace can use it to see how Xpert Knowledge processes content after a SightCall Remote Visual Support session or a video upload. User permissions stay the same.
- The default view is My contributions. Admins and Agents can also switch to a view of all contributions in their tenant.
- Each row shows the source (Remote Visual Support or Uploaded content), the meeting title or filename, the contributor, the date of the last update, and the processing status.
- Contributions that are still processing are listed first. All other contributions follow, with the most recently updated at the top.
- New contributions and status changes appear automatically. You don't need to refresh the page.
- The Contributions tab is read-only. You can't edit, approve, delete, or reprocess a contribution from this tab.
| Status | What it means | What you can do |
|---|---|---|
| Processing | Xpert Knowledge is processing the contribution. | Nothing. The status updates automatically. |
| Succeeded | A tutorial was created or updated. | Select the row to open the tutorial's latest version. |
| Not created | No tutorial was created or updated from this contribution. | Select the row to see why. |
| Failed | A technical error stopped processing. | Select the row to see why. |
A contribution can show Not created for any of these reasons:
- There wasn't enough reliable information to create a tutorial.
- The related tutorial has been reviewed or archived.
- The related tutorial has reached its limit of AI-generated versions.
- The recording was too short.
- A transcript couldn't be created.
Not created doesn't always mean the recording had a problem. If the tutorial is reviewed, archived, or at its version limit, its content lifecycle rules prevented the update.
Consistent tutorial labels
The Library, the tutorial page in VISION Console, and the shared tutorial view now all show the same tutorial label for the selected language. The label sits above Contributors, outside the tutorial content. It may update automatically as the tutorial's scope and content change.
- In Release 26.17, users can't edit the label.
- Headings inside older tutorials aren't rewritten.
List & Retrieve Archived Tutorials (API)
Authorized API consumers can now use a dedicated archivedTutorials resource to list and retrieve archived tutorials, view an archived tutorial with its latest version, and restore it.
| Operation | Purpose |
|---|---|
GET /api/v3/archivedTutorials |
List archived tutorials, with pagination, sorting, and search. |
GET /api/v3/archivedTutorials/{id} |
Retrieve one archived tutorial, optionally with its latest version. |
PATCH /api/v3/archivedTutorials/{id} |
Restore an archived tutorial by setting isArchived: false. You can't update any other attribute this way. |
GET /api/v3/tutorialVersions/{id} |
Retrieve a version that belongs to an archived tutorial. |
Good to know
- The standard tutorials list (
GET /api/v3/tutorials) hasn't changed and still returns active tutorials only. - VISION Console doesn't have a way to browse archived tutorials in this release.
- Xpert Knowledge MCP — AI Agent Access still excludes archived tutorials.
- The
archivedTutorialsresource doesn't support pinning, permanent deletion, or on-demand translation.
Microsoft Dynamics 365 — Xpert Knowledge Workspace Access
Agents using the Classic Microsoft Dynamics integration now have a Knowledge Library button that opens the Knowledge Workspace. It works outside an active call too.
- The user must have access to Xpert Knowledge.
- If the user is already signed in to SightCall, that session is reused where supported. Otherwise, the user goes through the standard sign-in.
- Existing Dynamics calling and sign-in workflows haven't changed.
- This update applies only to the Classic Microsoft Dynamics integration. The separate VISION-based Microsoft Dynamics integration isn't affected.