> ## 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.

# Channel Conflict Resolution

> Let AI detect when a partner-registered deal overlaps with a direct or another partner's deal, and guide a fair, fast resolution before it becomes a dispute.

export const Headless = ({prompts = []}) => {
  const PromptRow = ({prompt}) => {
    const [copied, setCopied] = useState(false);
    const copy = () => {
      try {
        navigator.clipboard?.writeText(prompt);
      } catch {}
      setCopied(true);
      setTimeout(() => setCopied(false), 1600);
    };
    return <div className="group flex items-center justify-between gap-3 px-4 py-3 transition-colors hover:bg-[#FD90FF]/[0.06]">
        <span className="text-sm leading-relaxed text-zinc-700 dark:text-zinc-200">{prompt}</span>
        <button type="button" onClick={copy} aria-label={copied ? "Copied to clipboard" : "Copy prompt"} className={`shrink-0 rounded-md p-1.5 transition-all hover:bg-[#FD90FF]/10 focus:opacity-100 focus:outline-none ${copied ? "text-[#FD90FF] opacity-100" : "text-zinc-400 opacity-0 group-hover:opacity-100 dark:text-zinc-500"}`}>
          {copied ? <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg> : <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <rect x="9" y="9" width="11" height="11" rx="2" stroke="currentColor" strokeWidth="2" />
              <path d="M5 15V5a2 2 0 0 1 2-2h10" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>}
        </button>
      </div>;
  };
  return <>
      <p>
        Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
        Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
        action written straight back to your CRM source of truth. The portal is one surface, never the only one.
      </p>

      {prompts.length > 0 ? <div className="not-prose my-6 overflow-hidden rounded-2xl border border-zinc-200/80 bg-white shadow-sm dark:border-white/10 dark:bg-white/[0.02]">
          <div className="flex items-center gap-2 border-b border-zinc-200/80 bg-gradient-to-r from-[#FD90FF]/10 via-[#FD90FF]/5 to-transparent px-4 py-2.5 dark:border-white/10">
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4 text-[#FD90FF]" aria-hidden="true">
              <path d="M12 2.5l2 5.5 5.5 2-5.5 2-2 5.5-2-5.5L4.5 10l5.5-2 2-5.5z" fill="currentColor" />
              <path d="M18.5 14l1 2.6 2.6 1-2.6 1-1 2.6-1-2.6-2.6-1 2.6-1 1-2.6z" fill="currentColor" opacity="0.55" />
            </svg>
            <span className="text-xs font-semibold uppercase tracking-wider text-zinc-500 dark:text-zinc-400">
              Try it from your LLM
            </span>
          </div>

          <div className="flex flex-col divide-y divide-zinc-100 dark:divide-white/[0.06]">
            {prompts.map(prompt => <PromptRow key={prompt} prompt={prompt} />)}
          </div>

          <a href="/headless" className="flex items-center justify-between gap-2 border-t border-zinc-200/80 px-4 py-2.5 text-sm font-medium text-zinc-600 no-underline transition-colors hover:text-[#FD90FF] dark:border-white/10 dark:text-zinc-300">
            <span>See the full headless playbook</span>
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M5 12h14M13 6l6 6-6 6" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
          from Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

> Channel conflict kills trust with partners. AI spots overlapping deals the moment they appear and guides a fair resolution, before it turns into a dispute.

## What it does

When a partner registers a deal, Introw's AI checks it against existing direct and partner deals to find overlap on the same account or opportunity. If it detects a likely conflict, it flags it with the context, who is involved, which deal came first, and the relevant rules, and helps your team resolve it quickly and consistently. Instead of conflicts surfacing late in a heated email thread, they are caught at registration and handled by clear rules of engagement.

The AI does the detection and triage; your team stays in control of the decision.

## The problem it solves

* **Conflicts surface too late and damage trust** → AI flags overlap the moment a deal is registered.
* **Resolution is inconsistent and political** → The AI brings the facts and rules to every case.
* **Reps and partners distrust deal registration** → Fair, fast handling makes registration credible.
* **Ops cannot manually police every deal** → AI screens every registration automatically.

## From problem to solution

Instead of discovering a clash when two teams are already working the same account, the conflict is caught at registration with the full context. Your team applies clear rules of engagement and resolves it fast, so partners trust the program and the direct team stays aligned.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  register["Deal registered"] --> catch["Conflict caught at intake"]
  catch --> rules["Rules of engagement"]
  rules --> resolve["Resolved fast"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Catch overlap early" icon="circle-check">
    Flag conflicts at registration, not at close.
  </Card>

  <Card title="Resolve consistently" icon="circle-check">
    Apply the same rules to every case.
  </Card>

  <Card title="Protect partner trust" icon="circle-check">
    Handle conflicts fairly and fast.
  </Card>

  <Card title="Screen at scale" icon="circle-check">
    Check every registration automatically.
  </Card>
</CardGroup>

## Impact

* **AI-native** - the agent screens and triages conflicts while your team decides.
* **CRM-native** - conflicts are detected across the deals already in your CRM, so nothing slips through a separate registration silo.
* **Trust & accuracy** - conflicts are resolved on facts, keeping the channel credible.

## Who it's for

<CardGroup cols={2}>
  <Card title="Chief Revenue Officer" icon="user">
    Keeps direct and partner motions aligned.
  </Card>

  <Card title="Partner Operations" icon="user">
    Enforces conflict rules without manual policing.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Deal & Lead Registration" icon="handshake" href="/features/co-selling/deal-lead-registration">
    Screen every registration for conflict.
  </Card>

  <Card title="Deal Registration" icon="file-signature" href="/features/deal-registration/registration">
    Detect overlap with reseller claims.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"Does this new registration conflict with any direct or partner pipeline?",
"Flag registrations that overlap existing opportunities.",
"Is Globex already being worked by our direct team?",
]}
/>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Endpoints and code.
  </Card>
</CardGroup>
