Automating request processing: how to stop moving them by hand
The most expensive part of working with requests is not getting them, it is not losing them. Requests come from the site, from email, from Instagram and from Telegram, and it is a living person who brings them together — one who now and then falls ill, sleeps and makes mistakes. We go through what can be removed here — and what is better left alone.
What it looks like without automation
The typical picture we see when people come to us: the form on the site sends an email, on Instagram people send DMs, someone calls, and regular customers write to the manager personally on Telegram. In the evening one person opens all of it and moves it into a spreadsheet.
The problem is not that it takes long. The problem is that it breaks invisibly. The email went to spam, the direct message was read and forgotten, the manager fell ill — and nobody even knows how many requests were lost, because there is nowhere to count them.
What actually gets automated
Not “everything”. Automation here is four separate things, and they can be done one at a time, in any order.
1. Collecting into one place
The first step and the most useful one. All the channels come together in one list: a spreadsheet, a panel or a chat. Each request gets a number, a time and a source. From then on you can see where people actually come from, not where you think they do.
2. An instant notification to whoever is working
The request lands not “in an email inbox” but with a particular person — on Telegram, with the name, the phone number and what the person wrote. The difference between answering in five minutes and answering in a day is mostly the difference between a customer and not a customer.
3. Status and reminders
A request stays in sight until someone sets its status: taken on, agreed, declined. If a request sits without an answer, the system reminds you itself. This is the part people do worst, because memory is not made for it.
4. Answers to the usual questions
Some of the questions repeat every day: is anything available, how much does it cost, where are you. A bot answers those — around the clock and the same way every time. People take on what needs a person.
How we build bots for this → They take requests, figure out the cost and answer the questions people always ask. What the work includes and what stays with you.Where to start if everything is done by hand
Not with software. Start with paper, literally in one evening:
- Write out every channel people reach you through. There are usually more of them than it seemed.
- Mark where each one lands right now and who reads it.
- Find the place where a request can get lost and nobody will find out. It is almost always the same place.
- Automate only that place first.
That way you get a result in a week rather than in a quarter, and you see whether it helps at all before you have spent the budget.
When automation is not needed
We say this plainly, because selling automation to someone who does not need it is the fastest way to lose that person for good.
- You get a few requests a week and all of them from regular customers. Here a person will do better than any system.
- Every request is one of a kind and needs a conversation. You can automate the record-keeping, but not the work itself.
- You do not have a settled way of doing things yet. Automation locks in what is already there — and it will lock in the mess just as well.
What this gives you in practice
The mechanism is simple, and that is exactly why it works. A request that has a number and a status cannot quietly disappear: either someone has taken it on, or it has been declined, or the system is reminding you that nobody has dealt with it. A whole category of losses goes away — one nobody knew about before, because there was nowhere to see it.
Process automation → Requests, reports and reminders that start happening by themselves. What the work includes and where we start.Common questions
- Do you need a CRM for this?Not necessarily. If there are not many requests, a spreadsheet and notifications on Telegram are enough — that is quick to do and costs nothing month to month. A CRM makes sense once several people are working with requests at the same time and you need to see who took what.
- Our requests come in through Instagram. Can those be pulled into one place?Yes, messages from Instagram and Facebook can be brought into a shared list. The limits are set by the platform itself, so before the work we check what exactly is allowed at that moment, and we say honestly if something is not possible.
- How long does work like this take?Simply bringing the channels together with notifications usually takes a few days. A full system with statuses, reminders and reports takes weeks. We name the exact timeline in the proposal after a conversation, before the work starts.
- And what if you want to change something later?That is the normal course of events: after a month of work it is always clear what was done wrong. That is why we advise starting small — changing a small piece costs less than rebuilding a system that was built over half a year on guesses.
Tell us how requests reach you
Just list the channels and say who reads them now. We will answer what is worth automating first and what is not worth touching at all.