Rover arrives after the desk works.
Rover is the support bot being shaped for this environment. The design starts with a working human desk, then asks which parts of support work can be proposed, checked, handed off, and eventually carried out without confusing capability with permission.
What came across
Selected MSP-Bot support ideas became local Rover components, not a wholesale installation. Triage classifies a request, exposes ambiguity, preserves higher priority, and proposes only eligible technician IDs supplied to it. It does not write to GLPI. A separate correction ledger keeps proposed answers and reviews from silently rewriting approved knowledge.
The desk still owns the truth
GLPI remains the ticket record, Active Directory the identity source, and human technicians the decision makers. A proposal is not an assignment; a reviewed correction is not a published article. Rover’s first useful job is to prepare a clear, evidence-backed handoff a technician can inspect.
What has to happen next
Authenticated requester context, AD eligibility checks, live GLPI read access, scoped action receipts, technician review, and a model endpoint must be qualified before Rover can work a real lab ticket. The local tests establish component behavior; they do not establish a deployed requester-to-Rover-to-technician workflow.
Rover has tested bones and a defined boundary. This is her introduction—not an announcement that she is operating the live Help Desk.
Rover is a cover-story interpretation of a support operator under development. Original artwork; no DC affiliation or endorsement.