I'm looking to build territories with both geographic and product dimensions but unable to see how this is done from the user guide.
Has anyone done this before?
Territory management is broadly done in 2-steps.
1. Create territory attributes and define the coverage.
2. Compute the primary territory on the work order by configuring Territory Match Rules.
By design, Territory Coverage configuration allows, to define territories based on multiple attributes. There are four out of the box attributes namely, City, State, Country, Zip that can be mapped to geographic attributes.
New attributes can be defined by adding pick list values on the custom object, 'Territory Coverage', field 'Type'. Add new pick list values, for e.g. Region County, Business Unit, Product Type etc, to map additional geographic or non-geographic attributes. These attributes should now be available in the Territory Coverage tab to specify the values to define the territories coverage.
Once the territory are created by specifying the values for coverage attributes, you can use Territory Match Rules to map these attributes to any work order fields.
Currently the Territory Match rules are computed on the Work Order only if the 'Dispatch Optimization' is enabled for OptiMax or Linx.
Peter / Russell, could you give me more details on the use case around the requirement and timelines when you are planning to implement?
We have just had a conference regarding our own roadmap for next year, and improving our scheduling is seen as a key objective, but one for the latter half of the year, which we hope will tie in with the Servicemax roadmap for next year, as recently discussed at the Paris Maxlive event. I know our Service Delivery manager is keen to work with Servicemax when you start on the Assisted Scheduling offering.
Just for some background, we have a single Salesforce Org, which for Servicemax works across 8 countries (UK, France, Germany, Holland, Belgium, Spain, US and Canada), each county is independent in terms of the Service business, and the system is split using Roles, Security Groups and Sharing Rules.
Currently, most of the scheduling is done by using the dispatchers local knowledge, and because we have to use the site centric model, we have do not have the ability to use Technician Matching rules for instance, at the moment, and given the size of technician base (approx 200) we are coping, but see a need to move this forward and not have to rely on an individuals knowledge.
Hi Russelll Russell Jacobs,
Could you please elaborate on 'Assisted Scheduling' offering, you are talking about? Just want understand what do you mean by that and whether that is aligned with what is coming up in the product.