Fieldcode Manual

Tip: You can use filters for better results

Ticket scoring allows you to give tickets a prioritization that should be paid attention to by the optimizer. Dependent on the score points certain categories of a ticket can have many points or fewer points and are treated by the optimizer differently. Eg. tickets with more points will be scheduled more prioritized, than tickets with a low points score. Finding the right balance here can help you achieve your company goals better, tailored to your specific business needs. The optimizer works out of the box, but giving him additional input from the Fieldcode Admin Panel, helps to optimize even better.

Inside the Admin Panel go to Dispatch → Ticket scoring
Expand the menu by clicking the expand arrow in the Navigation  OR click directly on the Dispatch symbol to reveal all options of Dispatch configuration.

Configuring different ticket scores = improving system smartness

The more scores you create, the smarter the system decides for you because it has more data points from which to make decisions.
If dynamic ticket scores are utilized the ticket score will adjust based on the rules changing (true to false/false to true).
Recalculations are triggered automatically with no additional user interaction required.

Static conditions versus dynamic conditions
  • Static conditions have a common ticket score if selected static conditions apply. 
  • You require at least one static condition in order to create a rule successfully.
  • Dynamic conditions stack up on the static conditions score, if the dynamic condition comes true.
  • Dynamic conditions adjust the score based on the selected condition(s). Dynamic conditions each have an independent score that only applies if the dynamic condition is true.
  • Dynamic conditions give you the flexibility to take full advantage of date and time values.
  • For example, you could create a rule where an individual ticket could have different dynamic scores depending on the LSDT as a factor.
  • You could create a rule where if a ticket's LSDT exceeds a certain amount of time, the ticket could receive higher scores in the system and therefore be selected faster by the optimizer because this ticket has higher scores after the time passes.
  • Good to know: Static and dynamic conditions also work combined together.
Suggested operator usage

We generally suggest you to use the "equal" operators for number values and use the "is like" operator for text values.

  1. Click on the plus button to open the New rule form.
  2. Fill in the New rule tab.
  3. Decide first if your new rule should be set to active in the system.
  4. Enter a name for your new rule.
  5. In the next step, you can select a score value from 1 to 100 for your static conditions.
  6. Configuring static conditions will be explained in the next section.
    Configuring dynamic conditions will be explained in the second next section.
  1. Decide how many points should be assigned for all static condition(s) by moving the slider to the corresponding number or typing the number into the number field.
  2. Click on the Add static condition button.
  3. Select your first static condition from the condition dropdown, select an operator, and (optional) select a comparison value.
    Condition: Defines the condition for your scoring criteria.
    Operator: Compares the condition with the comparison (IS EQUAL TO, IS NOT EQUAL TO, IS LIKE, IS NOT LIKE, IN).
    Comparison Value: Defines with which value the condition is compared.
  4. (Optional) Add another static condition that must occur for your rule to apply. You can either use the And or Or connector to connect static conditions.
  5. (Optional) If you are not happy with your condition, you can always click the trash button on the right side to delete a static condition in order to retry.
  6. (Optional) Configure dynamic conditions (explained in the next section) if you want to make your new rule time-sensitive or date-sensitive.
  7. Click Save if you want to save only the static conditions for now. After clicking Save you will be prompted that processing may take up some time.
  8. Confirm with clicking Acknowledge.
Adding static conditions
Affected tickets do get recalculated if you save a new or existing ticket score configuration
  1. Click on the Add dynamic condition button.
  2. Select your first dynamic condition from the condition dropdown, select an operator, and (optional) select a comparison value.
    Condition: Defines the condition for your scoring criteria.
    Operator: Compares the condition with the comparison (IS EQUAL TO, IS NOT EQUAL TO, IS LIKE, IS NOT LIKE, IN).
    Comparison Value: Defines with which value the condition is compared. You can configure Now, Now +, and Now- values. The now values consider the ticket time.
  3.  Decide how many points should be assigned for the dynamic condition by moving the slider to the corresponding number or typing the number into the number field.
  4. (Optional) Add another dynamic condition that can occur.
    Dynamic conditions work independent from each other and add up to the static condition(s) score of the rule, if they occur.
    They therefore don’t require an connector.
  5. (Optional) If you are not happy with your condition, you can always click the trash button on the right side to delete a static condition in order to retry.
  6. Click Save. After clicking Save you will be prompted that processing may take up some time.
  7. Confirm with clicking Acknowledge.
Adding dynamic conditions
Affected tickets do get recalculated if you save a new or existing ticket score configuration

The higher the number of points, the higher the priority of the optimizer.

Condition: Defines the condition for your scoring criteria.
Operator: Compares the condition with the comparison (IS EQUAL TO, IS NOT EQUAL TO, IS LIKE, IS NOT LIKE, IN).
Comparison Value: Defines with which value the condition is compared.

Calculation explained with a detailed example

Generally spoken all tickets start with a score of 0 points if you do not do not configure anything inside Ticket scoring.

Let's assume you have configured three different ticket score rules in the ticket score list:

isVIP is equal to True -> 40 Points assigned
isEscalated is equal to True -> 20 points assigned
projectName is equal to "Example project" -> 30 points assigned

If a ticket matches the third condition only the ticket score would calculate as follows:
30 points assigned
 -> The ticket score would be 30.

If a ticket matches all conditions the ticket score would calculate as follows:
40 points + 20 points + 30 points 
-> The ticket score would be 90 points.

Calculation formula if multiple rules apply on one ticket: 
The sum of points of all matching ticket score rules.

What is the maximum score a ticket can have?
999 points.

What is the minimum score a ticket score rule can have?
One point.

What happens with dynamic conditions?
Dynamic conditions simply just stack up on the static conditions score.
The above-explained calculation still applies. Or formulated in other words:
Dynamic conditions are an additional layer on top of the static conditions.

The ticket scores are displayed inside Ticket Pool if you have the Score column enabled.
If you cannot see the Score column you 
can learn here how to customize rows inside the Ticket Pool.

Score column inside the Ticket Pool
Was this topic helpful?
0 out of 5 stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we further improve this topic?
Please submit the reason for your vote so that we can improve this topic.
Navigation