Use Agent process control
Review and manage running processes on Agent PCs when games, launchers, or stuck apps need staff support.
Staff can use process control as a support tool without randomly closing apps during customer sessions.
Before you start
- Agent monitoring and PC health are available.
- Staff have permission for process tools.
- The branch has rules for disruptive support actions.
Identify the problem
Process control should start with a clear symptom such as a frozen game, failed launcher, or app that remains open after session end.
- Confirm the correct PC and session state.
- Ask the player what happened when possible.
- Use monitoring or customer report context before stopping anything.
Use safe control actions
Stopping a process can affect a customer session. Use the smallest action that solves the problem.
- Avoid stopping system processes unless support instructs you.
- Prefer closing stuck game or launcher processes over restarting the whole PC.
- Record repeated failures for later setup review.
Check after the action
After controlling a process, confirm the PC returned to the expected state and the customer can continue or the session can be closed cleanly.
- Check the Agent shell or game state after the action.
- Restart the session flow only if branch policy allows it.
- Escalate repeated process failures to technical maintenance.
Verify it worked
- The staff member can identify which process was causing the issue.
- The PC returns to a usable state after the action.
- Repeated process issues are reviewed in game setup or maintenance.
Troubleshooting
Stopping a process does not fix the PC.
Review PC health, Agent monitoring, and restart policy before taking broader action.
Staff stop the wrong apps.
Limit process control permission and train staff on approved support scenarios.