
Compare two working weeks
List the requests from a normal week and a busy week. Separate user issues, equipment failures and preventive tasks. A branch that loses its internet once may need a bounded troubleshooting job. A business repeatedly onboarding staff, repairing email access and checking backups needs a defined operating routine.
Write the support boundary
Ask who receives tickets, what happens outside the support window and whether site visits, parts and major upgrades are separately quoted. Track the difference between first response and resolution. If a QR code is used to open tickets, decide where it will be displayed and keep a fallback phone or email route for offline devices.
Test before committing
Run a short handover exercise. Report a printer fault and a branch outage separately, then check that each has the right priority, owner and escalation contact. Ask for a sample monthly report and confirm who controls asset and ticket records if you later switch providers.
What to prepare
Bring a device count by site, two recent problems, opening hours, and a list of systems managed by other vendors.


