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

# Deal Registration

> Let resellers register and protect the deals they own - a fast registration that checks for channel conflict, routes through your approvals, and locks in the partner's margin as a real CRM deal.

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>}
    </>;
};

> When a partner owns the sale, deal registration is how they protect the investment they are about to make in an opportunity. Resellers register, Introw checks for conflict and applies your approvals, and the deal becomes attributed CRM pipeline that no one else can claim.

## What it does

Deal registration lets a reseller claim an opportunity before they invest in working it. The
reseller submits a registration, Introw checks it against existing pipeline for channel
conflict, and it routes through the approval steps you define before becoming a deal in your
CRM. A clean, conflict-free registration can flow straight through, while the ones that need a
human get reviewed.

Because the registered deal lands in HubSpot or Salesforce attributed to the reseller, the
partner's margin and ownership are protected from your direct team and from other partners.
Resellers register from the portal or off-portal, and your team works from the CRM.

## The problem it solves

Resellers will not invest in a deal they might lose:

* **Partners fear the direct team or a peer will take their deal** → Registration with conflict checks locks in their claim before they invest.
* **Registering is too slow to bother with** → Resellers register in seconds from the portal or off-portal. Using Slack, Teams, Claude or Email.
* **Approvals are inconsistent and opaque** → Configurable approval steps, with optional AI validation, make decisions fast and fair.
* **Registered deals never reconcile in the CRM** → Accepted registrations become attributed CRM deals automatically.

## From problem to solution

Registration turns a reseller's intent into protected, attributed CRM pipeline. Resellers claim
deals with confidence, your conflict and approval rules keep the channel fair, and partner-owned
pipeline stays clean and defensible.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  submit["Reseller registers"] --> conflict["Conflict check"]
  conflict --> approval["Your approval rules"]
  approval --> attributed["Attributed CRM deal"]
  attributed --> protected["Protected margin"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Claim a deal before investing" icon="circle-check">
    Let resellers lock in an opportunity up front.
  </Card>

  <Card title="Catch conflict early" icon="circle-check">
    Check registrations against existing pipeline.
  </Card>

  <Card title="Approve with rules" icon="circle-check">
    Route registrations through the approvers you choose.
  </Card>

  <Card title="Protect partner margin" icon="circle-check">
    Attribute the deal so the reseller keeps the credit.
  </Card>
</CardGroup>

## Impact

* **Trust & accuracy** - Conflict checks and clean attribution protect the reseller's deal.
* **CRM-native** - Registered deals are real CRM records from the start.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Manager (CAM / PAM)" icon="user">
    Sets the registration and approval rules that protect resellers.
  </Card>

  <Card title="Partner - Sales (Reseller)" icon="user">
    Registers and protects the deals they will close.
  </Card>
</CardGroup>

## Works with

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

<CardGroup cols={2}>
  <Card title="Channel Conflict Resolution" icon="robot" href="/features/ai/channel-conflict">
    Each claim is screened for conflict.
  </Card>

  <Card title="Submissions & Approvals" icon="table-list" href="/features/forms/submissions-approvals">
    Claims run through approval.
  </Card>

  <Card title="Shared Pipeline" icon="file-signature" href="/features/deal-registration/shared-pipeline">
    Resellers work the deals they register on a shared pipeline.
  </Card>

  <Card title="Multi-tier Attribution" icon="file-signature" href="/features/deal-registration/multi-tier">
    Share credit across the channel.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"Register a new deal with Globex worth €80k, closing next month.",
"Which registrations are pending, and which overlap our direct pipeline?",
"Accept Acme's registration and link it to the existing HubSpot deal.",
]}
/>

## 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">
    Integration surface and code.
  </Card>
</CardGroup>
