> ## 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.
# Journeys
> Run onboarding and activation as repeatable task journeys applied to the right partners - so new partners reach first deal faster and quiet ones get caught early.
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.
}
;
};
> Journeys turn onboarding and activation from a memory exercise into a repeatable playbook: a defined set of tasks, applied to the right partners, tracked to completion.
## What it does
A journey is a reusable set of tasks you apply to partners, the playbook for a stage
of the relationship. Introw ships with starting points for the moments that matter
most: partner onboarding, partner activation, and certification. You can use one as
is, adapt it, or build your own from scratch, choosing whether tasks must be done in
order or can be completed in any sequence.
Once a journey exists, you apply it to the partners who need it and watch them move
through it. Each partner's progress is visible across to do, in progress, and done,
so a partner manager can see who is stalling and step in before a new partner goes
cold or an existing one quietly disengages. Because reminders and updates reach
partners where they already work, the playbook keeps running even when no one is
logged into a portal.
## The problem it solves
Onboarding and activation usually live in someone's head and a pile of reminders:
* **New partners take too long to reach their first deal** → A repeatable onboarding journey gives every new partner the same fast, guided path to productive.
* **Quiet partners go unnoticed until a review** → Activation journeys make stalled progress visible early, so partner managers catch silent failure before it shows up in the numbers.
* **Onboarding depends on one person remembering the steps** → The journey is the process, applied consistently to every partner, so quality does not depend on who runs it.
* **No clear view of who is stuck** → To do, in progress, and done buckets show exactly where each partner is, so follow-up goes where it is needed.
## From problem to solution
Journeys make the partner lifecycle a process you run, not a set of tasks you
remember. Partner ops designs the playbook once, partner managers apply it to the
right partners, and everyone sees progress in one place. New partners get to first
deal on a shorter, more consistent path, and the partners who stall surface early
enough to do something about it.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
design["Design the playbook"] --> apply["Apply to the right partners"]
apply --> progress["Track progress in one place"]
```
## Use cases
Apply an onboarding journey so every new partner follows the same guided path.
Run an activation playbook and catch partners who stall before a review would.
Use a certification journey to walk partners through getting trained and certified.
Make onboarding consistent across the whole team instead of person by person.
## Impact
* **Time to value** - A repeatable onboarding journey shortens the path from signed to first deal.
* **Low total cost of ownership** - Partner ops builds and changes journeys with no-code, without engineering.
* **Work where you already are** - Task reminders reach partners in their inbox and chat, so the playbook keeps moving.
## Who it's for
Applies journeys to partners and follows their progress to keep relationships moving.
Designs the onboarding and activation playbooks every partner runs.
## Works with
{/* CONNECTS:START - generated content goes here */}
Journeys are built from tasks.
Drive progressive onboarding.
Make a course a journey step.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.