Like if someone comes to me and says "what if we... did X with the schedule". I could tell them how to do that and not to right away. The code would have to be changed / rewritten and tested and fail at it each time... so much mess.
Especially when scheduling other humans... the humans being scheduled can smell a computer scheduling a mile away and IMO they expect the worst at that point. They're not necessarily wrong.
I dunno. Computers are pretty good at this one too, on different kinds of variance and weights.
The largest problem I see is that everyone is discussing "either or" on this thread, while the clear winner is both.
They are very much not the same thing and the dynamic nature of keeping people happy and filling a schedule is extremely difficult to account for with software.
I do think that software speeds up some parts of the process, but like so many automated processes, it's computer assistance, not computer intelligence.
Even if you can get competence, you may want to automate it anyways. I'm currently working in health, and I recently visited a radiology center that claimed it took a full year to get front desk staff fully up to speed. Understanding the full scheduling requirements for all scans, some medicare rules that influence scheduling, and how to handle all the various problems, takes a long time. They live in terror of having front desk staff leave, because a quick replacement is impossible.
You could try http://jeffreykingston.id.au/khe/ which is free.
You can try it online at http://jeffreykingston.id.au/cgi-bin/hseval.cgi
It is still the most intricate software I’ve ever written in my 25 years of software dev, and I wrote it in high school.
I remember struggling with running out of RAM on the 4 megabyte school PCs.