---
title: "January 26 - 30, 2026"
slug: "january-26-30-2026"
updated: 2026-01-29T13:03:08Z
published: 2026-01-29T13:03:08Z
canonical: "docs.voiso.com/january-26-30-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.

# January 26 - 30, 2026

## New in this release

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

### CRM integration

#### Bitrix24 call logging and screen pops

Calls made using the [Bitrix24](/v1/docs/crm-bitrix24) integration are now logged in the Bitrix24 call history. Call outcome logging and call details are automatically transmitted to the Bitrix24 database after a call and are available from the Call Details table.

When an agent handles a call in {{variable.BrandName}}, 
the contact record is automatically displayed in Bitrix24.

:::(Internal) (Private notes)
### Omnichannel Workspace

#### Support for mobile browsers

[Omnichannel Workspace](/v1/docs/using-omnichannel-workspace#using-omnichannel-workspace-on-a-mobile-device) now supports a mobile responsive experience in Chrome on Android and iOS, to enable deskless agents to handle digital conversations on a smart phone.

Inbox and chat views are optimized for smaller screens. Agents can read, reply, and manage multiple digital interactions without horizontal scrolling. Agents can start new conversations and continue working across the same channels they use on desktop.

Voice calling is available through **Agent Panel**, opened from the **Main menu** drawer or by tapping the voice call banner shown in **Inbox** during an incoming or active call.

Agents can switch between **Inbox** and **Agent Panel** at any time, keep working on digital interactions, and accept calls from either the call banner or **Agent Panel**.

:::

### Do Not Call Registry

#### Support for Zen DNCR services

For contact centers operating in the UAE, {{variable.BrandName}} supports an API integration with the Zen service to verify outbound UAE numbers against the [Do Not Call Registry](/v1/docs/do-not-call-registry) in real time. This integration applies only to UAE numbers (+971). All outbound call types are supported, including agent dialed calls, click-to-call calls, and Dialer campaigns.

#### DNCR End reasons

The following [End reasons](/v1/docs/end-reasons) are now included in [Call Detail Records](/v1/docs/reporting-cdr) to support calls that ended when their numbers were on the [Do Not Call Registry](/v1/docs/do-not-call-registry):

* **DNCR failure** —  {{variable.BrandName}} cannot complete the DNCR verification due to an API accessibility issue or error, so {{variable.BrandName}} blocks the call under the fail closed behavior (Disposition: Failed).
* **DNCR rejected** — When a Do Not Call Registry check completes successfully and returns that the outbound number is on the restricted list, {{variable.BrandName}} blocks the call (Disposition: Failed).

### Numbers

#### Minimum service terms numbers

Minimum service term tracking is now available for certain numbers on the **Buy Numbers** page. When access to these numbers is enabled for your contact center, numbers with a minimum service term are clearly labeled during browsing, checkout, and on the **[Numbers](/v1/docs/inbound-inbound-numbers)** page, including remaining months. If a number is returned before the term ends, {{variable.BrandName}} calculates and charges the early return fee immediately, and the charge appears in your billing transaction history with a clear description.

## Improvements

### UX and UI improvements

#### Improved Flow creation

A new indicator is added to the **[Flows](/v1/docs/inbound-flows)** page to help you identify which flows have not yet been fully configured. If **[Flow Builder](/v1/docs/inbound-flow-builder-overview)** has not been used to create and save an interaction routing, the status of the flow will be **Not configured**. After you create an interaction flow using **Flow Builder**, the status of the flow will be changed to **Configured** and the flow can accept and route interactions.

:::(Error) (Important)
There is currently no automated logic testing of your interaction flows. {{variable.BrandName}} recommends that you test all of your interaction flows manually before putting them into production.
:::