Release 26.15 (September 2026) brings four updates to Vision Console, formerly Console V3, for SightCall Remote Visual Support. You'll find clearer date and time attributes in invitation templates and personal date and time display preferences. If you embed Vision Console in your own application, there are also session lifecycle events and a compact layout for narrow windows.
Clearer date and time attributes in invitation templates
Applies to: Classic platform and Vision invitation templates (SMS, email subject and body, WhatsApp). Also covers related file names: media uploads, activity picture names and PDF report names.
Four attributes replace nine older date and time placeholders. Each one takes an explicit format:
| Attribute | Key | Meaning |
|---|---|---|
| Session Start Date | startsAt | When the session starts |
| Session End Date | endsAt | When the session ends |
| Created Date | createdAt | When a resource, such as saved media, was created |
| Current Date | currentDate | The date and time the content is generated |
- Syntax:
${attribute;format=...}. Example:${startsAt;format=DD/MM/YYYY [at] HH:mm}→08/09/2026 at 17:00 - Supported tokens:
YYYY,YY,MM,DD,HH(24-hour),mm,ss,a/A(AM/PM) - Existing templates: Your current date variables were converted to the new format automatically. You don't need to do anything.
- Good to know:
- A template with an invalid format can't be saved.
- The variable picker only shows attributes that make sense where you're working.
- Tooltips now describe what each attribute actually means.
- Time zone options aren't available in this release.
Personal date and time display preferences
In your Vision Console settings, you can choose:
- 12-hour or 24-hour time
- EU (
DD/MM/YYYY) or US (MM/DD/YYYY) dates
These choices don't depend on your app language. They apply as soon as you save.
Limitation: In this release, your preferences are saved only in the browser you're using.
Embedded Integration — Session Lifecycle Events
If your application embeds Vision Console in an iframe or opens it in a new window or tab, it can now be told when a call starts and ends.
- Events:
callStartedandcallEnded - Message format:
type(the event name) anddata(includes a timestamp in milliseconds since epoch) - Where messages go: the parent window when Vision Console is in an iframe, or the opener window when it's in a new window or tab
- What your application should do: listen for browser
messageevents, check the origin, and ignore event types it doesn't recognize
Requirements and limitations:
- Your embedding domain must be allowlisted by SightCall. Contact SightCall to request this. Embedding from a domain that isn't allowlisted is not supported.
- Events only go from Vision Console to your application. Your application can't start or end calls or send other actions to Vision Console.
- This doesn't replace the Classic JavaScript SDK.
Compact layout for narrow embedded windows
When Vision Console is embedded in a narrow space, such as a CRM side panel, it now uses a compact layout. This happens automatically when the window reaches the existing small-width breakpoint. The goal is to keep controls usable without clipped buttons or sideways scrolling.
Where it applies: the landing screen, creating a session, the list of sessions, in-call, the Activities panel, and Session Media Selection for the PDF report.
Good to know:
- Everything works the same as before; only the layout changes.
- Wider windows don't change.
- There's no separate Console just for integrations, and no setting to turn this on manually.