The cost of scattered requests is not the volume. It is that nobody can stop checking every channel. Here is how to give requests one home, and the four fields that are the whole form.
In most small businesses, work arrives from everywhere. Email, chat, a comment on a document, a text to somebody's personal phone, a remark in a meeting that nobody wrote down.
The cost is not the volume of requests. Compare the actual number against the exhaustion it produces and the arithmetic does not work. The cost is that nobody can stop checking. When a request could arrive anywhere, every channel has to be monitored continuously, and continuous monitoring is what destroys concentration.
What this automation actually is
One route in for anything that is genuinely a request, meaning something that needs an action from someone. That route creates a tracked item with an owner and a due date, and it tells the requester it landed.
Conversation stays wherever conversation lives. Only requests get a home.
The acknowledgement is not a courtesy. It is the mechanism that removes the follow-up message, and follow-ups are a large share of the traffic.
How to build it
1. Define what counts as a request
Write it down in one sentence. Something that needs an action from someone who is not the person asking. Questions, opinions and discussion are not requests, and letting them into the queue is how it becomes unusable.
2. Capture four fields and refuse the fifth
What is needed, by when, why it matters, and who is asking. The last is captured automatically. Every additional field lowers completion, and forms grow through well-meaning additions until people go back to sending messages.
3. Create the tracked item automatically
The form response becomes a real item in whatever tracker you already use, with a default owner based on request type, and a due date derived from the stated date.
4. Acknowledge immediately, with a link
The requester must see straight away that it landed and where it sits. Most chasing is anxiety about whether something was received, and this single step removes a large share of it.
5. Publish response times and honour them
Same day for urgent, two working days for normal, weekly for the rest. A stated response time removes the incentive to mark everything urgent, which is the cheapest intervention available here.
6. Redirect old-route requests gently and consistently
When somebody sends a request the old way, do it, then ask them to use the route next time. Six weeks of that changes the habit. Refusing to help until they comply changes nothing except how people feel about you.
Tools and what they cost
| Option | What it costs | Honest trade-off |
|---|---|---|
| Google Forms into a tracker via Apps Script | Free with Google Workspace. | No per-submission cost and complete control over routing logic. You write and maintain the script. |
| Native forms in your tracker (Jira, Asana, ClickUp) | Included in paid tiers. | Least work, and the item is created natively with no integration to break. Field types and routing logic are usually limited. |
| Typeform, Tally, Fillout + connector | Form tools from free to tens a month, plus per-task connector cost. | Best-looking forms and the highest completion rates. Two subscriptions and a moving part between them. |
| A shared inbox with rules | Effectively free. | Lowest friction for requesters, since they just send an email. You lose structured fields, which is most of the value. |
What it is actually worth
I am not going to give you a percentage, because I have not found an independent study measuring intake automation specifically and I am not going to borrow one from a vendor.
What I can offer is a measurable mechanism and a related piece of independent evidence.
The mechanism: count how many distinct places a person on your team has to check before they can concentrate. One route in reduces that number, and it is the number that governs interruption.
The related evidence: research published in Harvard Business Review in 2022, conducted with Soroco, observed rather than surveyed knowledge workers and found they toggled between applications roughly 1,200 times a day, spending just under four hours a week re-orienting after those switches, which is about nine percent of the working year. The sample was small, 137 users across twenty teams at three firms, and I state that because most people quoting this figure do not. Intake fragmentation is one contributor to that toggling, not the whole of it.
Your own arithmetic: for one week, ask two people to note every time they check a channel specifically for incoming requests. Multiply by fifty weeks. That is your baseline, and it is more persuasive internally than any figure I could cite.
How it breaks
Somebody senior bypasses it in week three. Usually the founder, usually with something genuinely urgent. Fine once, fatal as a habit, because everyone below copies it immediately. Handle it, then log it through the route so the record stays complete.
The queue becomes a graveyard. If items enter and nothing visibly happens, people stop using it within a month. Every item needs a status and an owner within one working day, even if the status is that it waits until next quarter.
The form grows. Someone adds a field, then another. Guard the four fields harder than you think is reasonable.
People use it for conversation. Requests and discussion are different things. Move conversation back out, gently, every time.
How to tell whether it worked
Three measures. The share of requests that arrive through the route, which tells you whether the habit changed. Time from request received to first response, which is what requesters actually experience. And the number of items with no owner after one working day, which is the early warning that the queue is becoming a graveyard.