> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/connect-telephony/direct-routing/interceptor.md).

# Interceptor

Understand where Interceptor fits in a Dialogue Cloud Neo (Connect) Direct Routing deployment.

Interceptor is used with Dialogue Cloud Neo (Connect) deployments that use Microsoft Direct Routing. It supports call-flow designs where direct calls to or from agents are routed through Dialogue Cloud before they continue to the intended Microsoft Teams or PSTN destination.

Use this section when a customer design includes Interceptor for direct inbound or direct outbound agent call paths. Do not treat Interceptor as a replacement for the Direct Routing, SBC, endpoint, and LineURI configuration that makes the Connect model work.

{% hint style="info" %}
**Connect model only.** Interceptor guidance in this section applies to Dialogue Cloud Neo (Connect) deployments that use Microsoft Direct Routing.
{% endhint %}

## What Interceptor does

In a Direct Routing deployment, the customer Session Border Controller (SBC) decides whether a call continues on the regular Microsoft Teams or Internet Telephony Service Provider (ITSP) route, or whether the call is sent to Dialogue Cloud.

Interceptor is involved in direct agent call paths where the design requires Dialogue Cloud to handle the call first:

* **Inbound interception**: a direct call to an agent number is routed to Dialogue Cloud before it is returned to the intended agent.
* **Outbound interception**: a direct call from an agent number is routed to Dialogue Cloud before it continues to the external destination.

For the detailed call-flow patterns that are currently documented for Direct Routing, see [Interception behavior](/connect-telephony/direct-routing/interceptor/interception-behavior.md).

## Before you configure Interceptor

Before you request or configure Interceptor for a customer environment, confirm the following:

* The customer uses Dialogue Cloud Neo (Connect) with Microsoft Direct Routing.
* The Direct Routing SBC and endpoint configuration is already designed for the affected agent numbers.
* The relevant Contact Center (UCC) and Service are known.
* The customer scenario is approved for Interceptor in the deployment design.
* The change owner, validation plan, and affected pilot or production numbers are agreed with the SBC and contact-center owners.

{% hint style="warning" %}
Before changing Interceptor settings for live numbers, coordinate the routing change with the SBC and contact-center owners. Validate the affected inbound and outbound call paths with pilot or test numbers before production.
{% endhint %}

## What this section covers

This Interceptor section contains:

* [Configure Interceptor](/connect-telephony/direct-routing/interceptor/configure-interceptor.md): the Interceptor settings reference, recording-impact notes, and validation workflow.
* [Interception behavior](/connect-telephony/direct-routing/interceptor/interception-behavior.md): the supported high-level inbound and outbound Direct Routing call-flow patterns, including a simplified behavior table.

Configuration details for recording storage remain in the call-recording documentation. For the recording configuration area, see [Manage Dialogue Cloud call recordings](/operate/recording-and-interaction-data/manage-call-recordings.md).

## Related Direct Routing topics

Use the Interceptor pages together with the Connect model Direct Routing documentation:

{% content-ref url="/pages/P2EMkmV52Ncf5FcJC6rT" %}
[Connect model: Direct Routing](/connect-telephony/direct-routing.md)
{% endcontent-ref %}

{% content-ref url="/pages/UT3mufCpNN5vI89hGEM2" %}
[Routing scenarios and testing](/connect-telephony/direct-routing/direct-routing-routing-scenarios-and-testing.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/connect-telephony/direct-routing/interceptor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.