Agent · Over email
Customers reply. The work gets done.
The agent emails when an account stalls. They answer in plain language, and it is done before they sign back in.
10,000 free credits · No credit card
// Stalled accounts
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
Food Safety course still in draft
Hi Maya, your Food Safety course is built but not published, so the 12 new hires at Denver have nothing assigned yet. Want me to publish it and enroll them? Just reply.
Yes please. Due in two weeks, and remind anyone who hasn't started by Friday.
Done. The course is published and 12 Denver new hires are enrolled, due in two weeks. Reminders go out Friday to anyone who hasn't started.
// Reply to delegate
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
Enroll the Denver new hires in Food Safety and remind anyone overdue?
On it. Running the enrollment now.
- Finding new hires at Denver
- Enrolling them in Food Safety
- Reminding anyone overdue
- Sending you the summary
Done in 40 seconds. No ticket, no queue.
// Same agent, same limits
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 maya@pellmark.com · Pellmark Training
- done
list_learners(location: "Denver", status: "new")
MCP tool · with their permissions
- done
enroll_learners(course: "Food Safety", count: 14)
MCP tool · with their permissions
- done
export_transcripts(month: "August")
no tool · ran the task definition in the browser
// Jobs by email
Hand off a job with a reply.
The jobs the AI owns keep customers posted where they already read, and handing off a new one is a reply away.
Kept posted: Denver back to compliant, three new hires enrolled, one manager looped in
Hand off more: a reply like "keep every new hire on track" becomes a job the AI owns
From your catalog: only services you defined, with the tools you granted
Pellmark Training
4 jobs owned for this account
- working
Keep every location compliant
11 / 12 compliant · 4 actions today
- on track
Get every new hire through onboarding
23 of 26 on track · 2 nudges sent
- on track
Renew every certificate on time
0 lapsed · next renewal in 9 days
- working
Keep the course catalog current
2 out of date · rewriting
// How it works
Over email, the work runs with the same tools and the same identity it has inside your app.
- 01
Connect your product and your systems.
Through your MCP or API, plus your CRM, Slack and email. No new integration to build.
- 02
Aimdoc authenticates as each customer.
Every call runs as that user, with their permissions, in their account.
- 03
Aimdoc delivers the work, and keeps working it.
Services are jobs the AI owns for each customer. Every step is metered, monitored and capped, wherever customers ask.
Let customers hand off work by email.
Turn on the email channel and the work keeps getting done while customers are away. Start free, no credit card.