> ## 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.
# Tasks
> Keep co-sold deals moving with tasks on the shared record, so the partner and your rep always know the next step and who owns it.
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.
}
;
};
> Co-sold deals stall when the next step is unclear. Tasks on the shared record keep the partner and your rep aligned on what happens next and who owns it.
## What it does
Tasks let you attach concrete next steps to a shared deal or CRM record during co-selling: send the proposal, schedule the demo, get the security review. Each task has an owner and a due date, and both sides see it on the record they collaborate on. As tasks complete, the deal keeps moving, and notifications keep everyone honest about due dates.
Tasks live alongside comments and collaborators on the shared record, so the next step is never lost in an email thread.
## The problem it solves
* **Co-sold deals stall between partner and rep** → A clear, owned task keeps the deal moving.
* **Next steps get lost in email** → Tasks live on the shared record both sides see.
* **No one knows who owns the follow-up** → Each task has an explicit owner and due date.
* **Slippage goes unnoticed** → Notifications flag tasks that are due or overdue.
## From problem to solution
Instead of a co-sell motion that depends on remembering what was said on the last call, every next step is a task on the shared record. The partner and rep see the same list, own their parts, and get nudged before things slip, so deals close faster.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
nextStep["Next step"] --> task["Task on the shared record"]
task --> assign["Assigned to rep or partner"]
assign --> close["Nudged to close"]
```
## Use cases
Attach an owned task to a shared deal.
Both sides see the same task list.
Due dates and nudges keep tasks on track.
Tasks live with comments and collaborators.
## Impact
* **Work where you already are** - tasks travel with the shared record, including in the CRM.
* **CRM-native** - the next step lives on the deal both sides trust.
## Who it's for
Keeps co-sold deals moving with clear next steps.
Knows exactly what to do next on a shared deal.
## Works with
{/* CONNECTS:START - generated content goes here */}
Tasks live on the shared record.
Same task model as the partner lifecycle.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Endpoints and code.