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 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 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
-
Admin Panel
-
- What is the Process menu?
- What does workflow mean?
- What are Appearances?
- What are Actuators & Invocations?
- What are Automations?
- What are Guides?
- What are Actions?
- 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 move stuck tickets
-
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 use the Quicklaunch component
When it comes to Field Service, ticket processing and ticket tracking are important tasks that need to be resolved. This is usually achieved by back-office persons.
These duties include tasks like scanning documents after the ticket has been created, tasks like scanning documents after the ticket has been reported, and more tasks where bulk-action and bulk-editing is required to fulfill the requirements.
The Quicklaunch component is capable of helping back-office persons with those tasks as it features the required functionality.
The Quicklaunch component displays the current active form, which is based on the status of the ticket. Also supported are Custom Forms.
You are a back-office agent, that needs to prepare tickets from the "General tab" to fulfill a given company standard. Let's assume that the company standard is that every newly created ticket requires an internal code (provided by the back-office person) in the problem description of the ticket. This code is used by engineers to quickly process and solve problems. This is achieved by an internal document that only the engineer can access.
You, the back-office agent, would preferably use a view where the Ticket Pool component and Quicklaunch component are side-by-side.
- The back-office person clicks on the Views editor inside the Fieldcode Work Place.
- The back-office person creates a view with the Ticket Pool and Quicklaunch.
- The back-office person saves this view with the name “Quicklaunch”.
The back-office agent now may want to edit ticket details one-by one to fulfill his job.
- The back-office agent clicks on the first ticket.
- The back-office agent scrolls to the problem description.
- The back-office agent enters the new required details.
- The back-office agents proceeds in the same way with the next tickets.
0 out of 5 stars
5 Stars | 0% | |
4 Stars | 0% | |
3 Stars | 0% | |
2 Stars | 0% | |
1 Stars | 0% |