> ## Documentation Index
> Fetch the complete documentation index at: https://relevanceai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Customer Success
> Put AI Agents to work across the post-sale journey — health, renewals, expansion — so CSMs spend time on the accounts that need them.
CSMs are stretched across too many accounts. AI Agents take the watchful work — tracking signals, prepping QBRs, surfacing renewal risks — so CSMs focus on the conversations that actually move retention and expansion.
## Start with a Marketplace template
The Marketplace ships pre-built Agents you can clone in one click. Adapt them to your segments, your renewal cadence, your playbook. Or [build a custom Agent from scratch](/build/introduction).
In-depth research on an account, producing a structured report — useful before QBRs and renewal conversations.
Researches an account and writes the plan back to your CRM — handy for expansion across the book.
The full catalog of Agents — health scoring, renewals, QBR prep, customer comms.
Click **Clone Agent** on any listing, connect the systems it needs (CRM, support, product analytics), and run it on a real account.
## Pick your path
How hands-on do you want to be? Pick a tab — the rest of the page is written for you.
You don't need to touch the builder. Open the cloned Agent above, ask in plain English, and let it work across the systems it's connected to.
## Sharpen the answers with knowledge
Upload your CS playbooks, segmentation rules, renewal use case docs, and product positioning. Every conversation references them — sharper output, no new setup.
Upload context once. Every conversation references it.
## Make it run on its own
When you find yourself summarizing the same account state every Monday, set a trigger — every CSM gets a weekly book-of-business digest, every at-risk account auto-flags. One toggle, no code, no builder.
Schedule runs, fire on CRM events, listen to webhooks.
## Ready to go further?
When prompting and templates stop being enough — when you want the Agent to follow your team's playbook word for word and orchestrate cross-system signal monitoring — pick the **Build visually** tab above.
You're comfortable in product UIs. You don't want to wire up an Agent from scratch, but you do want it to follow your CS playbook account by account. Open the cloned Agent in the builder and shape every piece.
## Connect the tools it needs
CS Agents work best when they can read from and write to the systems your team already uses.
* **CRM** — [HubSpot](/integrations/popular-integrations/hubspot) or [Salesforce](/integrations/popular-integrations/salesforce) for account data, deal stage, and renewal timing
* **Support** — [Zendesk](/integrations/popular-integrations/zendesk) or Intercom for ticket activity and CSAT
* **Product analytics** — your usage data source for engagement signals
* **Comms** — [Gmail](/integrations/popular-integrations/gmail), [Slack](/integrations/popular-integrations/slack) for outreach and internal alerts
See more about [Integrations](/integrations/introduction).
## Shape every surface
Each piece below changes how the Agent behaves. Run it on a real account between every change — small iterations beat big rewrites.
Edit the system prompt to match your segmentation, escalation rules, and renewal use case.
Add or remove the actions the Agent can take — pull usage data, query support tickets, draft renewal emails.
Upload your CS playbook, customer journey docs, segmentation rules. The Agent draws on these whenever it works.
Run the Agent automatically — on a schedule, when usage drops, when a renewal date approaches.
Get notified when an account crosses a health threshold or when a renewal slips.
Persistent context per account — last interactions, prior escalations, what worked at renewal time.
## Chain Agents into a workforce
When a single Agent isn't enough — score health, then draft outreach, then schedule, then log to the CRM — wire them together on the Workforce canvas.
Drag, connect, and run multi-Agent pipelines without code.
## Test before you trust
Set up evals so health scoring or QBR-prep regressions get caught before they reach the CSM.
Define test cases in the UI. Run them on every change.
## Ready to go further?
When clicking through the builder starts to feel slow — when you'd rather have your AI coding assistant build and edit Agents for you, drop into custom Python or JS code blocks, or call Agents from your own app via the SDK — pick the **Build with AI** tab above.
You already work in an AI coding environment. Clicking through a UI to edit health-scoring rules feels slow. Have your AI assistant build, shape, and orchestrate Agents directly from your editor.
## MCP & Plugins
Connect your AI coding environment to Relevance AI over MCP. Describe what you want in natural language; your AI assistant reads and writes your Relevance workspace — system prompts, Tools, knowledge, triggers, workforces, evals.
The fastest setup. Install the Relevance AI plugin and build Agents from your terminal.
Connect from Claude Desktop, Cursor, VS Code, ChatGPT, OpenAI Codex, or any MCP client.
Clone the skills repo so your coding assistant has built-in knowledge of Relevance patterns.
The full reference for what you can do programmatically.
## The four levels in customer success
How the [autonomy ladder](/guides) plays out across your book of business:
A CSM asks the Agent to summarize Acme's last quarter before a check-in — the Agent returns a snapshot with usage, tickets, and any deal-stage shifts.
A CSM asks for renewal plans across 12 accounts — the Agent drafts each plan, the CSM reviews and queues outreach.
Product usage drops on a key account → health score updates → the CSM is alerted with a draft outreach plan, all without anyone touching a dashboard.
You set the objective — "reduce gross churn" — and the Workforce scores health, drafts outreach, and logs to the CRM, with its risk-signal criteria tuned through evals as churn outcomes flow back.
## Zoom into a single use case
Each use case below is a working entry point — clone a template, then run it, shape it visually, or build with AI depending on which tab fit you.
Score every account on health with reasoning, not just a number. Surface risk before renewal.
Auto-generate exec-ready QBR decks from CRM, support, and usage data — minutes, not hours.
Draft account-aware renewal and expansion plays for every account, every quarter.
## See it in production