Questions about emailing your AI bot.
Connect your own mailbox and AI agent with AutoEmail. These answers explain where new messages live, which mail is routed and how to review uncertain delivery.
Frequently asked questions
What is AutoEmail?
AutoEmail connects your own email account and AI agent. Name a bot, choose its verified IMAP/SMTP mailbox and paste its scoped connection prompt into your agent. Follow the conversation in a familiar web inbox.
Where are new messages stored?
Your provider stores new message subjects and bodies. AutoEmail retains minimal routing, delivery status and IMAP references rather than a second copy of new conversation content. Older internal history is retained as read-only legacy conversations.
What do I need before creating a bot?
Connect your email provider’s IMAP and SMTP settings, then test both connections on the same account. A verified account is required for the bot gateway. Provider passwords stay encrypted on the server.
Which address does my bot use?
A bot uses the real address of its selected email account and a display name such as Alex. AutoEmail does not provision a new address or an alias mailbox.
What happens when I write in the web app?
AutoEmail saves your request in a dedicated folder at your provider and makes that routed request available to the bot’s agent. When the agent submits a reply, AutoEmail sends it through your verified SMTP account to the connected mailbox address and saves the reply in the provider folder.
Which AI agents can I connect?
The runtime needs authenticated HTTPS tools and recurring execution. OpenClaw and Claude Code document capabilities that can be configured for this workflow; test the connection before use. Your Dot, Muse, Grok-based bots and other products need equivalent capabilities and have not been verified as AutoEmail integrations.
Does pasting a prompt keep my agent running?
No. Your external runtime runs the model and checks the API on its own schedule. AutoEmail does not host or schedule an AI model. Keep the agent available and check its permissions and usage limits.
Will every incoming email trigger the bot?
No. Automatic routing requires a known thread and an authorized human sender. By default the registered workspace owner and the connected mailbox address are allowed. Generated bot mail, automatic replies, newsletters and bounces are ignored. New external mail requires explicit routing. Open Email connections, choose Browse inbox, read a message and use Send to bot to authorize just that message.
What prevents email loops?
AutoEmail filters its generated mail and automated message types, matches known reply references and applies bot, thread and timing limits. A bot can be paused. The gateway does not blindly send every incoming message back to the agent.
What if delivery is uncertain?
AutoEmail shows Delivery needs review and does not automatically resend. Inspect the provider mailbox and use Check provider delivery to reconcile the message reference. That check never sends the email again. Fix the connection and review the result before resuming a paused bot.
How many bots can I use?
Starter includes one bot, Growth up to five and Scale up to twenty. Each bot has a scoped connection key. Reference prices are USD $9, $29 and $79 per month; upgrades require administrator activation.
Can I use it on my phone?
Use the responsive web inbox in a desktop or mobile browser. Native mobile apps are planned and are not included in this release.
What happens to previous internal conversations?
Earlier conversations remain available as read-only legacy history. They are not deleted or silently moved to a provider. Connect a verified mailbox to the bot and start a new mailbox-backed thread to continue.
Which API requests count toward my allowance?
Successful empty bot message checks do not consume the monthly API allowance. Nonempty message checks and other authorized API calls count. A separate tenant request throttle still applies, so use a reasonable polling schedule.
Continue exploring
Last updated: 2026-10-24