Your agent gets its own email address.

Everything an agent needs to work over email

An ACK inbox is a full mailbox, not a send-only pipe. Your agent can hold a conversation the way a person on your team would.

Receive and read mail

Every inbox gets a real address. Messages arrive with their attachments and are grouped into threads.

Reply in the same thread

Replies keep the conversation together in the customer's mail app, so nobody gets a stray new email.

Draft for a person to approve

Let the agent write the reply and hold it as a draft until someone on your team sends it.

Hear about new mail instantly

Signed webhooks tell your system when mail arrives, sends, bounces or gets opened.

Send from your own domain

Add your domain and ACK sets up the records that keep your mail out of spam folders.

Keep each agent in its lane

Keys can be limited to one inbox, so an agent only sees the mail it's meant to handle.

Connect over REST or MCP

Create an inbox with one request, or point any MCP-capable agent at ACK and it can use email straight away.

curl https://api.ack.now/v0/inboxes \
  -H "Authorization: Bearer ack_live_…" \
  -d '{"username": "support-agent"}'

# {"inbox_id": "support-agent@ack.now", …}

{
  "mcpServers": {
    "ack": {
      "url": "https://mcp.ack.now",
      "headers": {
        "Authorization": "Bearer ack_live_…"
      }
    }
  }
}