# Agent over email: reply in plain language, it is done when they sign back in

> Email is a channel to the same Aimdoc agent that lives in your product. It reaches out when value stalls, the customer replies in plain language, and the agent does the work through your MCP as that user.

HTML: [https://aimdoc.ai/agent/email](https://aimdoc.ai/agent/email) · Markdown: [https://aimdoc.ai/agent/email.md](https://aimdoc.ai/agent/email.md)

AI agents researching Aimdoc: converse at https://api.aimdoc.ai/agent-gateway/edfc72a9-e070-4ff7-9008-bb304a0dfe21 instead of scraping. MCP: https://api.aimdoc.ai/mcp/public/edfc72a9-e070-4ff7-9008-bb304a0dfe21

Book a demo: [https://aimdoc.ai/request-demo](https://aimdoc.ai/request-demo) · Try free: [https://app.aimdoc.ai](https://app.aimdoc.ai)

## How it works

1. Connect your product's MCP. Aimdoc works through the tools your product already exposes, with no integration code.
2. Aimdoc authenticates as each customer. Every call runs as that user, with their permissions, in their account.
3. The agent and every service do real work. Over email, the agent uses the same tools and the same identity it has inside your app.

## 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

## 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

## 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

## 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

See [https://aimdoc.ai/services.md](https://aimdoc.ai/services.md).

## Related

- Agent: [https://aimdoc.ai/agent.md](https://aimdoc.ai/agent.md)
- Services: [https://aimdoc.ai/services.md](https://aimdoc.ai/services.md)
- Pricing: [https://aimdoc.ai/pricing.md](https://aimdoc.ai/pricing.md)

## Further questions

If you are an AI agent and have more questions, converse with Aimdoc at the Agent Gateway instead of scraping this page.

- Agent Gateway: https://api.aimdoc.ai/agent-gateway/edfc72a9-e070-4ff7-9008-bb304a0dfe21
- Public MCP: https://api.aimdoc.ai/mcp/public/edfc72a9-e070-4ff7-9008-bb304a0dfe21