> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/leads-deals/channel-conflicts/detect-channel-conflicts-deals.md).

# How to detect channel conflicts on deals?

When Partner registers deals, make sure there are no Channel Conflicts with other partners or your direct sales team.\
Otherwise, you might lose your partner's trust.

To avoid this kind of issue, use automatic Channel Conflict Detection in Kiflo.

Channel Conflicts can be detected within:

* Kiflo
* [An external source like your CRM](#detect-channel-conflicts-within-your-crm)

{% embed url="<https://www.loom.com/share/4b1d3664482d4269a7b4fb785a6cf8e6>" %}

## Enable Channel Conflict Detection

To enable Channel Conflict Detection on Deals:

* Go on your **Account** **settings**
* Click on **Deals**
* Check the option "**Enable channel conflict detection**"
* Click **Save**

![](https://3041514930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKkJn82Qo5a0Y4fOsoQzo%2Fuploads%2Fgit-blob-0288222bba3a83d6addfbff49f0b2e27f509126f%2F60c1cccfa6d12c2cd643e6ce.png?alt=media)

## Detect Channel Conflicts within Kiflo

Now that you have enabled Channel Conflict Detection, Kiflo will start watching for Channel Conflicts based on existing Deals, Leads, and Customers.

{% hint style="info" %}
**How does it work?**

To detect Channel Conflicts, we use the client email domain and search for existing:

* Deals that have a client on the same domain.
* Leads that have an email on the same domain.
* Customers that have an email on the same domain.
  {% endhint %}

## Detect Channel Conflicts within your CRM <a href="#detect-channel-conflicts-within-your-crm" id="detect-channel-conflicts-within-your-crm"></a>

To detect Channel Conflict within your CRM, you can use [Zapier](https://zapier.com/apps/kiflo-prm/integrations) and the "Create Channel Conflict" action.

Have a look at this [Zap Template](https://zapier.com/shared/91934ca07c1c36d96c83b2a8b2765212c642a293) to get an example.\
This Zap Template detects Channel Conflicts in HubSpot on Leads and can easily be updated to fit your business need.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-vnext.kiflo.com/leads-deals/channel-conflicts/detect-channel-conflicts-deals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.