ServiceBox can do this a few different ways now.


Companies have come to us with pre-designated AM/PM areas they had onen or multiple trucks in over a X day period (I can not recall the exact number of days - 2 weeks/10 business days perhaps).  They kept their schedule of "this community of the city on this morning or afternoon over the # of days of their preset service areas.  Jobs were then filled in to these days on the Scheduler.  They would also fill in extras jobs if they had open times that were close, given the openings they felt they had.  They used the postal code search to determine with their set up distance parameter to decide which extra's to schedule in.


Another way to do it is to not have the preset service areas, just start scheduling WO'ers a particular way.  Once produced, using the postal code search for each one and the Scheduler in Week or Month "Normal" mode, find which days have the highest concentration of like postal codes in an area with the allowable distance set as small as possible, that a company are comfortable with.  Then, they can see which day they need to drag and drop the work order to (ends up in the assigned persons name as scheduled to on the Scheduler - so I hope they do this with the dispatcher as the Assigned person,  Then he/she may do one of two things.  Either immediately change the name on the dropped WO to a tech's name on the Normal mode Scheduler calendar or - better yet I believe - go to the day dropped to in the Dispatcher Scheduler mode, and see who else has jobs on that day in that area and change the WO on the Calendar from the dispatcher column to the tech he wants to do the job.



Lastly, if a ServiceBox customer uses "Groups" and designate certain employees to work predominantly certain areas, they may set a group for an area (eg.: DT, NE of DT, NW of DT, NE out of town, NW out of town, etc....) and then bring up only that group on either the Normal mode or Dispatcher Mode to show only those employees working those areas and schedule the WO to one of them.  This works too, when executed correctly.