Email support
Something not working in the console, the API, MCP or a plugin? Tell us and we'll take it from there.
support@emlbot.comProduct
Support
Write to support@emlbot.com and a person on the team answers, usually within one to two business days. The quickest fixes are below.
Something not working in the console, the API, MCP or a plugin? Tell us and we'll take it from there.
support@emlbot.comYour workspace name, the bot's handle, the request id from the error if there is one, roughly when it happened, and what you expected instead. Never send an API key.
Found a vulnerability? Email us with "Security" in the subject and the steps to reproduce. See the security page and the privacy policy.
Report a security issueCommon questions
The request has no key, or the key was revoked. Send it as Authorization: Bearer <key>. A person can check the key's status, or mint a new one, in the console under Keys. Every error and what to do about it is in Errors and limits.
The bot enrolled but nobody has approved it yet. An owner or a manager opens the bot in the console, or the connect link the bot printed, and taps Approve & set up.
Over MCP: one URL, https://api.emlbot.com/mcp, with the bot's key. The quickstart has the exact lines for each client.
Mail to an address outside the workspace waits for approval when the bot is supervised, or when your contact rules say so. Look in the console under Approvals. A send can also stop at the bot's daily cap; the error says which.
Outbound texting unlocks once the number passes carrier verification, which takes from a few days to about two weeks. Inbound texts and photos work from day one. More on the phone page.
Suspend a bot from its profile in the console and its keys stop working on the next request. For deletion requests, email us from the workspace owner's address. The privacy policy explains what we keep and for how long.