Not a great solution for recurring route-based businesses. No way to create indefinitely recurring routes. Recurring schedules must always be given end dates. If you set the date out too far, you'll bump up against your Salesforce API limits every time you want to make a change. Skedulo offers no way to automatically renew recurring schedules, so we've had to hire freelancers to manually go through all of our jobs and manually extend the schedules out using a "trick" to get the pattern builder to reappear (change the date of the last job in the series to another day, apply it to that job only, then change the date back and this time apply to all jobs to trigger the pattern builder to reappear, where you can now extend the schedule out again). Everything in Skedulo we do requires some sort of trick to get it to do what you want to do, making training employees on how to use it very difficult and frustrating for everyone.
Additionally, changes to recurring schedules are especially burdensome. Every change requires confirmation to apply the change to all jobs in the series, meaning that if you have multiple changes to make to a job you must make one change, wait for the pop up, confirm all jobs, make your next change, wait for the pop up. This makes keeping routes updated a very time intensive process and is requiring us to hire a full time person to essentially navigate skedulo's clunky interface.
One of the best features of Skedulo, the drag and drop functionality, is very temperamental and takes multiple tries to get the job to stick to your mouse, making schedule changes very frustrating and time-consuming. You'll spend more time than you need to trying to fight Skedulo's interface to try to get your changes reflected in the system. Additionally, as mentioned before, when you do make the change, for example moving a job to another resource's swimlane at a different time, you'll get a never ending series of pop ups asking you if you want each change to apply to all jobs in the series or just that job. That includes 1) removing the resource from the job 2) adding the new resource to the job 3) change the date and time of the job. When you have many jobs to change around, this turns into an all day activity.
Skedulo doesnt handle errors well. If the current view, whether it is the swimlane or a resource calendar view, contains a job that is missing a data field, the whole interface will fail to load. This will require you to start a data loader scavenger hunt to try to match us the vague error message with the job that is causing the error in data loader. No work can be accomplished until that error is fixed.
There also is a never ending stream of error messages that follow you wherever you go in the system on every page and menu, many of them vague and require you to contact support to figure out why you are getting them. Review collected by and hosted on G2.com.