Dear customers, we are pleased to announce that we have improved how we store your passwords by switching from bcrypt to Argon2id. This change makes your data resistant to specialized hardware attacks and quantum computing threats.

Why this change?

This update aligns with our roadmap of incremental improvements toward greater information security against contemporary risks.

How does this affect me?

This change will be applied automatically the next time you log in, without the need to change your current password.

If any user associated with your account does not log in within the next 30 days, their password will be automatically changed, and at their next login, they will be prompted to restore access via your corporate email or by requesting a reset from your account administrator.

SSO are not affected by this policy.

---

If you want more information, you can read our blog post or contact us at support@videsk.io.

• Up to 20x more data per download: the limit has been increased from 5,000 to 100,000 records 🎉
• New formats: now, via our REST API, you can request exports in CSV (ideal for Excel) or NDJSON (ideal for bulk integrations), in addition to the standard JSON format.

From our dashboard, you can download more records per month or across multiple months, with a new limit of 100,000 records within the selected date range.

All current integrations continue to function as before. For more information on downloading in CSV and NDJSON formats, please consult our documentation.

If you have any questions, you can contact us at support@videsk.io or your account manager.

What happened before:

• The interface indicated "disconnected" even though it wasn't. In active or queued calls, a brief network flicker would cause the badge to turn red (disconnected), even though the agent remained connected; our server detected this and continued functioning normally. This caused confusion for the agent.

While this issue did not cause operational problems, it could lead to confusion in daily console use, specifically during network outages.

What happens now:

• The console remains green during brief network outages. If the connection drops for less than 1-2 seconds (typical on unstable networks) and recovers automatically, the agent doesn't see any visual change.

This does not affect:

• The agent's status always reflects the server's reality. When hanging up a call and changing to "Available" (or any other status), the change is immediately visible.
• Automatic recovery after reconnection: If the agent disconnects due to a genuine problem and reconnects, their previous status is correctly restored without intervention.

We've updated the format of our recordings to give you a better experience.

What's changing?

Recordings are now delivered in .mp4 (H.264 + AAC) format instead of .webm.

Benefits for you

• Universal playback: your recordings now open directly on any device, browser or player (Windows Media Player, QuickTime on Mac, Smart TVs and mobile devices) with no extra software needed.
• Faster delivery: recordings are processed significantly faster, so they'll be available much sooner after the meeting ends.

• Higher reliability: edge-case issues that previously affected long meetings or sessions with many participants are now resolved.

Things to note

• Recordings created before this update remain in .webm format and will continue to work as usual; only new recordings will be delivered as .mp4.
• File size stays roughly the same: we prioritized compatibility and speed over storage reduction.

If you have any questions, you can contact us at support@videsk.io or your account executive.

Estimados clientes, hemos implementado una notificación sonora para videollamadas agendadas, que permite saber cuándo un cliente ha llegado a la reunión y está en la sala de espera.

El sonido de notificación es el siguiente: https://cdn.videsk.io/ringtones/waiting.mp3

La notificación como sonido no se pausará a menos que ocurran algunas de las siguientes acciones:

1. Cerrar notificación
2. Ingresar a la reunión

Si tienes dudas, puedes contactarnos en support@videsk.io o con tu ejecutiva de cuenta.

Estimados clientes, hemos mejorado los filtros para el historial de llamados y agendamientos. Desde ahora podrás filtrar por:

• Fecha inicio y fin
• Agente
• Segmento o calendario
• Campo de búsqueda global*

* El campo de búsqueda global permite buscar por cualquier valor presente en:

• Comentarios de llamada
• Valores de formularios de cliente
• Valores de formularios de agente

Llamadas

Agendamientos

Dear customers, we would like to announce the new real-time monitoring feature. This will allow supervisors or administrators with granted permissions to monitor video calls by listening and viewing them in real time.

To access this feature, you can follow the steps in our documentation: https://docs.videsk.io/es-dashboard/dashboard-management/account-settings/configuration/live-monitoring

If you have any questions, you can contact us at support@videsk.io or your account manager.

Dear customers, we are implementing an improvement to our video calling components (WebRTC), starting on Wednesday, July 8, 2025.

This may now display a new button in the interface to indicate that the audio or video may be blocked by the browser. Simply clicking it will begin playing correctly.

Previously, our loading indicator may have been displayed when the browser blocked autoplay.

From now on, you'll be able to see the "Click to activate audio and video" button only if necessary, as follows:

Please note that all of our components are automatically translated, so depending on the user's language, the content will be displayed in their respective language.

If you have any questions, please contact us at support@videsk.io or your account manager.

Dear customers, our provider, Google Cloud Platform, is currently experiencing a massive outage across various products globally.

Videsk has not experienced any service interruptions or changes to normal operations. Any changes due to this contingency from our infrastructure provider will be communicated through our status site (https://status.videsk.io).

Response latency from our servers may increase due to the contingency.

Dear customers, we are implementing an improvement to the scheduling system, specifically in the way customers join.

Starting Monday, June 9, you will need to manually accept participants (customers) who want to join a meeting. This will be done using the following mechanism:

You can accept or reject the connection request, giving you control over who joins the meeting.

Please note that this only applies to meetings, not live calls.