> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Catch and resolve channel conflict
> Turn on AI channel-conflict screening for a deal form, then review and resolve any overlap from the Submissions inbox before it syncs to your CRM.
Channel conflict is configured on the form that creates the deal, not in a global settings screen. When you turn on Channel Conflict Analysis for a deal-creating form, every submission is cross-referenced against the deals already in your CRM, and any likely overlap is held in the Submissions inbox with an AI assessment so your team can decide before the deal syncs. This is what keeps a partner deal and a direct (or another partner's) deal from quietly colliding and turning into a dispute weeks later.
## What you'll achieve
A deal-registration or lead form that automatically screens each submission for channel conflict, plus a clear review flow: flagged submissions wait in the Submissions inbox with the overlapping deals and a recommended next step, and your team approves, declines, or links the deal before any CRM record is created. Detection runs automatically; the decision stays with your team.
## Before you start
Channel conflict analysis only runs on forms whose automations create a Deal (or Lead / Opportunity). Build or open the form partners use to register or submit deals first.
Detection compares each submission against the deals synced from your CRM, so a connected CRM with your deals is required.
You need permission to edit forms, and reviewers need submission access to approve or decline a flagged conflict.
## Watch it
## Steps
### Turn on detection for the form
Go to [Forms](https://app.introw.io/forms), open the form partners use to register deals, and switch to the **Automations** tab. The left column lists every automation that can run on a submission.
Confirm the form has a deal-creating automation (a **Deal**, **Lead**, or **Opportunity** automation). Channel conflict analysis only screens submissions that produce a deal, so without one there is nothing to cross-reference. Adding a **Create partner** automation turns channel conflict off, so keep that off on deal forms.
Select **Channel Conflict Analysis** from the automation list. If it shows a **Disabled** pill, it is not yet screening submissions.
* **Channel Conflict Analysis** - the on/off switch for AI screening on this form. When on, every submission is checked for overlapping deals before the form's CRM automations run. Turn it on.
* **Object** - the CRM object the analysis runs against. This is fixed to your **Deal** object and cannot be changed, because conflict only makes sense against deals.
* **Filters** - optionally limit screening to deals that match these conditions (for example only above a certain amount, or only a specific pipeline). Leave it empty to screen every deal the form creates; add conditions when you only want larger or specific deals reviewed.
* **Additional context** - free text that helps the agent judge what counts as a conflict for your program (for example how you treat existing open opportunities, or which regions overlap). Describe your rules of engagement here so the assessment matches how your team actually decides.
Save the form so the automation goes live. New submissions to this form are now screened for conflict.
### Resolve a flagged conflict
Go to [Submissions](https://app.introw.io/submissions). A submission with detected overlap is held as pending and shows a channel conflict flag on its status.
Open the submission to see the deal it would create alongside the overlapping deals the AI found, plus its assessment and recommended next step. This assessment is internal only, partners never see it.
Using the AI panel, apply your rules of engagement:
* **Approve** to let the submission proceed and create or update the deal in your CRM.
* **Decline** to reject the overlapping registration.
* **Link to an existing deal** when the right move is to attach the submission to the deal that is already in flight rather than create a duplicate.
The decision is recorded on the submission, and only then do the form's CRM automations run.
## Verify it worked
Submit a test deal that overlaps a deal already in your CRM. The submission lands in the Submissions inbox as pending with a channel conflict flag, the AI assessment lists the overlapping deal and a recommended next step, and approving or declining it records the outcome before any CRM record is created. A submission with no overlap passes straight through.
## Related
Settings, prerequisites, and limits for channel conflict analysis.
The registration flow that feeds these submissions.