> ## 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.
# Multi-lingual
> Run one partner program in every language your partners speak - portal content, courses, forms, and emails translate automatically and stay on brand.
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 engage when the program speaks their language. Multi-lingual translates your partner-facing content automatically, so every partner reads, learns, and acts in the language they think in, without you running a separate program per region.
## What it does
Multi-lingual lets you add the languages your partners speak and pick a default. Once a language is
active, partner-facing content translates into it automatically: portal experiences and stages,
courses and modules, forms, announcements, certificates, reports, tiers, and the emails partners
receive. Partners choose their language in the portal, or you set it for them, and every surface
follows.
Translations are generated for you and kept consistent with a brand glossary, so product names and
key terms are never mistranslated. You stay in control of which languages exist and how your brand
reads in each one, without copy-pasting content into a translation tool.
## The problem it solves
A single-language program quietly caps adoption everywhere outside your headquarters:
* **Partners disengage when content is not in their language** → Content translates automatically into each partner's language.
* **Translating a growing content library by hand is impossible** → Translations are generated and kept in sync as content changes.
* **Brand and product terms get mistranslated** → A glossary protects terms across every language.
* **Running a separate program per region adds headcount** → One program serves every language without duplicating it.
## From problem to solution
Add a language once and your existing content, and everything you publish after, becomes available in
it. Partners self-serve in their own language across the portal and their inbox, and your team
maintains one program instead of one per region.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
add["Add a language"] --> translate["Content translated automatically"]
translate --> serve["Partner self-serves in their language"]
```
## Use cases
Serve partner content in every language.
Deliver courses partners actually finish.
Keep product terms consistent everywhere.
Run one program, not one per market.
## Impact
* **Partner self-serve** - Partners read and learn without waiting for a localized version.
* **Work where you already are** - Emails partners receive arrive in their language too.
## Who it's for
Localizes content and keeps it on brand.
Works in their own language end to end.
## Works with
{/* CONNECTS:START - generated content goes here */}
Serve the portal in each language.
Translate course content.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.