How it works
In your app, the agent has the same tools your product exposes, used as the signed-in user.
1Connect your product's MCP.
Aimdoc works through the tools your product already exposes. No integration code.
2Aimdoc authenticates as each customer.
Every call runs as that user, with their permissions, in their account.
3The agent and every service do real work.
In your app, over email, on your site, or for another agent. Where a tool is missing, a task definition teaches the browser path.
It connects to your MCP on behalf of every user.
Connect your product's MCP server once. Every action the agent takes runs through those tools, authenticated as the customer who asked, with their permissions and nothing more.
- Your tools, their identity: each call runs as the signed-in user, in their account, and is logged
- Task definitions for the rest: where your product has no tool, record the task once and the agent runs it in the browser
- Tribal knowledge included: narrate the caveats only your team knows; the agent keeps them
acting as matthew@hartwell.io · Hartwell Logistics
- done
list_shipments(status: "exception")
MCP tool · with their permissions
- done
update_carrier_rule(warehouse: "EU", carrier: "DHL")
MCP tool · with their permissions
- done
export_invoices(month: "August")
no tool · ran the task definition in the browser
It does the setup.
A new user lands in your product and the agent configures the account with them, step by step, showing the work as it goes.
- Operates your product: real setup completed while the user watches and stays in control
- Troubleshoots the edges: if a third-party integration throws an error, it finds the fix
- Knows when to hand off: escalates to your team the moment a human should step in
Starting setup…0/4It meets them with context.
The conversation from your website or gateway continues inside your app, so the first session starts with answers instead of questions.
- No cold starts: use case, stack, and goal carry over from the first conversation
- Identified through your SDK: website contact and app user connect automatically
- One agent throughout: the agent they met on your site is the one helping them in-app
Can it route new trial signups to the right rep in HubSpot?
Yes — and I can set it up with you. Start a trial and I'll bring this conversation in with me.
Welcome back, Matthew. Let's connect HubSpot first — I'll do the setup with you.
It knows the account.
With verified identity, the agent unlocks your CRM context for that user and their company, so every step reflects the relationship you already have.
- Verified identity: a signed sign-in unlocks CRM context per user and account
- Full account context: deals, history, and notes inform every answer and every step
- Per-account, not per-segment: this user, this company, this use case
Welcome back, Matthew. I’ve already switched this trial to SSO, and we can pick up where you left off with Alex. You can also skip the billing step — you’re covered under the Q3 proposal.
Set up in the first session.
By the end of the first session the account is configured and the user has seen your product work on their problem.
- A real account: configured during onboarding, not a slideshow
- Time to value, compressed: the aha moment happens in the first sitting
- Enterprise fits get routed: bigger deals go to your team with the whole journey attached
Matthew Smith
Hartwell — trial, day 1
First session
- 00:00Signed up — context from website chat
- 00:41HubSpot connected
- 03:12Lead fields mapped
- 06:48Routing rules configured
- 09:053 teammates invited
- 11:32First lead routed
Customers ask. The agent does it.
After setup, every customer keeps an agent that can do anything your MCP allows: change settings, run reports, complete tasks, resolve issues.
- Plain language in: users describe what they need; the agent does it in the product
- Done, not explained: work completed through your tools, with the result shown in the app
- Escalates with judgment: your team steps in for the moments that need a human, with full context
Can you export last month's qualified leads to HubSpot?
On it — running the export now.
- Pulling qualified leads
- Mapping fields to HubSpot contacts
- Syncing records
- Sending you the summary
Done in 40 seconds — no ticket, no queue.
It offers your services.
The agent is where your catalog shows up: it suggests a fitting service, sells it if it is priced, and runs it for that account inside the app.
- From your catalog: only the services you defined, with the tools you granted
- Sold in the conversation: included with a plan, requestable, or bought through your Stripe account
- Run and kept running: configured to the account, on a schedule, with results in the app
Hartwell Logistics
4 services configured to this account
- running
Weekly account audit
Mondays, 7:00 · Fixed 3 drifted settings
- running
Usage drop monitor
Continuous · Emailed 2 accounts this week
- scheduled
Monthly executive report
1st of the month · Sent to 4 recipients
- running
Failed sync investigation
On trigger · 2 resolved, 1 escalated