How GLPI transforms IT incident management in companies

Three of the primary reasons for unresolved tickets are: authorization issues, misinformation, and lacking details. (J. D. Power) These challenges plague support teams daily, leading to delays, inefficiencies, and frustrated clients. However, with a system like GLPI, managing the lifecycle of tickets becomes easier, turning challenges into solutions.

Support teams face a lack of information in tickets, too many points of contact when people open tickets, numerous email threads to communicate about the same issue, making it harder to find where they stopped at, not to mention that in big teams, more people are working on the same ticket and are not aware of the efforts from others.

Additionally, teams finish the work in a ticket without the proper approval of a solution, and three weeks later the client mentions that a ticket was not solved, even though the service team believes it was. Even improper authorization policies tend to leave a ticket unresolved or wrongly solved.

A computer that faces the same issue every week, or every month, could be replaced as a better solution if the team knew this was a recurrent incident.

Problems like this are constants in support departments.

Assets have issues, and people at support would love to be aware of a pattern or the history of an asset that they are dealing with – it’s like a patient medical record.

If a doctor is aware of a patient’s medical history, including past illnesses and treatments, the current appointment and prescription will be more accurate. At hospitals, we have a medical record of a patient. In GLPI, a ticket may be this medical record for issues and, when integrated with its automatic inventory update, a medical record for assets.

Using the same example of hospitals, when you first get into a hospital, the emergency team knows exactly the steps they have to follow to ensure you receive proper support

In Brazil, it is like this – when it’s not a huge emergency:

  • Registration: You fill out an initial registration – forms for tickets
  • Triage: You are forwarded to a preliminary screening with a nurse – business rules for tickets or escalation
  • Vital Signs and Symptoms: Basic vital signs are taken by the same nurse (blood pressure, body temperature, and symptoms you are experiencing) – followup templates
  • Risk Classification: This triage gives you a classification of urgency in care – also called risk classification at hospitals – business rules for tickets
    • Different SLAs are applied based on this same classification – Time to Resolve an Incident in GLPI
  • Specialist Referal: Patients are directed to a specialist depending on their symptoms – Escalation levels in GLPI

What the first level staff doesn’t deal with is the other processes after this initial triage.

When doctors have access to your medical record, they work with information from triage and with additional information the patient provides when being listened to. There’s no post-its, or additional calling to the triage team during the appointment with the doctor. The doctor’s job now is to follow the next steps based on the information available.

The process of incident management is almost the same. I often say that service management is for every department that receives inputs and needs to deliver some output, whatever they may be.

GLPI in Action

When a person, or an asset has an issue, it fills, or they fill, a request automatically or manually telling that it needs, or they need, help with something. Whether it’s adding new features to a service or by fixing features in a working service.

The process in GLPI would be like this.

  • Issue Reporting: The issue is reported using a customized form that assesses important information for technical staff
  • Triage and Classification: GLPI automatically forwards it to a triage team, or uses automatic business rules for tickets, that perform a first evaluation and classification for priority and SLA
  • Impact Analysis: An SLA and Impact Analysis will trigger actions, so the ticket can be seen by people that should work on it.
  • Team Assignment: The incident is forwarded to the most proper team to solve the incident, taking into account the specialty needed for this issue
    • This may be done automatically with Business Rules for Tickets in GLPI
  • Transparency: The most important part is: Everything is transparent. Customer and all the teams working on the ticket have, or will have, access to this “medical record”, or timeline of a ticket in GLPI.

There are some additional

  • Customized Follow-Ups and Pending Reasons: The ticket gets stuck due to a need for information from the requester, so the service management team would appreciate adding pending reasons, so other team members know why that ticket is pending for so long.
  • Validation Requests: The service team may need extra authorizations to add features, or fix assets due to investment needs, extra layers of security, or validations. In GLPI, you may ask for validation without leaving the tool and, again, log everything into the same “medical record.”

GLPI Empowers Managers with Insights

  • Identify Trends: Managers can discover the most requested features or the most problematic assets, enabling proactive decision-making.
  • Plan for the Future: Leaders can use dashboards to assess recurring incidents and plan replacements or upgrades for high-maintenance assets.
  • Measure Success: Reports are constantly used to evaluate team performance and optimize processes.

GLPI changes the way a lifecycle of a ticket is handled by addressing core challenges that support teams face daily. From automated workflows to centralized and powerful timelines, ensuring transparency, and collaboration at every step.

Discover how to experience this same feeling of transformation for yourself.

More content? Follow us on our social media!

New Silver GLPI Partner in Palestine: Blueprint 360

Congratulations! We are happy to announce our new Silver GLPI Network partner in Palestine: Blueprint 360

Blueprint 360 is a top-notch tech consultancy focusing on IT Governance, Digitalization, Quality Management, and Process Automation. They’re all about innovation and helping businesses run smoother, work smarter, and grow sustainably. Their team blends experience with the latest tech to deliver solutions that keep organizations ahead in today’s fast-changing digital world.

🌐 Website: https://bit.ly/3WuDlyP

We are excited to see GLPI ITSM expanding internationally and helping more clients through our GLPI Network offering, whether it’s on-premise or in Cloud. Our new partners play a key role in making these services more accessible and ensuring high-quality support.

Being a partner means:

  • Enjoying special discounts
  • Accessing official support
  • Having a privileged contact with a Channel Manager to acquire more clients and boost your reputation in the Open Source ITSM market

If you would like to represent and deploy GLPI in your country, contact us: https://glpi-project.org/contact_us/

Stay connected! Follow us on our social media platforms!

Why managing your IT Tickets via email is risky?

An average person spends about 28% of their workweek managing emails. That’s nearly a full day each week lost in the chaos of inboxes and try to reach the so-called “inbox zero”. While email is a powerful communication tool, relying on in for managing tickets (IT, HR, Facilities or any other support department) may lead to significant challenges. 

Effective ticket management is crucial for maintaining operational efficiency and improving client satisfaction. However, many organizations still rely on email to manage their tickets, which can lead to a big number of issues on daily-routine.

The chaos of email management

Managing IT tickets via email may seem convenient at first, but it often results in chaos. Multiple threads, lost messages, unclear priorities, forgotten information, and even unwanted spam messages, lead support teams to overwhelming routines. According to industry studies, over 60% of SLA violations can be traced back to poor handling of tickets, now imagine if this information is fragmented.

Common problems with E-mail based ticket management

  1. Lost requests
  2. Miscommunication
  3. Delayed Responses

Transitioning to an ITSM Tool like GLPI you can transform how your organization manages service requests. Here’s how:

  • Centralized Communication with followups and tasks available to all members of departments
  • Improved Tracking with all actions related to a ticket in just one tool
  • Enhanced Collaboration using GLPI as your unique point of contact

Managing IT tickets via email seems like a simple and effective approach, and it works for a variety of organizations for some time and with a limited number of agents and daily service requests. The question is: Is it worthy the risk, stress and complexity of handling with the downsides of this practice while having better ways to do so?

By transitioning to GLPI, you can integrate your ticket management process, improve your team’s communication, and finally enhance customer satisfaction.

Don’t let the chaos be the rule and hold your team back. Embrace a more efficient way to manage your tickets.

Ready to take control of your ticket management? Learn more about GLPI and how it can transform your workflow!

More content? Join us on our social media!

New version of GLPI Android Inventory Agent 1.6.0 is available!

Fix 

Compatibility with Android 14

  • Fixed crash on first startup
  • Remove ServiceForeground that causing crash on Android 14
  • Fixed crash about registerReceiver

Enhancement

Scheduler

The Task Scheduler running automatic inventory has been rewritten using JobScheduler

This allows Android to determine the optimal timing for executing the automatic inventory within the defined time interval (dayweekmonth), while adhering to Android’s recommendations regarding battery usage, mobile network access, etc.

Notification 

The notifications engine has been rewritten to comply with Android.

From Android 13 onwards, you will be asked to authorize notifications on first startup.

(You can revert to this configuration in the notification settings of your Android device).

Permissions

The permission process has been rewritten for better compatibility with the latest version of Android.

Don’t forget!

The GLPI agent can be deployed / configured from an MDM / EMM tool such as

  • Samsung Knox
  • AirWatch
  • InTunes
  • MobileIron
  • etc.

As long as the MDM / EMM tool is compatible with managed configurations, you can configure the GLPI Agent (at deployment or on the fly).

Compatibility

Android

EMM / MDM compatibility implies a change in the minimum Android version supported by the android app.

From now on, you’ll need a device running at least Android 5 Lollipop (Sdk 21), and the agent is compatible up to Android 14 Upside Down Cake (Sdk 34).

GLPI environment

Android Inventory Agent1.3.01.4.01.5.01.6.0
GLPI10.0+10.0+10.0+10.0+
Plugin GLPI Agent Config1.2.01.2.11.2.11.2.1

Distribution

Google Play -> https://play.google.com/store/apps/details?id=org.glpi.inventory.agent

Github → https://github.com/glpi-project/android-inventory-agent/releases

Stay connected! Follow us on our social media platforms!

Recap of the GLPI Partner’s Day 2nd Edition in Rome 🇮🇹

Recap of the GLPI Partner’s Day 2nd Edition in Rome 🇮🇹

On Friday, October 25, we had the pleasure of welcoming our partners from around the world to the Palazzo Anantara in Rome for the 2nd edition of our GLPI Partner’s Day 🚀.

This event, designed to strengthen our community ties and share the latest GLPI updates, began at 4:30 p.m. with a warm welcome for attendees.

The conference kicked off at 5:30 p.m., with opening remarks from our CEO, Pascal Aubry, followed by Loic Lefur, our Sales Director, and his team of channel managers who work directly with our partners. Next, Daniela Buxo, Marketing Manager, shared key marketing statistics, insights about our social media, and plans for the upcoming year.

We were pleased to have Chloé Robin, Director of the web agency Buy The Way, present the upcoming GLPI website, which will be launched soon. Alexandre Delaunay, GLPI Product Owner, and Arthur Schaefer, GLPI Tech Writer, then took the stage to introduce the new features of GLPI 11 and discuss future functionalities.

The session concluded with a Q&A, providing an enriching exchange between the Teclib team and our partners.

At 7:00 p.m., it was time to enjoy an aperitif on the rooftop terrace of the Palazzo Anantara, offering a stunning view of Rome. The evening continued at 8:00 p.m. with a dinner filled with conversation, laughter, and cultural exchanges, making the event even more special.

We extend our heartfelt thanks to all our partners for their active participation and presence. We look forward to seeing you again next year for another exciting edition. Where will it be held? Stay tuned to find out!

Follow us on our social media so you don’t miss anything!