Support
First replies: a day to under a minute
A support operator exports every customer message from the last three weeks and reads them all before he automates anything. He sorts the messages into three piles. Pile one needs one factual answer: order status, hours, return window, a reset. Pile two needs a decision: a partial refund, a late return, an item on hold. Pile three is angry, legal, or new, and a person always takes it. Only pile one goes to the AI. Pile two works only when the owner first writes the decision as a one-page policy. In the first two weeks he read every AI answer. By week three he read exceptions only.
How it wentAcross the rollouts he tracks, first response fell from 12 to 24 hours to under a minute. A refund that took 3 to 5 days now closes the same day. He reports 60 to 80% of tickets closing without a human, and about 15 minutes a day reading exceptions by week three. These are rollout figures across his clients, not one named business.
Try it · based on the source's workflow
Sort my last [three weeks] of customer messages into three piles. Pile 1: one factual answer, using only [order system], [policy page], and [hours page]. Pile 2: needs a decision. Pile 3: angry, legal, or new. Draft pile 1 replies in my words and show me the first [20] before any send. Do not touch pile 2 until I give you a one-page written policy for it. Send pile 3 to me at once with the full history.
A starting template based on the workflow the source describes. Review it before you use it; you are responsible for what it does.
First replies: a day to under a minute — from The SmallOffice Brief, a daily brief of real AI cases for small businesses: https://smalloffice.space/case-first-replies-a-day-to-under-a-minute