AcornReply
Sign in
Customer service automation

Automate the writing, not the deciding.

Most customer service automation is deflection in a nicer word: fewer customers reaching a person. AcornReply does the opposite. It automates the part that eats the time, which is writing the reply, and leaves every judgment call to you. A human reads each answer and hits send.

Start for free See pricing
The problem

What small teams mean when they say they want automation.

Almost nobody wants a robot answering their customers. They want back the twenty minutes it takes to write eight replies from a blank box. Those are different problems, and most automation software solves the first one by putting a deflection layer between you and the person who wrote in.

  • Every reply starts from nothing.

    A question you have answered fifty times gets typed out again, because the answer lives in one person's head rather than anywhere the inbox can reach.

  • The same twenty questions arrive every week.

    Pricing, refunds, setup, the one confusing screen. The volume is repetitive, but each customer still deserves an answer written for them and not a canned macro.

  • The knowledge sits with one person.

    When the teammate who knows the product is in a meeting, the queue waits. Nobody else can answer without checking with them first.

  • Hiring is the only lever most teams have.

    A second support hire is a large, permanent step for a team of four. Most small teams stretch instead, and every reply gets slower.

How AcornReply solves it

What AcornReply automates, and what it deliberately does not.

The drafting is automatic. The deciding is not. That line is the whole product, and it is the reason this kind of automation is safe to leave switched on.

  1. Your help center and past replies become the knowledge base.

    Articles, FAQ entries and the replies your team has already sent are what the AI reads. It answers out of your own material rather than a generic idea of customer service.

  2. Every inbound message arrives already drafted.

    The draft comes written in your voice, with the customer history and the articles it used sitting next to it. The blank box is gone before you open the thread.

  3. A human edits and sends.

    Nothing reaches a customer unreviewed. You skim, fix a line, send. The calls that need judgment stay with the person who can make one.

  4. The genuinely mechanical parts are opt-in.

    Routing to the right workspace, snoozing a thread until a date, and auto-reply all exist. Auto-reply is opt-in and ships off, so the human-sends rule holds unless you deliberately turn it on.

Example

Where the time actually goes.

A refund question that used to take six minutes takes one. The draft already cites your refund policy article and has the order history beside it, so you change a sentence and send. Repeat that across a morning queue and the automation has paid for itself without a single customer talking to a bot.

Getting started

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.

Start for free Read the quick start

Frequently asked questions

What can you actually automate in customer service?

Reliably: drafting the reply, pulling up the customer history, tagging and routing, snoozing a thread until a date, and acknowledging receipt. Much less reliably: deciding what the answer should be. AcornReply automates the first list and leaves the second to a person.

Will automation make replies sound robotic?

Only if the automation writes generically. AcornReply drafts from your own help center articles and past replies, in a voice profile you pick at setup, and you edit before sending. The message that goes out is one you approved.

Is automated customer service worth it for a small team?

It is worth it when the same questions repeat and replies are slow because writing them takes time. It is not worth it at five emails a week, where the setup costs more than it saves. Be honest about which one you are.

What should never be automated?

Refunds, apologies, and anything with a legal or contractual edge. Those need a person who can make a judgment call and stand behind it. AcornReply will draft them, but it will not send them unless you switch auto-reply on yourself, and it ships off.

Related