Mailboxes
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.
What your customer does. Once.
support@acme.com
Permissions requested
Northwind Support
northwind.com
This app would like to:
Accepting these permissions means that you allow this app to use your data as specified in their terms of service and privacy statement. You can change these permissions at https://myapps.microsoft.com. Show details
What your product sends from. From then on.
await aiinbx.emails.send({ from: "support@acme.com", to: lead.email, subject: "Following up", text: draft,})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.
Point their domain at us
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
Give them a subdomain
support@mail.acme.com- Their IT has to publish DNS records
- You both wait on it
- Not the address their customers know
Connect their mailbox
support@acme.comGmail, Outlook- 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
- 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
- Auto-reply detectionTell an out-of-office, a ticket acknowledgement or a bounce from a real reply. Every inbound email arrives with a category, decided from headers and content.MailboxesSuppressions
- 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