Why an email address beats a chat window for agent work
Most people meet AI in a chat window: open a tab, type, wait, copy the answer out. Mailbuttons agents have an email address instead. It sounds like a small difference. For business work it changes who can use the agent, when the work gets done, and how you stay in charge of it.
A chat window is a destination. You go to it, bring the job with you, and carry the result back out. An email address is the opposite. The job comes to the agent the way it already comes to you, and the agent writes back when it is done. Both can have the same kind of model behind them. The difference is where the work arrives and what happens to it before anything leaves.
We build agents you can email, so we are not neutral here. The cases where the chat window wins are further down, and they are real.
At a glance
| A chat window | An agent you can email | |
|---|---|---|
| Where it lives | A web app or a website widget. Another tab, another login. | The email you already use, on any device. |
| Handing over the work | High effort. Copy, paste, upload, then carry the answer back out. | Low effort. Forward the email, attachments and all. |
| How the work runs | Live. You sit with it, turn by turn. | In the background. Send it and get on with your day. |
| When a person must decide | By hand. You read the output and act on it somewhere else. | A button. Approve, Edit or Reject, from your phone. |
| Who can reach it | Your staff. Customers only through a widget on your website. | Anyone with an email address. No account to create. |
| What is on record | A transcript, in whichever account started the chat. | Every email it sends, marked as sent by an agent. |
| Best for | Thinking out loud, drafting, exploring. | Work that arrives by email and needs a yes before it goes back out. |
Each row is unpacked below.
Nothing new to learn
With a chat window, the business has to adopt something: a new place to go, another password, a change to the working day. With an address, there is nothing to adopt. Your staff already know how to forward an email. Your customers already know how to send one. The agent fits the routine you have instead of asking for a new one. We put it in three words on the homepage: nothing to install. The agent brings its buttons to your inbox.
The work happens while you are elsewhere
A chat is live. It needs you in the seat, feeding it, waiting for the next turn. That is fine for ten minutes of thinking out loud. It is a poor fit for a job that takes a while and does not need you for most of it.
Email is the other way round, and so is most business work. Take the quoting agent for builders. A customer emails an enquiry with the drawings attached. The agent reads the lot, asks the questions a good estimator would ask, and prices the job from the builder's own rate card. The builder is on site while that happens. When the quote is ready, it arrives for approval. Nobody sat in a chat window pasting in measurements.
Approval is a button, not a copy-and-paste
This is the point the name is about. A chat window has no natural way to ask permission. It produces text, and a person takes that text and does something with it, elsewhere. The oversight is real, but it is manual: read, judge, copy, paste, send.
An agent with an email address can simply ask. The quote arrives with Approve, Edit and Reject on it. You press one from your phone. Nothing reaches the customer until you do. The buttons you get are the agents you have hired: the quoting agent surfaces a quote to approve, and Sam, the sales assistant, surfaces a draft reply to a person. Signed in, the same items gather in one list called Needs you, so the question each morning is not "what did the agent do" but "what is waiting for me".
This is also how trust is built. A new agent starts supervised, and what it wants to send waits for you. As it proves itself you decide what it may do on its own, and the list of things that need you gets shorter. Some agents hold a line regardless: the quoting agent holds every quote, because that is what the job demands. The dial is yours.
People outside the business can use it
A chat window is for insiders. Your customers and suppliers never see it unless you put a widget on your website, and even then they are talking to your website, not to a colleague. An email address faces outward. A customer sends an enquiry to the address and gets a reply. A supplier asks a question and gets an answer. They never signed up for anything, because they already had the one thing needed: an address of their own.
The protections you would want come with it. The agent can only email people you have approved. Everything it sends is on record and says an agent sent it.
When the chat window is the better tool
It often is. Choose a chat window when:
- You are thinking out loud: brainstorming, drafting, arguing with yourself.
- The work is a conversation, with many quick turns and no clear end.
- You are exploring something: a spreadsheet, a long document, a question you cannot yet phrase well.
- The output is for you, now, and nobody else needs to approve it.
Choose an agent you can email when:
- The work starts as an email from someone else: an enquiry, a request for a quote, a supplier's question, a follow-up that is due.
- The job takes a while and does not need you for most of it.
- Something has to be checked by a person before it leaves, and you want that check to be a button rather than a chore.
- People outside the business need to reach it without an account.
Most businesses will end up using both. The chat window for the thinking. The address for the work that arrives from outside and needs a decision before it goes back out.
Where to start
The catalogue is small, and each listing says plainly whether you can hire it today. Browse the agents and give one job to an agent this week. If you would rather build one, start under Build: that is where an agent gets its address, its rules and its buttons.