You can’t answer your way out of a pile.

Inquiries stack up. Everyone agrees the answer is to respond faster, so somebody buys a tool, somebody writes an autoresponder, and a month later the pile is the same size.

It was never a speed problem.

The pile is a sorting problem

A queue grows when things arrive faster than they leave. You can make things leave faster in two ways: work quicker, or work fewer of them.

Almost everybody tries the first one. It has a ceiling, and the ceiling is the number of hours your team has. The second one has no ceiling, and it is the one nobody wants to write down, because writing it down means saying out loud which inquiries you are not going to chase.

Until that is written somewhere, every inquiry is theoretically worth answering. That is what makes it a pile.

What breaks first is the order

The first thing a pile costs you is not response time. It is order.

People work the top of the list. The top of the list is whatever came in most recently, or whatever is easiest to reply to, or whoever emailed twice. None of those is the same as the one most likely to become a customer.

So the good inquiry sits four days at the bottom while three quick ones get handled, and by the time anyone opens it the buyer has talked to somebody else. Nobody made a bad call. There was no call to make, because there was no order other than the one the inbox invented.

Speed only counts inside a lane

Responding fast genuinely matters. It matters within a group of comparable inquiries, and it stops meaning much across a pile that has not been sorted.

Five minutes to everyone sounds impressive and mostly means you spent your sharpest hour of the day on your least likely buyer. Same-day to the ones that fit, and an honest reply to the ones that do not, will beat it on every measure you care about.

Write the disqualifier before the profile

Defining your ideal customer is hard and takes weeks. Defining what you will not take is quick, and you can usually do it in one sitting with the people who answer the inquiries.

Ask them which ones they already know are a waste. They will tell you immediately, because they have been carrying the list in their heads. Write those down as rules a new hire could apply without asking. Under a certain size. Outside the countries you can serve. Wants a thing you do not sell. Has asked three times and never booked.

That list is worth more on a Monday than a finished profile is, and it is the fastest route to the real one - a profile specific enough that two people would disqualify the same lead is the goal, and the disqualifiers are the first honest draft of it.

Two or three lanes, not a score

The instinct at this point is to build a scoring model. Resist it for now. A score needs history to be worth anything, and a team drowning in inquiries does not have the attention to tune one.

Two or three lanes will do almost all of the work.

Three lanes is usually enough to start. The point is not the categories, it is that every inquiry has one owner and one clock, and that the third lane exists at all.

The third lane is the one that makes the whole thing function, and the one most teams leave out. A queue without a bin is a queue that only grows. Answering honestly and closing it is not rudeness, it is the kindest thing you can do to someone you cannot help - and it is how the other two lanes get the time they need.

One owner per lane, and one clock. Not a shared inbox where the rule is that somebody will get to it. Equal responsibility is not shared responsibility, and a lane everyone owns is a lane nobody works.

Automate the sorting, not the answering

This is where most of the money gets spent in the wrong place.

Sorting is rule-based work. Deduplicate, enrich, check the disqualifiers, put the inquiry in a lane, assign an owner, start a clock, tell someone. A machine does that reliably, at three in the morning, without getting bored on the fortieth one. That is a good use of automation, and where a model earns its place it is in the judgement calls a rule cannot express - which is what qualification that actually reasons looks like on a record.

The reply is different. That is the first thing a buyer learns about how you work, and volume is a poor reason to hand it over. Automating the answer produces a faster pile with a friendlier tone, which is the old mistake with better grammar.

An acknowledgement is fine, and it does buy real time - as long as the actual reply lands when it says it will. An autoresponder that promises 24 hours and delivers in six days teaches people something specific about you.

When the pile means something else

Sort the pile for a few weeks and you get a number nobody had before: what share of inbound is actually a fit.

That number is worth sitting with. If most inquiries fail a disqualifier, more people will not fix it - you will have hired capacity to work inquiries you were never going to win. The lever is upstream, in what the site says, which channels are feeding it, or what you charge.

And if most of them do fit and there is still a pile, that is a genuinely good problem, and the answer is the boring one. Hire, or raise the price, or both. Either way you now have the number to argue it with.

None of this means the current setup was built badly. It was built for the volume that existed when it was built, by people who had other jobs. Demand outgrew it, which is the outcome everyone was working toward, and it shows up as a mess because nobody budgeted for the version that handles more. If you want a hand drawing the lanes and wiring them, that is what our services are for.

The pile is not asking you to be faster. It is asking you to decide.

Common questions