How Biteable runs customer support on AcornReply

Biteable is a video-making platform with a user base far larger than the team behind it. It is also one of the products whose customer support we run day to day, which makes it our most demanding user: every Biteable support email flows through the same AI support inbox we sell.

This post is the working setup, written down honestly. No invented metrics, just the workflow.

The constraint

Biteable's audience writes in about everything a large consumer product generates: billing questions, export problems, account access, feature requests, the occasional student asking for a discount. The team answering them is tiny, and support is nobody's full-time job. The constraint isn't draft quality — it's that every minute in the inbox is a minute taken from building the product.

The setup

Biteable's support address forwards to an AcornReply workspace. That's the whole integration: no DNS surgery, no migration project, customers keep emailing the address they always used.

From there, the loop is the one described on our AI support inbox page:

1. Every inbound email arrives pre-drafted. The draft is written in a voice profile tuned to how Biteable actually replies — direct, friendly, no ticket-speak.
2. The customer's history sits beside the draft. Repeat writers are recognized instead of re-interrogated.
3. A person edits and sends. In Biteable's workflow, nothing reaches a customer without a human deciding it should. That discipline matters more at Biteable's volume, not less: one wrong automated answer to a paying customer costs more than all the drafting time saved.

Chat, too

Since June 2026 Biteable's in-app chat has run on AcornReply as well. The widget is one script tag in the app, and every chat lands in the same inbox as the support address — same thread history, same AI draft, same person deciding whether to send. Nothing about the loop above changes; chat is one more door into it. When nobody is online, the message waits in the inbox like any other, and if the customer left an email the reply reaches them there.

What running it ourselves proves

Every product we run support for uses the same workspace pattern — Grasshopper Signup, TangoQR, JupiterInvoice, and AcornReply itself. Biteable is the stress test: the one with real volume. The reason we're confident selling a flat-priced inbox to small teams is that we run a large product's support on it without hiring a support department.

Where this is heading

The drafts keep getting more specific as the voice profile tunes on every sent reply, and the FAQ-matching improves as the help content grows. The direction we care about is unchanged, though: AI that prepares, humans that send. That's the design bet the whole product makes, and Biteable is where we test it daily.

Curious what the same setup looks like for a team of one? Read how founders run it, or start free — your support address forwards in under a minute.