Email agent
An AI sales engineer inside your inbox
Connect the inbox your enquiries already land in. Kabaido reads each new RFQ, purchase order and technical question, runs the same pipeline the app runs and drafts the reply from your own address. Review mode is the default, so nothing reaches a customer until you say it can.
Customer enquiry
InboundAn RFQ arrives in the connected inbox, attachments included. The agent classifies it deterministically before any model is called.
Drafted reply, threaded
Review modeThe standard pipeline runs, then the agent drafts the branded reply in your voice with the quote PDF and portal link attached.
What it does
What happens to each message
The cheapest step runs first, so most mail never reaches a model at all. Everything after that is the standard Sales Engineer pipeline, working on the request exactly as it arrived.
- Classified before any model call
- Loop guards drop the agent's own sends, bounces and auto-replies. Then your own include and exclude filters on senders, domains and subjects apply, then deterministic keyword scoring sorts the message into RFQ, purchase order, technical question or none. A model is consulted only when those heuristics are uncertain.
- The standard pipeline, attachments included
- A detected email becomes a platform request and runs the same Sales Engineer pipeline as the app: typed lines, catalogue matches with fit ratings, values cited to their source and a clarification wherever something is missing. Attachments are uploaded and read with it.
- One of four replies, drafted in your branding
- The quote with its PDF attached and its portal link, a clarifying question where the pipeline cannot quote yet, a cited technical answer, or a structured read-back of a purchase order. The order entity itself is still created by a person: the agent does not commit orders on its own.
- Threaded on the original message
- Replies go out through the connected inbox itself, threaded with the original In-Reply-To and References headers, so the conversation stays one thread in the customer's mail client and in yours.
- A per-inbox activity view
- Every email the agent has seen is listed with its classification, its outcome and the credits it consumed. Anything the filters skipped can be processed by hand from the same view.
Connecting
Gmail and Microsoft 365
An organisation admin connects an inbox from Settings, Integrations, through the provider's own consent screen. These are the delegated permissions each connection asks for, in full.
Gmail
LiveGoogle's own consent screen, through a Google Cloud OAuth client.
- gmail.readonly
- Reads new messages and their attachments so the pipeline can work on the request as it arrived.
- gmail.send
- Sends the drafted reply from your own address, threaded on the original message.
Microsoft 365
LiveMicrosoft's own consent screen, through a Microsoft Entra app registration.
- User.Read
- Reads the signed-in account so the inbox is labelled with the address it belongs to.
- Mail.Read
- Reads new messages and their attachments.
- Mail.Send
- Sends the drafted reply from your own address.
- offline_access
- Keeps the connection alive without asking you to sign in again every hour.
Once connected, a scheduled job syncs every inbox every five minutes and picks up whatever has arrived since the last run. Each run processes up to three detected emails per inbox and carries the rest over, so a busy morning is worked through in order rather than all at once. Tokens are stored encrypted and the inbox can be disconnected at any time from the same settings page.
Review mode
Nothing leaves without your say-so
Every inbox starts in review mode. The agent still reads, classifies, runs the pipeline and drafts the full reply, but that reply goes to a review address you choose, which starts as the connected inbox itself. Your customer sees nothing.
You read the drafts the way you would read a new colleague’s: the quote with its PDF and portal link, the clarifying question, the cited technical answer. Where a draft is wrong you fix the underlying data or the filters, and the next one is right.
When the drafts are consistently right, flip that inbox to direct mode. It is a per-inbox switch, so one mailbox can run direct while another stays under review, and it can be switched back at any time.
| Behaviour | Review mode (default) | Direct mode |
|---|---|---|
| Reads and classifies new mail | Included | Included |
| Runs the full pipeline and drafts a reply | Included | Included |
| Where the drafted reply goes | A review address you choose | The customer, from your address |
| Quote marked as sent automatically | Not included | Included |
| Switchable per inbox, at any time | Included | Included |
Limits
What it never touches
An agent in your inbox is only worth having if its boundaries are exact. These are ours.
- Mail that predates the connection
- The sync cursor is anchored at the moment you connect. Everything already sitting in the inbox is outside the agent's window and is never read, classified or replied to.
- Mail that is not an enquiry
- Anything that classifies as none is left alone: no reply is drafted and nothing is created. It is still listed in the activity view so you can see what the agent decided and process it by hand if it was wrong.
- Its own sends, bounces and auto-replies
- Every send carries a Kabaido agent marker header, and the loop guards drop anything carrying it along with bounce and vacation traffic. The agent cannot answer itself.
- Your customers, until you say so
- In review mode, which is the default, no drafted reply reaches a customer at all. Nothing is sent outside your organisation until you flip the inbox to direct.
Cost
Reading is free, replying is one credit
The agent runs on the same credit balance as the rest of your account. There is no separate inbox subscription.
Syncing, reading and classifying consume nothing, at every rung of the ladder: the loop guards, your filters, the keyword scoring and the model call that only happens when those are uncertain. An inbox that receives a hundred newsletters a week costs the same as an empty one.
A drafted reply costs 1 credit, charged on top of the standard per-line charges of the pipeline run it wraps, exactly as the same request would cost in the app. Triggering a skipped email by hand charges the same as one the agent detected itself, and the activity view shows what every message consumed.
Questions
About the email agent
- An organisation admin connects a Gmail or Microsoft 365 inbox with full OAuth. The agent syncs new mail every five minutes, classifies each message deterministically before any model is called and turns detected RFQs, purchase orders and technical questions into requests that run the standard pipeline, attachments included. Replies are drafted in your branding, threaded on the original message with the quote PDF and portal link. Review mode is the default until you switch the inbox to direct.
- Gmail asks for gmail.readonly and gmail.send. Microsoft 365 asks for User.Read, Mail.Read, Mail.Send and offline_access. Those are the whole list: read new mail, send the reply from your own address and stay connected. Tokens are stored encrypted and an organisation admin can disconnect the inbox at any time.
- No. The sync cursor is anchored at the moment of connection, so only mail that arrives afterwards is ever seen. Nothing already in the mailbox is read, classified or replied to.
- Not unless you choose that. Review mode is the default and sends every draft to a review address you set, which starts as the connected inbox itself. Only when you flip the inbox to direct mode do replies go to the customer, and the quote is then marked as sent.
- A cron job syncs every connected inbox every five minutes. Each run processes up to three detected emails per inbox and the rest carry over to the next run five minutes later, so a heavy morning never starves the schedule.
- Reading and classifying consume no credits at all. A drafted reply costs 1 credit on top of the standard per-line charges of the pipeline run it wraps, and triggering a skipped email by hand costs exactly the same as one the agent detected itself. Every email in the activity view shows what it consumed.
- No. Every value carries a source span from your catalogue or the request. Where a value is missing the agent replies with a clarifying question instead of a quote. Cite or abstain is the rule in the inbox exactly as it is in the app.
The rest of the module
The same engine, wherever the request arrives
The inbox is one door into the Sales Engineer. A request pasted into the app, sent through the portal or pushed over the API runs the identical pipeline.
Point it at the inbox your enquiries already land in
Start free, connect a mailbox and read the drafts before anyone else does.