Setup stalled? It writes to the person who can fix it.
Most accounts go quiet with setup half done, and a nurture sequence has no idea. The agent notices what stopped, emails the right person about it, and offers to do the fix itself.
- Triggered by 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: they answer, it acts, nobody opens a ticket
No jobs dispatched since Tuesday
Hi Jane, your Denver service area is set up but no dispatch rule points at it yet, so new Denver jobs are sitting unassigned. Want me to route them to a crew? Just reply.
Yes please. Residential jobs to the North crew, commercial to the South crew.
Done. Two dispatch rules added under Denver, 14 unassigned jobs scheduled. You will see them on the Schedule page when you sign in.
A reply is the request.
The customer answers in their own words. The agent works out the steps, completes them inside your product as that user, and the change is live by the time they open it 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.
Nothing it could not do in the app.
A verified reply from a known customer unlocks exactly the 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 action 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 Mechanical
- done
list_jobs(status: "unassigned")
MCP tool · with their permissions
- done
update_dispatch_rule(territory: "Denver", crew: "North")
MCP tool · with their permissions
- done
export_invoices(month: "August")
no tool · ran the task definition in the browser
Results land in the inbox.
Scheduled services deliver where the customer already reads, and asking for a new one is a reply away.
- 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 Mechanical
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
How it works
Over email, the agent has 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.