---
title: "April 20-24, 2026"
slug: "april-20-24-2026"
updated: 2026-04-24T15:30:58Z
published: 2026-04-24T15:30:58Z
canonical: "docs.voiso.com/april-20-24-2026"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voiso.com/llms.txt
> Use this file to discover all available pages before exploring further.

# April 20-24, 2026

## New in this release

Refer to the latest [documentation changelog](/v1/docs/changelog) for additional information.

### Inbound

#### Interaction context mapping

The **[Interaction context mapping](/v1/docs/interaction-context-mapping)** feature allows you to map incoming interaction data from supported sources to standardized fields in Voiso. You can map data from SIP headers and Dialer API campaign lead fields (`context_headers`) to custom display fields. These fields are shown to agents in Agent Panel during interactions and are also available in the Extended Call Detail Records.

### API

- The following new **Campaign** endpoints were added:
  - [Add users to a campaign](https://developers.voiso.com/reference/addcampaignusers): assigns users to the specified Dialer campaign.
  - [Remove user from a campaign](https://developers.voiso.com/reference/removecampaignuser): unassigns a user from the specified Dialer campaign.
- [Get List of CDRs](https://developers.voiso.com/reference/getcdrs): Details for filtering by `subtype` and `duration` are added.
- [Get list of CDRs](https://developers.voiso.com/reference/getcdrs) the following new `end_reason` enum parameter values can be used to filter requests for `GET /api/v4/reporting/cdrs`: `dncr_failure` and `dncr_restricted`
- `user.id` and `user_id` are now integers instead of UUID strings:
  - [Get list of users](https://developers.voiso.com/reference/getusers) now returns an integer for the `id` parameter.
  - [Get user](https://developers.voiso.com/reference/getuser) the `GET /api/v4/users/{user_id}` now expects an integer `user_id`.
  - [Get list of deleted users](https://developers.voiso.com/reference/getdeletedusers) now returns an integer for the `id` parameter.
  - [Get deleted user](https://developers.voiso.com/reference/getdeleteduser) the `GET /api/v4/users/deleted/{user_id}` now expects an integer `user_id`.
  - [Start call](https://developers.voiso.com/reference/startcall) the `user_id` parameter of the `POST /api/v4/voice/calls` request is now an integer.
  - [Stop call](https://developers.voiso.com/reference/stopcall) the `user_id` parameter of the `POST /api/v4/voice/calls/{call_id}/hanguprequest` is now an integer.
  - [List scheduled callbacks](https://developers.voiso.com/reference/listscheduledcallbacks) the `user_id` parameter of the `POST /api/v4/tasks/scheduled_callbacks` response is now an integer.
  - [Get list of conversations](https://developers.voiso.com/reference/getconversations) the `user_id` parameter of the `POST /api/v4/messaging/conversations` request is now an integer.
- [Start call](https://developers.voiso.com/reference/startcall) Start call request: `source.name` is renamed to `source.system` in the  

`POST /api/v4/voice/calls` request.
- [Get list of campaigns](https://developers.voiso.com/reference/getcampaigns) The following new filters are added for the `GET /api/v4/campaigns` request:
  - `name`
  - `status`
  - `strategy`
  - `method`
  - `live`

## Improvements

### UX and UI improvements

#### In CRM call recording playback

You can now play call recordings directly in HubSpot, Zoho, and Freshdesk, without switching to the Extended Call Detail Records in Voiso.

When enabled, Voiso adds a recording playback option to each call record or ticket in the following CRMs:

- [Freshdesk](/v1/docs/freshdesk): An audio player is added to the ticket description
- [HubSpot](/v1/docs/crm-hubspot): A native audio player appears in the call engagement
- [Zoho](/v1/docs/zoho-crm): A native audio player appears in the call record