Bring your agent. Give it a way to reach people.

01 / Request Access

Access is coming soon. Request Access on the Agent Identities page and tell us about your workflow. Once access is available, our team can help you connect your agent and test its first conversation.

Bring the agent you already run for sales, support, or operations. Mailrun gives it email and phone channels, and your application defines the job.

02 / Connect your existing agent

Add the Mailrun MCP connection to a compatible agent client and configure your key, or connect your application directly to the HTTP API. The key authorizes the communication tools available to your account. Your model, prompts, business systems, and approval rules remain under your control.

For an inbound voice conversation, your running agent must expose a customer-hosted public HTTPS voice handler. A desktop or MCP connection alone cannot answer live calls. Mailrun passes the caller’s words to that handler and speaks the agent’s response. Calendar booking and customer lookups use the tools you connect to your agent.

03 / Choose the identity and its domain

Give the agent a name and choose the email address and domain you want it to use. An identity can exist before its email channel is ready. Your agent can request domain onboarding and report the DNS or nameserver changes needed from the domain owner.

You need control of the domain or help from the person who manages it. Our team can help you plan the domain setup. Domain changes require the appropriate access; connecting Mailrun does not automatically give an agent permission to edit your registrar.

04 / Let the channels finish provisioning

Domain enrollment and mailbox setup run in the background. After the domain is active, your agent can attach the email channel and check its provisioning status. Adding a phone number is a separate step, and its status is checked separately.

Provisioning time depends on the domain, DNS changes, and infrastructure readiness. We’ll show what is ready and what is still waiting during onboarding. Use the ready status for each channel before attempting the first message or call.

05 / Give the agent a real task

Start with one person you know: ask the agent to send an introduction and copy you. Reply to that message, then ask the agent to continue the conversation. For phone, use a test caller and verify that your connected voice handler can answer and return the next step.

Your agent can use customer context, a calendar, or an internal system to complete the work. You decide which actions need approval. Mailrun provides the communication identity that stays consistent when you later change the agent or its model.

Your agent. Your limits. Your control.

Start with the access your agent needs for its job. Mailrun provides email sending caps, voice usage safeguards, and scoped API keys. Your application controls business decisions such as who the agent contacts, what it says, and when a person must approve an action.

Email limits you can set: choose a daily sending cap for each identity when you create it, or update the cap later through the API. An identity’s cap can tighten the account’s allowance, but cannot raise it. For example, you can give a new agent a smaller daily allowance while you test its workflow. Sends that exceed the enforced cap are refused.

Phone limits built in: calls have a maximum duration and a maximum number of conversation turns. Concurrent-call and voice-allowance checks also bound usage. These are service and account safeguards; the per-identity daily sending cap controls email, not phone calls. We’ll walk through your account’s voice limits during setup.

Access you can control: give each integration an API key scoped to the operations it needs. Keep administrative credentials separate from the agent’s working key. Revoke a key when an integration no longer needs access; future requests using that key are refused. Revoking a key does not undo messages already sent or actions already accepted.

Begin with a small email allowance and narrowly scoped access, test a real conversation, then expand access as the workflow earns your confidence. Usage limits bound communication activity; your agent’s instructions and approval rules still govern its decisions.