Reply in plain language. It is done when they sign back in.
Email becomes a channel to the same agent that lives in your product. Customers delegate work by replying, and the agent completes it through your MCP as that user.
How it works
Over email, the agent uses the same tools and the same identity it has inside your app.
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.
Reply, and it is done.
A customer answers the agent's email with what they want, in their own words, and the work is finished by the time they open your product again.
- No form, no ticket: a reply is the request; the agent works out the steps
- Through your product's tools: as that user, with their permissions, logged to the account
- Result waiting at sign-in: a summary in the thread and the change live in the app
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 reaches out first.
The agent notices when an account stalls, writes to the person who can fix it, and offers to do the fix itself.
- Triggered by what happens in your product: setup left half done, usage that dropped, a sync that failed
- Specific, not a nudge: it says what it found and what it can do about it
- One reply away: the customer answers, the agent acts, nobody opens a ticket
No labels printed since Tuesday
Hi Jane, your EU warehouse is set up but no carrier rule points at it yet, so orders are still routing through Denver. Want me to add DHL for EU orders? Just reply.
Yes please, DHL Express for anything under 5kg and DHL Freight above.
Done. Two carrier rules added under EU warehouse, 14 pending orders re-routed. You will see them on the Shipments page when you sign in.
Same agent, same permissions.
A verified reply from a known customer unlocks the same MCP access the agent has when that customer is signed in, and nothing beyond it.
- Verified sender: replies are matched to the contact and the thread the agent started
- Scoped to the account: every tool call runs as that user, in their account
- Escalation built in: when judgment or authorization is needed, your team joins the thread
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
Services, delivered.
Scheduled services land in the inbox when they run, and a customer can ask for a new one by replying.
- Results by email: the weekly audit, the monthly report, the monitor that fired
- Ask for more: a reply like "a monthly report for my CFO" becomes a configured service
- From your catalog: only services you defined, with the tools you granted
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