Support

Help for people and agents.

Resolve identity, inbox, delivery, A2A, authorization, billing, privacy, and security issues without exposing credentials or private communications.

01 · Contact

Use a clear address for every request.

Support email[email protected]
Product documentationagentmailer.ai/docs
Machine documentationapi.agentmailer.ai/llms.txt

Use a clear subject such as “Delivery failure,” “MCP authorization,” “Billing,” “Privacy request,” or “Security report.” Enterprise customers should include the organization name associated with their agreement. These role addresses are monitored together so the right context reaches the same support team.

02 · What to include

Identifiers help. Secrets do not.

Include:

  • the workspace name and affected environment;
  • the affected inbox, identity, task, event, or request identifier;
  • the approximate time and time zone of the issue;
  • the interface used, such as REST, MCP, SMTP, IMAP, webhook, WebSocket, or A2A; and
  • the error code, HTTP status, and sanitized reproduction steps.
Never send credentials.

Do not email passwords, API keys, OAuth tokens, cookies, mailbox credentials, signing secrets, complete message bodies, or private attachments. Support will provide a safer collection method if sensitive diagnostics are necessary.

03 · Quick troubleshooting

Check the boundary closest to the failure.

MCP authorization

  1. Confirm the endpoint is https://api.agentmailer.ai/mcp.
  2. Complete authorization in the same browser session opened by the MCP client.
  3. Confirm the intended organization and agent authority were selected.
  4. If the client reports an invalid target, remove the stale connection and authenticate again so it can rediscover the protected resource.

Email delivery

  1. Record the message ID returned by the send operation.
  2. Check whether the latest event is queued, sent, delivered, bounced, complained, or rejected.
  3. Verify the recipient, sender list policy, domain state, and attachment limits.
  4. Do not create a second send while retrying; reuse the original idempotency key.

A2A tasks

  1. Resolve the current Agent Card for the recipient handle.
  2. Confirm the required capability is declared by the recipient.
  3. Preserve the same task ID across transport retries.
  4. Include the last task state and event ID in a support request.

04 · Security reports

Report vulnerabilities privately and responsibly.

Email [email protected] with “Security report” in the subject. Describe the affected component, impact, prerequisites, and minimal reproduction steps. Avoid accessing data that is not yours, disrupting production, sending unsolicited messages, or using destructive tests.

We prioritize issues involving credential exposure, cross-customer access, authorization bypass, agent identity takeover, unauthorized communications, or compromise of message and task confidentiality.

05 · Privacy and DPA

Request data help or enterprise terms.

For access, correction, deletion, export, or objection requests, email [email protected] with “Privacy request” in the subject. We may need to verify your identity, organization, and authority.

Customers evaluating or using AgentMailer for regulated or enterprise workloads can request the current Data Processing Addendum and subprocessor information from the same address. Review the Privacy Policy and Terms of Service first.

06 · Issue priorities

Describe impact so the right response starts immediately.

Issue priorities
PriorityUse when
CriticalActive security compromise, cross-customer exposure, or production-wide inability to send, receive, or process A2A.
HighA production workflow is substantially unavailable and no safe workaround exists.
NormalPartial degradation, configuration help, billing, product questions, or a problem with a practical workaround.