Create and deactivate users
Handle onboarding and offboarding in the directories specified in the ticket.
AI for service desks and ticket automation
Behind every ticket, someone needs to get back to work.
Myrmex connects the user’s request to what is happening in the environment. Your team investigates, fixes the issue and responds with context.
The resolution also needs to make sense to the person who opened the ticket.
“I already restarted it. Nothing changed.”
The history grows, the ticket moves between queues and the person is still waiting. To move forward, support needs to see the asset, the events and the cause behind the complaint.
Between the request and the resolution, the environment has answers.
Explore three support situations. Myrmex reads connected sources and presents the diagnosis alongside the work performed or proposed.
The description, history and asset come into the same conversation.
The team’s request
“Take GLPI ticket 4812, work out what happened on the requester's laptop and give me the answer ready to send.”
Cases › Service Management (ITSM)
What this example showsAnswer ready to publish, recurrence identified.
Illustrative scenario. Demonstration data; results depend on the environment and configured policies.
Access is part of support
Many tickets start with “I cannot sign in”.
New account, forgotten password, group change or offboarding: Myrmex handles the user alongside the request. Connect Active Directory, Microsoft Entra ID and Google Workspace to query and perform authorized actions.
Active DirectoryMicrosoft Entra IDGoogle Workspace
Reset passwords
Handle password requests through the authorized workflow and record the support outcome.
Update groups
Apply approved access and verify the user’s final state.
The request carries the user, the directories involved and the result of each action. Open items stay visible to the support team.
Explore the solution for identity teamsSome tickets can be prevented before they reach the queue.
An agreed routine can start with a Zabbix alert, check the host and run permitted actions. Anything requiring further authorization stays pending, with the context needed to decide.
Monitoring alert
Routine with a defined scope
Fix and validation
Decision when needed
Books › Execution
What this example shows61 GB freed; volume expansion awaits approval.
Team managers need to see the whole picture, too.
Inventory shows the assets that responded. Auditing identifies what needs fixing. Reporting brings together support activity and its evidence for review.
The team’s request
“Show me every computer with an outdated Chrome and who uses each one.”
Device › Inventory · win-nb-0212
What this example shows23 of 186 hosts below the baseline.
Before putting it to work
How we protect your operationsDo we need to leave GLPI?
The scenario starts with a connected GLPI instance. Myrmex reads the ticket and its history and can act through the integration, subject to permissions and approvals, keeping support connected to the ITSM.
How do we know the issue was resolved?
The demonstration should show verification on the asset and the support record. A completed action needs to include the observed result and any remaining work.
Choose a ticket that keeps coming back to your team.
See the context arrive, the diagnosis take shape and the resolution get recorded.