> ## 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.
# Partners
> Auto-detect, organize, and progress partners with your CRM as the single source of truth - management, journeys, tiers, and segments in one place.
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 ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Partners is where your program lives: every partner is detected from your CRM, organized into phases, tiers, and segments, and moved through onboarding and activation, all without a second source of truth.
## What this area does
A partner program falls apart when partner data lives in a spreadsheet that drifts from the CRM. Partners keeps your CRM as the system of record and builds the program on top of it. Partners are auto-detected from the companies or records you already manage in HubSpot or Salesforce, kept in sync both ways, and organized with the structure a real program needs: lifecycle phases, tiers, and targeting segments.
From there, you progress partners deliberately. Onboarding and activation are run as repeatable journeys instead of one-off reminders, so a new partner reaches first deal faster and a quiet partner gets caught before the next review, not after. Tiers set the benefits and requirements that motivate partners to grow, and segments decide who sees what across the rest of the product.
Because everything sits on the CRM, the program stays clean: no rogue objects, no duplicate partner lists, and every status change reconciled to the record your revenue team already trusts.
## Why it matters
* **CRM-native** - Partners are detected and synced from HubSpot or Salesforce, so there is one partner list and it is always the CRM's.
* **Low total cost of ownership** - Partner ops configures phases, tiers, journeys, and segments with no-code, never waiting on engineering.
* **Time to value** - Stand up the structure of a real program (phases, tiers, onboarding journeys) in an afternoon, not a quarter.
## How it fits together
Partners are detected, organized, and progressed, all on top of the CRM:
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
detect["Detect from CRM"] --> organize["Organize: phases, tiers, segments"]
organize --> progress["Progress: journeys and onboarding"]
progress --> sync["Synced to CRM"]
```
## Capabilities
Auto-detect partners from your CRM, keep them in sync, and organize the list into lifecycle phases.
Run repeatable onboarding and activation playbooks as task journeys applied to the right partners.
Build tier programs with requirements and benefits, and sync each partner's tier to the CRM.
Group partners into dynamic or static segments that target content, notifications, and more.
Onboard partners progressively, unlocking tabs, assets, and abilities as they qualify.
Assign your team to each partner and let that ownership drive the program.
Reach partners on the events that matter, by email, Slack, or Microsoft Teams.
Give partners clear next steps and show them in the portal.
## Who works in this area
Recruits, onboards, and activates partners and keeps the relationship moving without leaving the CRM.
Configures phases, tiers, journeys, and segments and keeps partner data reconciled to the CRM.
Reads phase, tier, and activation progress as leading indicators of partner-attached pipeline.
## Headless
## All guides
{/* ROLLUP:START - generated content goes here */}
Apply a journey to the right partners, then follow each one through to do, in progress, and done so you can step in before anyone stalls.
Use the tasks section in the experience builder to auto-assign a journey to every partner who gets the experience.
Define your own ordered or flexible set of partner tasks, with each task's assignee, due date, visibility, and auto-complete action set.
Start from a built-in onboarding, activation, or certification journey, then tailor the tasks, order, assignees, and auto-complete actions to your program.
Choose which partner notifications go out by email, scope them to the right partners, and turn on reply-by-email so partners respond from their inbox.
Enable the right partner notifications on Chat so Introw posts them to each partner's mapped Microsoft Teams channel, and scope who receives them.
Enable the right partner notifications on Chat so Introw posts them to each partner's mapped Slack channel, and scope who receives them.
Set up the Sleeping deal notification so partners are automatically reminded when a deal sits too long in a stage, keeping your pipeline moving.
Work through the usual causes when a partner says they did not get an email or invite: the address, the notification setting, spam and domain filtering, then resend.
Plan onboarding stages, create a dynamic segment per stage, gate portal tabs, sections, and abilities to those segments, and let journeys move partners forward so the portal unlocks as partners qualify.
Change tier, commission plan, currency, team roles, or the published experience for many partners at once.
Add a single partner by hand, linked to its CRM company, before sync detects it.
Understand how Introw builds and keeps your partner list from CRM records, and where to run the connect-and-detect setup.
Build views, columns, filters, and lifecycle phases so each team reads the partners list the way they need to, then act on partners in bulk.
Open a partner, set every field that drives their experience, keep their contacts current, and capture the context your team needs.
Build an audience that updates itself from filters, then set its permissions and notifications so the whole segment behaves the way you want.
Hand-pick a fixed list of partners and contacts, then set its permissions and notifications so the exact group behaves the way you want.
Start every partner in a restricted default segment, then let more specific segments grant more; when a contact is in several segments, the most permissive setting wins.
Create a one-off task on a partner with the right owner, due date, visibility, and auto-complete action, then surface it in the partner portal.
Assign your team to a partner with the right roles, then wire that ownership through the portal points of contact, communication sender, certificate issuer, and form approval routing.
Set a partner's tier on their detail page, or update a whole cohort at once with bulk edit, and have it flow to your CRM when tier sync is on.
Create a tier program, add ordered tiers with their name, color, badge, and description, and fill each tier's requirements and benefits with text, checkbox, and goal items.