---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/conversational-interfaces

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Domain separation and Omnichannel Callback

# Domain separation and Omnichannel Callback {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Domain separation is supported for Omnichannel Callback. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

## Support level: Standard {#omnichannel-callback-domain-separation__section_dzg_mlx_nxb}

* Includes all aspects of Basic level support.
* Application properties are domain-aware as needed.
* Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
* The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.
{#omnichannel-callback-domain-separation__ul_tfh_drj_xkb}

Sample use case: An admin must be able to make comments required when a record closes for
one tenant, but not for another.{#omnichannel-callback-domain-separation__p_ssc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#omnichannel-callback-domain-separation__p_tsc_nfg_h1c}

## Overview {#omnichannel-callback-domain-separation__section_cq3_tmv_kxb}

Domain separation enables you to partition your organization's data and administrative control into separate domains. This lets you isolate data and control access to it, which is particularly important in environments where
multiple tenants share a common platform.

## How domain separation works in Omnichannel Callback {#omnichannel-callback-domain-separation__section_dq3_tmv_kxb}

Domain separation in Omnichannel Callback works by routing callback requests to domain-specific available agents.  
When using domain separation for Omnichannel Callback, keep the following points in mind.

* Domain separation applies to both the agent and the customer requesting for a callback. This means that agents will only be able to access interactions records that are created under the domain of the user requesting the callback.
* The agent should be in the same domain as the user to receive a callback request in the workspace.
* No configuration is required for domain separation for Omnichannel Callback.
{#omnichannel-callback-domain-separation__ul_tl3_q4x_nxb}

## Domain separated tables {#omnichannel-callback-domain-separation__section_wdb_w4x_nxb}

The sys_cs_callback table is domain separated.

## Use cases {#omnichannel-callback-domain-separation__section_eq3_tmv_kxb}

When domain separation is used, a callback request from guest users is routed to the agent with the same domain as the guest user. For custom chat channels, the domain of the provider application is used as a reference to route the
callback to the domain-specific agent.
**Zugehörige Informationen**   

* [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)