# AI for Implementation Teams: What Obi Does With Every New Customer

By Mantas Aleksiejevas

> Obi works directly with every new customer: it builds a plan, runs live screen-share sessions, sets things up where permitted and shows where they got stuck.

URL: /blog/ai-for-implementation-teams
Published: 2026-10-22
Target keyword: AI for implementation teams

**Quick answer:** Obi is Cor's AI onboarding agent. For an implementation or professional services team, Obi works directly with every new customer. It contacts them first, learns what they need and builds a plan. An admin on your team confirms the plan. Then Obi runs live sessions where the customer shares their screen, and it guides them through configuration, integrations, data imports and first-user training. Where you permit it, Obi sets things up for them. It follows up when a customer goes quiet, hands over to your team when a person is needed, and reports where each customer got stuck.

## Where implementation time goes

An implementation project has two kinds of work.

The first kind repeats with every customer: setting up the account, connecting the tools they already use, walking through a data import, training the first users, and chasing customers who stopped halfway.

The second kind needs judgement: scoping, unusual configurations, custom work, and conversations with the customer's stakeholders.

Obi takes on the first kind with each customer. Your team keeps the second.

## What Obi does in each phase of an implementation

| Phase | What Obi does |
|---|---|
| New customer | The customer is added to Cor, directly or through an integration. Obi contacts them first, by email. Nobody on your team has to trigger it. |
| Discovery and plan | Obi asks about the customer's goals and setup, then builds a plan for that customer, in their preferred language. An admin on your team confirms the plan before any work starts. |
| Configuration | The customer shares their screen. Obi sees their real account and works through each setting with them, step by step, by voice and chat. |
| Integrations and data | Obi follows the customer across tabs, windows and other apps, so connecting tools and moving data in are covered too. |
| Setup on their behalf | Where you permit it, Obi completes steps for the customer, within their own permissions. It asks for confirmation before major actions. |
| First-user training | Any new user can start a session from a link, any time of day, and Obi trains them on the workflows they need. |
| Follow-ups | When a customer goes quiet between sessions, Obi follows up by itself and picks up the plan where they left off. |
| Escalation | When something needs a person, Obi hands over to your team by email, Slack or Cor Admin, with what the customer was trying to do and what blocked them. |
| Reporting | Every session ends with a report: what got done, where the customer got stuck and what needs follow-up. Session data syncs to your CRM on every plan. |

## For example: one new account, start to finish

For example, a new customer of a scheduling product needs to connect their CRM, import their client list and invite their team.

1. The customer is added to Cor and Obi emails them to get started.
2. The customer starts a live session. Obi asks what they want working first.
3. Obi builds a plan: connect the CRM, import clients, invite the team. An admin on your team confirms it.
4. The customer shares their screen. Obi opens the CRM settings with them and works through the connection.
5. The import file has a column the product does not expect. Obi sees it on screen and helps the customer fix it before the import runs.
6. Where permitted, Obi sends the team invites for them, after the customer confirms.
7. The customer asks about a custom field mapping your team has not documented. Obi says it does not know, hands the question to your team with the context, and notes it in the report.
8. Your team gets the session report and picks up the one open question.

## What your implementation team keeps

Obi does the repeat work with each customer. Your team stays in charge of how it runs and keeps the work that needs a person.

- **Scoping and custom work.** What the customer needs built, and anything outside your standard setup.
- **Judgement calls.** How the customer's process should map to your product.
- **Key accounts and stakeholders.** The accounts and conversations you want a person on.
- **Approvals.** An admin confirms each plan before Obi starts, and you decide which actions Obi may take.
- **Handovers.** The questions and accounts Obi passes to your team, with the context already written up.

## Seeing where customers got stuck

Implementation leads usually find out a project stalled when someone asks. With Obi, every session ends with a report, plus the recording and transcript if you want them. An issue log collects the steps and questions that keep tripping customers up, each linked to the session moment. Session data syncs to your CRM on every plan, so account owners see progress where they already work.

## Getting Obi ready

You start with what you already have. Connect your help docs (direct integrations for Intercom and Zendesk), upload screen recordings or walk through your key workflows once. Obi turns them into session guides you review before going live. Run a test session yourself before any customer sees it. No engineering is needed, and most teams go live within days.

Your team can run Cor from Cor's own platform, or from Claude, ChatGPT and other AI assistants through Cor MCP. Critical changes still need approval in Cor Admin.

Customers can start Obi from a link, from inside the onboarding portal they already use, or from inside your product.

## When Obi fits an implementation team

It fits when every customer needs a slightly different setup, when setup spans several apps, and when customers sit in many time zones. It matters less when setup is one or two clicks, or when every project is custom work from start to finish.

Read more: [what an AI implementation agent is](/blog/ai-implementation-agent), [the customer onboarding workflow, step by step](/blog/customer-onboarding-workflow), and [how Obi runs a session](/product/onboarding-agent).

## About the author

**Mantas Aleksiejevas**

Co-founder of Cor. Works on Obi, the AI agent that runs customer onboarding.

[LinkedIn](https://www.linkedin.com/in/mantasaleks)

## FAQ

**Can AI run implementation sessions with our customers?**
Yes, for the repeat parts. Obi runs live sessions where the customer shares their screen, and it guides them through configuration, integrations, data imports and training. Where you permit it, it completes steps for them. It hands over to your team when something needs a person.

**Does Obi replace our implementation team?**
No. Obi takes on the repeat setup work with each customer. Your team keeps scoping, custom work, judgement calls and the accounts you want a person on. Obi hands those over with the context.

**Who approves what Obi does?**
An admin on your team confirms each customer's plan before any work starts. You decide which actions Obi may take, and it asks for confirmation before major actions. Critical changes need approval in Cor Admin.

**Can Obi handle integrations and data imports?**
Yes. Obi follows the customer's screen across tabs, windows and other apps, so it can guide them through connecting tools and moving data in, not only steps inside your product.

**How does our team know where a customer got stuck?**
Every session ends with a report showing what got done, where the customer got stuck and what needs follow-up. An issue log collects the repeat blockers across sessions, and session data syncs to your CRM on every plan.

**Can Obi work inside our onboarding portal?**
Yes. Customers can start a session from a link, from inside the onboarding portal they already use, or from inside your product.

**How is Cor priced?**
By session volume, never per seat. Plans start at $750/month. See [pricing](/pricing).