# Send from your customer's own inbox

Let them connect the Gmail or Outlook account they already work out of. From then on it sends and receives through AI Inbx on the same API as a domain you own.

[Get started](/signup)
[Documentation](https://docs.aiinbx.com/guides/mailboxes)

Your customer approves a Microsoft sign-in consent screen once, letting your app read their mail, send mail as them and keep that access. From then on support@acme.com is connected, and your product sends from it with the same aiinbx.emails.send call as any other address.

The ask

## Getting an address at your customer

Your AI support agent has to write from an address their customers recognise. There are three ways to get one, and two of them land on their IT department's desk.

Option 1: Not happening.

Point their domain at us

Sends as support@acme.com

-   Their MX record has to move
-   The whole company's mail moves with it
-   Nobody signs that off for a support agent

Option 2: Second best.

Give them a subdomain

Sends as support@mail.acme.com

-   Their IT has to publish DNS records
-   You both wait on it
-   Not the address their customers know

Option 3: Live in seconds.

Connect their mailbox

Sends as support@acme.com

-   One person approves, once
-   No DNS, no IT ticket
-   The inbox their team already works out of

After that

## It is just another address

The from address is the only line of your code that knows this is somebody else's mailbox. Short of open and click tracking, everything AI Inbx does for a domain you own, it does for this one — and not one of these is a thing you wire up per mailbox.

Threading

Replies land on the thread they answer, quoted text and all — not in a pile addressed to the same person.

Categories

What arrives is read and tagged before your webhook fires, the same way it is on every other address.

Pacing

Your rules and sending hours hold this address like any other. Scope a limit to its from address and it gets a budget of its own.

Suppressions

Someone who asked you to stop is stopped here too. The list is the workspace's, not the domain's.

Spaces

The mailbox is filed into the space its customer belongs to, and stays inside it.

Webhooks

Same payloads, same signature. Opens, clicks and complaints are the exception: a mailbox has no tracking and no feedback loop to report them.

Solutions

## Where it comes in

-   [Inbound email APIReceive email in your app over an API. Point an MX record at AI Inbx or connect Gmail and Outlook, and every message arrives as a signed, parsed JSON webhook.ThreadingAttachmentsMailboxesWildcard domains](/solutions/inbound-email-api)
-   [Email reply parserParse every email reply down to what the sender wrote: quoted text and repeated signatures removed, answers typed inside the quote kept where they were.ThreadingMailboxes](/solutions/email-reply-parser)
-   [Auto-reply detectionTell an out-of-office, a ticket acknowledgement or a bounce from a real reply. Every inbound email arrives with a category, even when no header gives it away.MailboxesSuppressions](/solutions/auto-reply-detection)
-   [Send email APISend email from your domain or your users' own Gmail and Outlook with one API call. Opt-outs and pacing are checked first, and replies land on the thread.ThreadingMailboxesPacingSuppressions](/solutions/send-email-api)

## Give your product an inbox. The hard parts are already handled.

[Get started](/signup)