2 min read
4 ways on how to use Netadmin to visualize and improve processes
Netadmin Content Creator : Mar 20, 2020 4:11:00 PM
Modeling processes in Netadmin Nine
Every company follows a set of processes that define its business. In the fiber business, those processes define how customer orders are handled, installations are scheduled, and incidents are resolved. This involves a lot of data that should be documented and used in a standard way.
The Netadmin Nine Ticket Management capability supports customer processes involving user interaction by modeling each process as a ticket flow. It includes a graphical user interface to draw the flow with a set of steps and actions. With ticket flow, the user can follow the process instead of having to guess which actions should be taken and when.
Processes that could be modeled in Netadmin Nine Ticket Management:
-
Service order capture
-
CPE installation
-
Patching / depatching work orders
-
Incident reporting
-
Escalation between departments (e.g., 1st line support to 2nd line)
-
Customer communication
Customized user experience
Netadmin Nine Ticket Management can be customized with ticket templates. Ticket templates are plugin-based views that allow full customization of individual ticket flow actions.
A ticket template might include specific fields and questions users must fill in when processing a ticket. This allows the user to be guided through the process, which can also be followed up by reporting.
The template could also fetch information from other systems in real time and give the service desk user a full view of the customer without having to combine data from multiple sources.
Examples of ticket templates:
-
Predefined questions for customer service
-
Checklists for troubleshooting
-
Combined information about customer and network status
-
Possibility to execute operations on external systems
-
Documenting costs and work done by contractors
-
Categories for reporting
Visualizing problems
Tickets can be filtered in the ticket dashboard so users can focus only on the tickets they are interested in. Multiple filters can be configured to switch between different ticket types easily. When tickets are created on physical objects with coordinates such as subscriptions or installation addresses, they can be visually shown in Netadmin Nine maps (requires the GeoMaps Add-on). This can be useful for customer service in locating network problems and visualizing affected users in specific regions.
Netadmin Nine offers a separate interface for service providers, which can be used to communicate between the service provider and the network owner. Ticket flows make it easy to separate the actions between different parties. It also makes it possible to visualize who is responsible for handling the issue. An example of such a wholesale ticket flow can be seen below.
Reporting
Reporting is an essential part of the process. Without follow-up, it is impossible to tell if the process works as intended. Feedback also leads to improved methods when faults are discovered. For reporting to be consistent, the collected data needs to be structured and clean. The available options are often predefined in the ticket template to achieve this. The tickets can then be filtered by labels or more customized reporting.
The Netadmin Nine API can also integrate ticketing with an external reporting system. This might be preferred when reporting data is collected from several systems.
Ticket SLA Add-on includes reports to follow breaches of SLA during ticket flow. SLA tracking can be used to improve customer service and the work done by external contractors.
Conclusion
Netadmin Nine has been designed to meet the fiber business's many needs. It supports flexible process modeling with ticket flows and a fully customizable user experience with ticket templates.
So, if you want to improve your customer service and streamline your work, plenty of possibilities are ready to be used.