AI drafts every reply. A human still hits send.
AcornReply is a shared support inbox with AI built into the core, not bolted on as an add-on seat. Every inbound email arrives with a draft already written in your voice, the matching FAQ attached, and the customer's history alongside. You read, edit, send.
Why bolt-on AI keeps disappointing support teams.
Most helpdesks added AI as an upsell on top of a ticketing system designed fifteen years ago. The AI lives in a sidebar, the pricing lives per seat per add-on, and the workflow still assumes a support department. Small teams end up paying enterprise prices to babysit a chatbot they don't quite trust with their customers.
Autopilot AI answers customers wrong.
Fully automated replies fail exactly when it matters: the edge case, the angry customer, the refund question. One bad autonomous answer costs more than a hundred drafted ones.
Bolt-on AI costs a seat plus an add-on.
The AI tier usually stacks on per-seat pricing, so a three-person team pays for three seats and then again for the intelligence.
Chatbots deflect. Small teams need to answer.
Deflection metrics make sense at enterprise volume. At small-team volume every conversation is a customer you know by name, and deflecting them is how you lose them.
What AI-native looks like in practice.
AcornReply was designed around the draft-first loop from the first commit, which is why the whole product fits in a forwarded address and one screen.
Forward your support address.
Point [email protected] at your workspace address. Customers notice nothing; you stop living in Gmail.
Every email arrives pre-drafted.
The draft is written in the voice profile you picked, with the matching FAQ snippet attached and the customer history next to it. No prompt engineering, no sidebar.
You edit and send.
By default the AI never emails your customer on its own; drafts wait for you. That default is why the drafts can be aggressive about saving you time: the human catch is built into the loop.
The price ignores the AI.
Flat per workspace, free to start. The drafts are the product, not an add-on tier.
What a drafted reply actually looks like.
A customer asks 'can I export my data?' The draft arrives matched against your FAQ, written in your tone, with the customer's past conversations beside it. You add one sentence about timing and send. The customer gets a normal email from a person, because that's what it is.
Your first reply, in five minutes.
Sign up, forward your support address, paste five past replies. The next inbound message arrives with a draft already written.
Frequently asked questions
What is an AI support inbox?
A shared inbox where AI reads each inbound customer email and prepares a reply for a human to review and send. It differs from a chatbot (which answers customers directly) and from a plain shared inbox (where every reply starts from a blank box).
Can AI answer customer support emails by itself?
Technically yes, and AcornReply deliberately defaults the other way. Automated replies fail on the conversations that matter most. Drafting-plus-human-send captures nearly all the time savings with none of the wrong-answer risk.
Will customers know AI is involved?
Customers receive a normal email from your address, written in your voice, sent by you. There is no ticket portal and no bot signature; in the default workflow, nothing goes out without a person hitting send.
How is this different from a chatbot?
A chatbot talks to your customers. AcornReply talks to you: it prepares the reply, and you stay the sender. For small teams where every customer matters, that direction of trust is the whole point.