You know who gets the plumbing call at every building you run. That did not happen by accident: it took a few jobs that went well, at least one that did not, and a quote you still remember. The decision is finished. The next time a resident reports a leak, you will make it again.
Nothing about that feels like waste. Assigning a contractor takes a minute: open the request, see that it is plumbing, pick the name you always pick, write two lines, send. It is the kind of minute nobody counts, and doing it yourself feels like staying in control of who walks into your buildings.
The cost is in where the minute has to happen. The request cannot leave until someone with the authority to send it has opened it, and that person is walking a unit, or on the phone with an owner, or asleep. So a job whose answer has not changed in years sits in the same queue as the jobs that need thought. From the outside the two look alike: an open request with no one on it yet.
It also makes you a relay in a chain where you add nothing new. The resident knows what is wrong. The plumber knows what to do. Between them sits a step whose whole content is a choice you settled long ago, carried out again by hand.
And because the settled sends and the open questions arrive in one stream, the open questions get whatever attention is left. The repair that should have been quoted first, the damage that might be an insurance claim, the resident who needed a phone call before anyone knocked: those are the ones that deserved the morning.
A rule is a judgment you make once.
So what still needs a person? It helps to see that one maintenance request holds three different jobs. Reading it: what was said, where, and how urgent it is. Sending it: who gets the work. Judging it: what this particular situation deserves. The third is the one you are there for. The second is judgment too, but it is judgment you have already exercised, and a rule is how you keep it. Write down that plumbing at these buildings goes to this plumber, and the routine job leaves with your decision on it whether or not you were at your desk.
The control does not go anywhere. You choose which kinds of job the rule covers and which stay by hand, you can read who a request would go to before it goes, and you can turn the rule off. What changes is the queue: the requests waiting for you are the ones with a question in them.
Scaalr is built on that split. Alex reads each resident email as it arrives, writes the summary, and flags the urgent ones. Your rules send: map a case category to a trade, switch on automatic contractor dispatch, and a new case in that category becomes a work order for your best-matched preferred contractor. A case that arrives without a category goes out once your team sets one. The judgment calls come to you. How the match is made, and which cases wait for a person, is in Automatic Contractor Dispatch: Which Cases Leave on Their Own.
For the full breakdown of how automatic contractor dispatch works, see: Automatic Contractor Dispatch: Which Cases Leave on Their Own.
$99 covers your first 50 units, Alex included. Cancel anytime.