Use case

Start a slow-computer case with evidence from the endpoint.

Investigate resource use and recent device context, review what the findings establish, then decide whether the next step is a remote session, command, or further check.

Start Free Trial Book a Demo

Explore Endpoint Diagnostics & Investigations

Ticket INC-58119

Illustrative support ticket

Subject

Illustrative case: computer running really slow

User

[email protected]

Endpoint

WIN11-MKT-204

User said

My computer is slow when I open the applications I use for work.

Example device context

Illustrative support request, not a customer result
Findings depend on the connected endpoint and available evidence

The problem

Keep the case together as you troubleshoot.

The request, device evidence, technician actions, and user updates belong in one support workflow. Use GenticFlow internal ticketing or connect a supported service desk.

User context

Start with the symptom, affected user, and when the issue occurs.

Endpoint evidence

Collect relevant readings and distinguish current observations from historical context.

Technician tools

Move into investigation, remote control, terminal, or files as the case requires.

The support workflow

From the request to the next technician action.

Use the available context, gather evidence, and choose the next support step. The workflow below is illustrative; actions and outcomes depend on the case and your configured access.

Resource readings

Review CPU, memory, disk, and process evidence from the affected endpoint.

Context and uncertainty

Compare the symptom with available history and recent changes. A resource reading alone does not establish the cause.

Technician next step

Review the findings, use hands-on tools when needed, and check the effect of any subsequent action.

Supported work

Supported actions and checks

The technician reviews the evidence and the applicable permissions or approval policy before acting.

Step 1

Investigations gather read-only evidence and retain the findings for review.

Step 2

Follow-up changes use separate technician actions or supported workflows.

Step 3

Confirm the original symptom with the user before recording resolution.

Scope and follow-up

When further work is needed

Keep the evidence and attempted actions with the ticket so the next technician can continue.

Boundary 1

An investigation can be inconclusive, particularly when the symptom is intermittent.

Boundary 2

A proposed cause is not a verified repair or a guarantee of improved performance.

FAQ

Common questions.

Specific answers for service desk and operations teams evaluating this workflow.

Does an Investigation fix the issue?

Investigations gather read-only evidence. A finding or recommendation is not a completed repair. Use a separate technician action or supported playbook and verify the outcome.

Do we need an existing RMM or PSA?

No. Lean teams can use GenticFlow as their primary support platform, including internal ticketing and user support. Connect supported existing tools where they fit your environment.

How can we try this workflow?

Start the free 30-day trial with the full product, your own environment, and real support cases. There is no artificial endpoint cap. The team will help arrange trial setup.