Welcome to the Fieldcode Manual

Tip: Start typing in the input box for immediate search results.

Some basic knowledge before we explore the applications in depth...

Tickets are the smallest piece of information within Fieldcode applications. Basically, every interaction with an affected customer can be handled inside a ticket. We intentionally offer various possibilities to categorize tickets (categories, sub-categories, or ticket types) and structure all important information within a ticket to give you enough space to use Fieldcode exactly as you need it. Our application is designed to provide you with the best possible insights on the status of a ticket within its life cycle. Therefore you will find multiple ways to search, find, display and analyze tickets.

Above you can see how a ticket in the Ticket Pool list is displayed

We call the lifecycle of the ticket the workflow. The workflow reflects all possible steps  available for a ticket and determines which actions are available. Initially, we provide you with a basic workflow that covers all standard Field Service Management use cases and helps you understand what is going on in every phase of the ticket. 

Simplified view on our workflow model

Ideally, a ticket in the process should follow the happy path until it is resolved, which is marked green in the scheme above. Exceptional paths, marked in red can occur but should lead back again to the happy path for the ideal procedure and completion of a ticket.

The workflow is not only supposed to indicate the status of the delivery but also helps to manage who should do what and when: The ticket inside the workflow allows for certain actions (see Interactions) or automatically triggers events (See Automated Actions) based on the progress of the workflow.

"We believe that the key to great service quality is the alignment of processes with less room for individual errors but enough space for direct actions"
Annika Goeres
- former Product Manager UX/UI

Workflows are designed to align all users of one process throughout the delivery chain, nevertheless, leaving enough freedom to handle and manage customer inquiries properly and quickly without the impediments of a static system.

Each ticket in your Fieldcode work place belongs to one project, whereas you are allowed to create as many projects as required to display and structure your delivery. Projects can reflect contracts with different customers to split tickets by category or other features. That depends on your preferences and use cases. Nonetheless, splitting tickets by customer gives you the best way to analyze KPIs and keep Service Level Agreements in focus.

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents