Tip: You can use filters for better results
-
Latest News
-
Quick Start
-
Work Place
-
-
- How to schedule tickets
- How to search for tickets
- How to query tickets
- How to filter for tickets
- How to use the Ticket Clipboard tab
- How to grab/ungrab tickets
- How to link & unlink components together
- How to download ticket data as a excel sheet
- How to copy filters/queries for colleagues
- How to email filters/queries to colleagues
- How to assign/unassign tickets to/from partners
- How to manage parts
- How to show tickets on Map
- How to open tickets in a new tab
- How to use container tickets
-
-
- How to use the Optimizer
- How to schedule tickets
- How to publish/unpublish tickets
- How to lock/unlock tickets
- How to lock/unlock engineers
- How to manually reschedule PUDOs
- How to show tickets on Map
- How to manage availabilities
- How to manage subgroups
- How to display an additional time zone
- How to move tickets back to the Ticket Pool
-
-
-
- How to manage parts
- How to assign/unassign tickets to/from partners
- How to use the Interaction buttons
- How to use the Workflow buttons
- How to use communications
- How to schedule tickets
- How to edit ticket details
- How to cancel a ticket
- How to use the Remove Pending button
- How to report a ticket
- How to create intervention infos
- How to create intervention reports
- How to cancel an appointment
- How to clone tickets
- How to edit private notes
- How to add & remove skills
-
Admin Panel
-
- How to connect with ServiceNow
- How to create test tickets
- What are aliases?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
-
- What is the Process menu?
- What does workflow mean?
- What are appearances in context of workflows?
- What are buttons in context of workflows?
- What are automations in context of workflows?
- What are guides in context of workflows?
- What are actions in context of workflows?
- How to create & edit projects
- How to create & edit custom forms
- How to create & edit lists
- How to customize the Customer Portal
- How to create & edit automated actions
- How to create & edit conditions
- How to create & edit indications
- How to set up email templates
- How to create & edit ticket durations
- How to create & edit custom fields
- How to create & edit value sets
- How to create & edit SLA Profiles
- How to repair tickets with Ticket Workflow Monitoring
-
Fieldcode FMA app
-
- Fieldcode FMA app
- How to download the Fieldcode FMA app
- How to login
- How to configure multiple accounts
- How to enable/disable notifications
- How to change the theme
- How to log work times
- How to synchronize tickets
- How to navigate to appointments
- How to log drive times & drive breaks
- How to inform dispatchers
- How to view archived appointments
-
-
Customer Portal
How to configure ticket durations
Setting up ticket durations allows you to preset a time a ticket for the engineer should take by default. The time you set up here is later represented for a ticket that is dragged to the Timeline. Setting up conditions can further help to specify which tickets should be affected by the time preset. Enabling historical data allows for a smart way of determining a good default time duration, as it takes averages from previous tickets.
Inside the Fieldcode Admin Panel go to Process → Ticket Duration
FAQ Ticket durations
The default ticket duration if not configured differently is 60 minutes.
Dependent on if ticket durations are configured either the default ticket duration is used or not used:
- The overwrite ticket duration applies on newly manually created tickets with ticket duration slider or interface tickets
- The overwrite ticket duration applies on tickets where configuring ticket durations is possible inside the ticket creation form or interface tickets
- Therefore it may not be necessary to switch the toggle on, if you do not have the ticket duration slider inside the ticket creation form
- If no ticket duration is configured the default ticket duration is 60 minutes
- If ticket duration is configured the chosen ticket duration will be used as default for newly manually created tickets or interface tickets
- If user creates tickets and ticket durations are configured and “overwrite” is used, the default value will be overwritten
- If user creates tickets and ticket durations are configured and “overwrite” is not used, the default value will not be overwritten and accepted instead
- Users can edit the ticket duration in the Ticket Details anytime
If multiple Admin Panel rules match the ticket the following applies:
- The summary of the rules is calculated and the calculated average time will be used as ticket duration.
- Example:
Rule 1=20 minutes
Rule 2=30 minutes
Rule 3=15 Minutes
20+30+15=55 minutes
55 minutes/3 rules=18,33 Minutes
How to create & edit ticket durations
- Click on the plus button to open the creation form.
- Fill in the Basic, Filters and Historical data tabs.
1. Basic tab
- Decide if your new or existing ticket duration should be set to active in the system.
- (Optional) Insert a description for your ticket duration.
- Set a ticket duration in minutes. The default ticket duration (if nothing else is set) is 60 minutes.
- Click Save.
2. (Optional) Filters tab
The filters tab lets you determine which tickets should be affected by the time duration.
Filters: Allows fine-tuning criteria for AA using comparison and logical operators.
Condition: Defines a condition for your filter 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.
Connector: Allows you to combine a monitored field with another monitored field (AND, OR)
3. (Optional) Historical data tab
The Historical Data tab may be grayed out. If this is the case, you will need to reach a higher ticket count for smart estimations to be enabled and start working.
Enabling historical data allows the system to smartly estimate the ticket duration automatically.
Based on historical data the ticket duration will be adjusted automatically for future tickets without the user needing to enter a ticket duration.
- (Optional) Toggle the switch to the right to enable smart ticket duration estimation.
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |