Which AI Onboarding Agent Works With Claude? (2026)

What "works with Claude" means for onboarding

"Works with Claude" can mean two different things.

A chatbot that answers questions. Some tools use an AI model to answer what customers type. The customer still has to know what to ask and work out the setup alone.

A connector your team uses from Claude. A connector lets Claude work with another tool for you. You ask Claude a question, and Claude asks the tool. Connectors are built on MCP, an open standard that lets AI assistants use other tools.

Cor is the second kind, and the onboarding itself goes further than answering. Obi does not wait for questions. It learns what each customer needs, builds a plan and takes them through the setup. Your team runs and checks that work from Claude.

So there are two sides:

• Your customers work with Obi. They join a live session in their web browser from a link. They do not need Claude.
• Your team works with Cor from Claude. You ask Claude how onboarding is going, and Claude asks Cor.

How Cor works from Claude, step by step

1. Add the Cor connector. Open Claude's connector directory, add Cor and sign in with Google. You need an existing Cor account. No engineers are needed.
2. Connect your knowledge base. Give Cor the link to your help docs (direct integrations for Intercom and Zendesk), upload screen recordings or walk through your key workflows once. From Claude, you can ask Cor to turn your help docs into tutorials for Obi. You review them before any customer sees them.
3. Obi works directly with every new customer. A new customer is added to Cor, directly or through an integration. Obi contacts them first and learns what they need.
4. Obi builds a plan. The plan fits that customer, in their preferred language. An admin on your team confirms it before any work starts.
5. Obi runs live sessions. The customer shares their screen. Obi sees their real account and guides them step by step, by voice and chat, across tabs, windows and other apps.
6. Obi sets things up where permitted. Where you allow it, Obi completes steps for the customer, within their own permissions. It asks for confirmation before major actions.
7. Obi hands over to your team. When something needs a person, Obi hands over by email, Slack or Cor Admin, with what the customer was trying to do. When a customer goes quiet, Obi follows up by itself.
8. Obi reports where customers got stuck. Every session ends with a report: what got done, where the customer got stuck and what needs follow-up.
9. Your team checks progress from Claude. Ask Claude "Who got stuck in onboarding this week, and why?" Cor shows the customers, where each one stalled and the session evidence. Then ask Claude to fix the knowledge gaps or rework a tutorial as a draft. Nothing reaches your customers until your team approves it.

What you can ask Claude once Cor is connected

These are the kinds of requests the Cor connector handles:

• "Who got stuck in onboarding this week, and why?"
• "Walk me through where Jane got stuck on Tuesday."
• "Ask our knowledge base the 30 questions a new customer would ask, and show me the weak answers."
• "Fix the knowledge gaps Obi found this week."
• "Rework the integration tutorial where customers keep stalling, and save it as a draft."

Claude is often already connected to your other tools, such as Slack and your CRM. Add Cor and it joins them. One request can find the customers who got stuck in Cor and draft follow-up tasks in your CRM, using the connections Claude already has.

Your team stays in control

• Critical changes need approval. They are reviewed and approved in Cor Admin. The AI assistant cannot approve or apply them.
• Admins choose what runs automatically and what needs permission.
• Your permissions still apply. Each person acts with their own Cor account permissions, and every action is logged.
• Plans are confirmed first. An admin confirms each customer's plan before Obi starts.

Who it fits

Cor fits B2B software teams whose customers need help setting up, not just answers. It fits best when:

• Your team already works in Claude (or ChatGPT) and does not want another tool to learn.
• Every customer needs a slightly different setup.
• Setup spans several apps, such as integrations and data imports.
• Customers sit in many time zones and want help when it suits them.

What it doesn't do

• Claude does not run the sessions. Obi runs the live sessions with your customers. Claude is where your team manages Cor.
• It does not replace your team. Obi takes on the repeat setup work. Your team keeps custom work, judgement calls and the accounts you want a person on.
• It does not act without limits. Obi only takes actions you permit, within the customer's own permissions, and asks before major actions.
• It does not create a Cor account from Claude. Signing in through the connector needs an existing Cor account.
• It matters less for very simple setups. If setup is one or two clicks, you may not need a live session.

Also works from ChatGPT and Claude Code

The same Cor MCP works from ChatGPT and other AI assistants that support MCP. Engineering teams can use the Cor CLI from the terminal, and the Cor MCP also works inside coding agents like Claude Code. Cor MCP is included in every plan. See Cor MCP.

What about other onboarding tools?

Other onboarding and customer success tools may offer their own Claude connectors or MCP servers. Check each vendor's own docs and Claude's connector directory for what is available today. When you compare, ask one question: does the tool run the onboarding with your customers, or does it answer questions and report data? For a wider list, see the best AI onboarding agents.

Pricing

Cor is priced by session volume, never per seat. Plans start at $750/month, and the Claude connector costs nothing extra. See pricing.

Read more: how Obi runs a session and Cor MCP for Claude and ChatGPT.