The full reel workflow

One inbox. Five agents. Nothing gets buried.

In the reel I said I'd send the whole workflow. Here it is — what each of the five agents does, and underneath that, the rulebook that puts every message into one of four categories. I've run this system on my own brand, so the things that break in practice are written down too.

Here's what you actually get:Every message gets read — text or voice note. Every message gets a category. The everyday questions get answered instantly, everything else reaches the right person, and all of it gets written to a sheet. At the end of the month you know what people are asking about most — and that on its own is a business insight.
Problem

Your real office is WhatsApp

Nobody asks for the shop address any more. Everyone turns up on WhatsApp. Orders there, questions there, complaints there, and the payment screenshot there too.

The problem is that all four land in the same list. Somebody's 'what are your timings' arrives in the middle of an order, a screenshot under that, and under that the person asking for the third time where their stuff is.

You read top to bottom, answer three, and the fourth slides down. By evening it's 40 messages down. It wasn't missed — it got buried, and nothing notifies you about a buried message.

So the question isn't who is going to reply. It's who is sorting the inbox.

System

Five agents, five separate jobs

Each agent does one thing. One. That is exactly why you can tell which part is working and which isn't.

  1. Agent 1

    Reads everything

    Text and voice notes both. A voice note gets transcribed into text and moves on the same way. This matters — a lot of people don't type, they talk, and orders usually arrive as voice notes.

    It does not read a list written inside a photo. There's more on that in the order block below.

  2. Agent 2

    Assigns the category

    Order, question, complaint, payment. Four, that's it. This agent doesn't reply — it only puts a label on, and the whole system runs off that label.

    Anything that fits none of the four — and there are two or three every day — goes straight to you with no label. Agent 2 is not allowed to guess.

  3. Agent 3

    Answers the everyday questions

    Timings, address, delivery charge, how to pay — those get answered immediately, at midnight too. It has an approved list: the question and the answer written out.

    If it isn't on the list, it doesn't answer. Guessing is forbidden for this one — and that is its most useful quality.

  4. Agent 4

    Gets it to the right person

    Orders to whoever handles dispatch, payments to accounts, complaints straight to the owner. A line goes with the message saying what it's about, so nobody has to scroll the whole chat.

    A route isn't just a name, it has a time on it. If nobody has touched it in two hours, it comes back up.

  5. Agent 5

    Writes everything to the sheet

    Every message becomes a row — when it came in, who sent it, what category it got, whether an auto-reply went out, who it went to, what the status is now.

    This is the part that pays off at the end of the month. '22 out of 60 people were asking the same thing' — you only ever see that in the sheet, never from memory.

Rulebook

Agent 2's triage rulebook

This is the part that decides everything else. Wrong category means the wrong reply goes out, the wrong person gets it, and the wrong thing gets written to the sheet. So for every category four things are settled in advance.

Jump straight to your category:

Every block has the same four things in the same order — Signal (how it gets recognised), Reply (bot or a person), Route (who it goes to), Log (what gets written to the sheet).

First block of the rulebook — how an order gets recognised and where it goes.

Order — never auto-confirmed

An order is the most expensive message there is. Buried means money gone, and wrongly confirmed means more than that. So in this category the system is fast but says very little.

  • Signal How it gets recognised

    The surest signal is a quantity — '2 dozen', '5 packets', '10 pieces'. Along with a doing word: send, need, make it, pack it. An address or a pin code getting pasted in is an order too. 'What's the rate' on its own is a question — but 'what's the rate for 10 packets' has already become an order, because a quantity turned up.

  • Reply Bot or a person

    The bot says only that the message was received and a confirmation is coming. The bot never confirms an order — it doesn't have the stock or the rate. Once a bot has said 'that's fine' and the stock wasn't there, you've traded a buried message for an angry customer. That's not a trade to make.

  • Route Who it goes to

    To whoever handles dispatch or billing — on WhatsApp and in the sheet. If nobody has changed the status in two hours the row comes back to the top and you get a ping. Order is the one category with the shortest timer on it.

  • Log What goes to the sheet

    category = order, the message exactly as it arrived, auto_replied = yes (only the acknowledgement went out), assigned_to = whoever got it, status = pending. notes holds the quantity and item that were extracted — so later you can see whether it read them right.

Two things break here in practice. One — people send orders in halves: a photo of the product on top, then a voice note underneath that just says 'send 2'. Read that message on its own and it means nothing, so Agent 2 reads the previous two or three messages alongside it. That rule got added later, because this is exactly what was breaking at the start. Two — a photo of a handwritten list. A person still reads that one; the system only says 'a photo of a list came in, take a look' and moves on. That's a gap, and I'm not hiding it.

Read the whole rulebook from the top

Question — the only category where the bot answers on its own.

Question — the answer comes from a list, not from thinking

This is where the volume is and where the effort is lowest. Usually 60-70% of messages are the same ten or twelve questions that come in every day — and every day a person is typing out the answers by hand.

  • Signal How it gets recognised

    Question words — what, how, when, how much, where, do you have — or just a '?'. The topics are usually a short list: timings, address, delivery charge, how to pay, whether a size or variant is in stock. A missing question mark means nothing; half the people on WhatsApp never type one.

  • Reply Bot or a person

    Auto-reply, but only from the approved list. If it's on the list the answer goes out immediately, 24 hours a day. If it isn't, Agent 3 doesn't compose one — it hands it to a person. That isn't a limitation, it's the rule. The day the bot invents a rate or a delivery date of its own, trust in that number is finished.

  • Route Who it goes to

    Anything already answered goes to nobody — it just gets written to the sheet. Anything that wasn't on the list goes to sales or to you, with one line saying what was asked. And that list slowly grows — today's escalation is next month's auto-reply.

  • Log What goes to the sheet

    category = question, auto_replied = yes or no, status = closed if the bot answered it. And a topic tag in notes — timing, price, delivery, stock. That tag looks like a small thing, but it's what builds the end-of-month insight.

The biggest mistake here is treating every question as a question. 'When is the delivery coming? It's been 4 days' looks like a question — it's a complaint. The rule is simple: if time has passed inside the question ('it's been 4 days', 'I've been waiting since yesterday') or an old order gets mentioned, it isn't a question — it goes to the complaint block. This one rule saves you the most, because getting it backwards is expensive: an angry person receiving an FAQ answer.

Read the whole rulebook from the top

Complaint — getting it to a person matters more here than speed does.

Complaint — the bot doesn't solve it, it only gets it to a person

In complaints the damage doesn't come from the message getting buried, it comes from the delay. The person is already angry — two hours of silence sends them off to write a review.

  • Signal How it gets recognised

    Two kinds of signal. Word ones — didn't arrive, wrong item, broken, refund, return, still nothing. And behaviour ones — the same person sending three messages in a short span, a reference to an old order, or a line where time has passed ('it's been three days'). The behaviour ones are more reliable, because words keep changing and behaviour doesn't.

  • Reply Bot or a person

    The bot sends one short acknowledgement with a name and a time in it — 'Rahul is looking at it, he'll reply by this evening'. The bot never gives a solution. And that line is kept deliberately short: sending a long polite template to an angry person is throwing fuel on the fire.

  • Route Who it goes to

    To the owner or a senior — not to the person who handled that order. The reason is straightforward: people sit on complaints about their own mistakes. Not deliberately — they just think 'I'll sort this out myself'. I learned that rule running this in my own business, not from a book.

  • Log What goes to the sheet

    category = complaint, status = open. This row never closes on its own — a person closes it by hand. notes holds the first message and what action was taken. How many rows were left sitting open at the end of the month is a report in itself.

Don't go by sentiment. Most of this inbox is written in Hinglish, and in Hinglish a sarcastic line and a genuine compliment look exactly alike — 'wah bhai bahut badiya service' reads as positive to any system judging by tone. So tone is deliberately given little weight in the rulebook, and behaviour a lot: how many times they wrote, how much time has passed, whether an old order came up. And one thing no rule catches — the person who goes completely quiet is the biggest complaint of all. No system will spot them. You have to go looking yourself, and reading back through the old closed rows in the sheet is the only way to do it.

Read the whole rulebook from the top

Payment — there's one line here the system never crosses.

Payment — a screenshot arriving and money arriving are two different things

A payment screenshot comes in several times a day, and 90% of them are completely fine. This whole rulebook is written for the other 10%.

  • Signal How it gets recognised

    An image with a short bit of text — done, sent, paid, transferred. Or a twelve-digit UTR / transaction reference, usually pasted on its own. Sometimes just an image with not a word attached — if an order was being discussed right before it, that's a payment, and this is exactly where reading the previous messages earns its keep.

  • Reply Bot or a person

    The bot says 'got the screenshot, we'll check and confirm'. It never says the payment has been received. A screenshot doesn't mean the money arrived — a pending transaction screenshots exactly like a successful one, UPI payments get reversed, people send to the wrong UPI ID, and a screenshot can simply be made.

  • Route Who it goes to

    To accounts, or whoever reconciles against the bank statement. The payment row gets tied to that same sender's order row so the two show up together — otherwise the sheet has a screenshot in it and no way to tell what it was for.

  • Log What goes to the sheet

    category = payment, status = unverified. Verified only gets written once somebody has seen it in the bank — the system never writes verified itself. notes holds the amount that was visible in the screenshot, with the word 'claimed' next to it, because that is a number that was read, not a number that arrived.

One thing that looks obvious but isn't: the system reads the amount out of the screenshot, and treating that as the truth is the actual mistake. That's why the word in the sheet is 'claimed' — it's a small difference, but it's the one that saves you when you're reconciling at the end of the month. The second thing — people who write 'sent the money' with no screenshot attached. That isn't a payment, it's a claim. The rulebook still gives it the payment category, but status unverified and notes saying 'no screenshot came' — so accounts knows in advance that they'll have to go looking.

Read the whole rulebook from the top
Why

Five small agents instead of one big inbox bot

Fair question — why not just hand the whole inbox to one bot?

You can. The problem is that bot has to do two jobs in one breath — work out what this is, and answer it. And when it gets confused it doesn't go quiet, it replies. That is the most expensive failure there is: it answered a complaint as though it were a question. The person was angry, and what they got was an FAQ.

In five separate agents that can't happen, because the one that recognises (Agent 2) and the one that replies (Agent 3) are not the same thing. Agent 3 has nothing beyond the approved list — it doesn't know how to guess, and that isn't a shortcoming, it's the design.

And the practical benefit: the day the auto-replies stop looking right, you switch off Agent 3 alone. The other four keep running — messages are still being read, categories are still being assigned, routing still happens, the sheet still fills. The inbox slows down a bit; it doesn't stop.

One big bot has no 'turn part of it off' — there is only on and off. The real advantage of five agents is that switching one off isn't switching the system off.

Sheet

Log sheet — make a copy

This is what Agent 5 writes to. Eight columns — timestamp, sender, category, message, auto_replied, assigned_to, status, notes. Everything the rulebook above says goes 'to the sheet' goes into these columns.

There are five example rows inside — one for each of the four categories, plus the question that wasn't on the list and went to a person. Read the rows and the format explains itself.

The sheet is useful on its own. Even without the system — start writing these four categories down by hand from today. Within a month you'll see for yourself what's coming in most, and after that the decision about what to automate becomes easy.

Make a copy of the log sheet

The link opens on 'Make a copy' — you get your own copy, mine isn't touched.

Next

If you want it set up on your own inbox

You can take the rulebook as-is and use it — the categories are fairly similar across most businesses. If you want it set up on your own inbox, send me a message and tell me two things: roughly how many messages come in a day, and what most of them are. I'll look at it and tell you how much can be automated in your case and how much should stay with a person. In plenty of cases the answer is 'not all of it', and I'll say that straight too.

Message me on WhatsApp

Straight to WhatsApp. No forms, no email.