October 2026 Release
The October 2026 release is a voice upgrade for Pulse: voice calls now run on the Console realtime voice engine, with an updated session flow and agent endpoint behind the voice experience. This release requires an upgrade migration and post-upgrade validation for voice call behavior.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- Voice calls now use the Console realtime voice engine. Pulse voice calls now follow the new realtime engine path, with an updated session flow and agent endpoint behind the experience.
New in Pulse
Voice calls now run on the Console realtime voice engine
Pulse now routes voice calls through the Console realtime voice engine. Behind the voice experience, the session flow and agent endpoint have changed, so voice call behavior after upgrade follows the new realtime engine path.
For organization admins
- Treat this release as a migration upgrade, not only an image update.
- Run the database migration before starting the new version.
- After upgrade, verify any operational procedures or integrations that depend on Pulse voice calls against the new realtime voice session flow and agent endpoint.
For developers
If you maintain custom voice call integrations or operational tooling around Pulse voice, validate them after upgrade against the new realtime engine path, updated session flow, and agent endpoint.
What to try
- Run the upgrade migration before starting the new version.
- Place a Pulse voice call after upgrade and confirm the call completes as expected on the new realtime engine path.
- If your team depends on voice-related integrations or runbooks, verify them against the updated session flow and agent endpoint.
Action required
Before starting the new version, run the database migration for this release. After upgrade, validate voice call behavior and any dependent integrations or operational procedures against the new realtime voice session flow and agent endpoint.