4. Look for work to do when your queues are empty. Pay attention to widgets in the shared Technicians' Ticket and Work Overview tab including New Tickets That Need Attention, High Priority Alerts and Notifications, etc. Schedule appointments with the user as appropriate. (To avoid playing phone tag with the user, work should be scheduled, even if it is scheduled for the same day.)
5. Document changes you have made in customer infrastructure including:
- password changes
- new hardware
- new users and user accounts
- changes in or additions to network
- new software licenses and LOB programs
- other changes as needed
6. Notice and take appropriate action if something does not conform to our policies or normal procedures, even if you are not provided with explicit instructions (e.g., a missing checklist item, a security policy that is not being followed, an end user with admin privileges, a machine you were assigned to set up or troubleshoot for a customer we manage that does not have our RMM software on it, etc.) If such a case arises, notify a senior team member of the discrepancy promptly.
7. Attend to "Workstation offline" tickets promptly as needed.
8. Notice and take appropriate action if you notice a technical issue while working on a different issue (e.g., you’re checking backups on a server and you happen to notice updates have been failing on the server). If such a case arises:
- Create a ticket for it. Assign Office Admin as secondary resource. Add a note to the ticket to ask Office Admin to schedule a tech to handle it. You may ask to shadow the tech as they work so you can learn.
We take cyber security very seriously. You are responsible for understanding and following our general security policies and culture, beyond the letter of any checklists or KB articles you are following.
8. Stay abreast of documentation and KB articles. Retain what you are taught, take notes and review as necessary. If something in the documentation or checklist is inconsistent with the way you're being shown, you are responsible for pointing that out and asking senior staff about updating the documentation.
9. Ask for help if you have a technical issue which you do not believe you can resolve in a timely manner. Ask another technician for assistance immediately via Slack. It's best to first Slack the tech asking if she is available to help you, provide the ticket # and hold off on too much detail until she responds to your request. If other techs are not immediately available to help you, you are responsible for requesting a scheduled review of the issue and getting a resolution.
10. Follow directives and instructions issued by more senior team members.
11. Track your stock of forms and accessories (such as cables, etc) and notify Office Admin when you are running low and need a refill.
12. Meet virtually at least once per week with Senior IT Specialist and be prepared with questions regarding specific assignments or, more generally, software that we use, technical best practices, next steps to grow professional knowledge, etc.
13. Follow directives and instructions issued by the Senior IT Specialist .
II. Assignments
Assignments are work that a technician is assigned by another team member:
1. Scheduled remote appointments and on-site appointments. You are responsible for completing tickets promptly on which you are the primary resource. If you get stuck, ask for help in real time whenever possible. Your goal should be to complete the ticket in one session whenever possible.
2. Answer technical questions from administrative personnel, when possible, in a prompt and helpful manner.
3. Configure workstation specs for order quotes in cooperation with office admin.
4. Onsite:
Aim to arrive in the earliest part of the one-hour time window whenever possible.
Assist with physical labor and specific tasks as requested by senior tech.
Fill out OSSR and get it signed by customer contact.
III. Other Expectations
All Technicians should make every effort to respond to ticket escalations from the help desk team, taking on tickets ASAP. The procedure is documented
here.
As time allows, the Technician, in coordination with the office admin, should assist office admin by
responding promptly (within two hours) to support requests as appropriate. Responding does not mean work needs to be scheduled or completed immediately. It means the customer receives a response. Please see
Response Times and Services Levels .
As time allows, the Technician may work on other projects of tech's devising after receiving approval from a senior staff member.
The Technician must be able and willing to communicate with the customer via the ticket system notes as well as via phone when necessary. The Technician must also be able and willing to communicate with other team members to provide information or ask questions as necessary via the ticket system, Slack, phone and email.
It is expected that the Technician will utilize work time productively. When ticket work is slow, the Technician is expected to use the available work time to educate himself further on software and services we use and sell via vendor documentation or internal documentation.
It is expected that the Technician will take the initiative to grow and learn.