Helpdesk operations
A shared mailbox handover checklist for IT support queues
A short checklist that keeps a shared support mailbox readable across shifts, so the next assistant can see what was answered, what is waiting, and who owns each thread.
Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.
Delegation playbook
On this pageJump to section
A shared support mailbox is easy to start and hard to hand over. One assistant answers a thread, another adds a note, and by the end of the week the inbox holds half-finished conversations that nobody can attribute. A handover checklist turns that pile into a short, readable queue. The checklist adds little work at the end of a shift, but it gives the next person a clear picture of what is open, what was promised, and what needs a decision.
Decide what the mailbox is for
Write down the kinds of messages the shared mailbox should receive, such as password resets, access requests, hardware faults, and questions about a published service status. Name the messages that belong in the ticketing system instead, and say who moves them. A mailbox with no intake rule becomes a second, informal ticket queue that nobody reports on. Review the rule when a new service or office joins the company.
Give the mailbox one owner who can change the rules and one backup who can act when the owner is away. Record both names in the mailbox description so a new assistant can find them. The owner does not need to answer every message, but they should decide what the queue is for. Ownership is what stops the mailbox from drifting into a general chat channel.
List the folders and saved replies that matter
Keep a small folder set such as New, Waiting on user, Waiting on vendor, and Resolved this week. Explain in the checklist what belongs in each folder and when a message moves. A folder tree with twenty categories is harder to maintain than a short one with a clear rule. Review the folders each quarter and remove any that no longer match the work.
Store saved replies for the messages the team sends every day, including the acknowledgement, the request for more detail, and the closing note. Put the saved replies in a shared document or a reviewed template library. Replace placeholders such as the ticket number and the service name at send time. A saved reply that still names a retired system undermines the answer it is meant to speed up.
Write the handover note at the end of each shift
End each shift with a short note that lists the messages still open, the owner of each one, and the next action with a date. Include the messages that were answered but need a follow-up check. Write the note in the mailbox or the ticket system, not in a personal chat. A handover that lives in a private channel disappears when that person is on leave.
Use the same four or five headings every day so the next reader can scan the note quickly. Put urgent items first, then the waiting items, then anything that needs a decision from a manager. Keep each line to one sentence with a name and a date. A consistent format is more useful than a longer note with a different shape every day.
Set rules for who may move or delete mail
Allow any trained assistant to move a message between folders, but restrict permanent deletion to the mailbox owner or a manager. Archive resolved threads on a schedule rather than deleting them, because an old message often explains why a change was made. Record the retention period the company uses and follow it. A shared mailbox is a business record, not a personal filing cabinet.
Check that every assistant knows how to search the archive before asking a colleague for context. A quick search of the sender and the subject often answers the question without interrupting anyone. If a message must be removed, record the reason and the approval in the ticket. Deletion without a trail makes a later dispute much harder to resolve.
Test access before the first solo shift
Give a new assistant access to the mailbox through a named account rather than a shared password, and test the sign-in before their first solo shift. Confirm they can read, reply, move, and search, and that sent items appear under their own name. Watch them send one test reply to an internal address. A permission that looks correct in the admin console can still fail at the mailbox.
Record the test date and the person who ran it in the onboarding checklist. Repeat the check after any change to the mail platform or the permission group. If the assistant also needs calendar access, test that separately because the two permissions are often granted by different groups. Access that is assumed is the access that fails on a busy morning.
Review the shared queue each month
Count the messages received, the messages still open at month end, and the median time to first reply. Compare the counts with the ticket system so a request that arrived by both routes is not counted twice. Look for a sender who repeatedly bypasses the queue, because that pattern often signals a broken form or a missing service. Report the three numbers to the IT manager in one short paragraph.
Ask the assistants which saved replies and folders they actually use, then remove the rest. A monthly review keeps the mailbox aligned with the work instead of with last year's process. Record one improvement to make before the next review and who owns it. The queue stays readable when someone prunes it on a schedule rather than during a crisis.
Sources and next step
Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the helpdesk intake, change communication, asset return, outage update, and patch pilot practices discussed in these guides. The NIST patch management planning guidance supports the pilot hold and stop-signal steps, and NIST configuration management guidance supports the equipment and deployment records. Apply your own policies, contracts, and system documentation to the workflow. Compare this guide with the contractor equipment return checklist and the outage status update guide before changing a live process.
Keep decisions, approvals, and evidence in systems the business already controls. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.
Operating brief
What this guide should help you decide
Routine intake, status updates, records, screenshots, and documentation upkeep.
Approvals, risky system changes, security decisions, and final technical judgment.
How to use this guide
Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.
Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.
Workflow
Recommended operating workflow
Define the request
Write what a shared mailbox handover checklist for it support queues means in your company, where requests enter, and what finished work looks like.
Limit the access
Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.
Run a pilot
Use a two-week sample period so the manager can review accuracy before expanding the workflow.
Review patterns
Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.
Decision rules
| Question | VA fit signal | Escalate when |
|---|---|---|
| Is the work repeatable? | The same request appears weekly and can be described in steps. | The request changes business policy or system design. |
| Can quality be reviewed? | The manager can inspect the output without redoing the work. | Only a senior technical person can judge correctness. |
| Is access contained? | The assistant can work with read-only or role-limited access. | Admin rights, customer data, or security settings are involved. |
Delegation checklist
- Write the intake source, expected output, and manager review cadence.
- Confirm the assistant has only the permissions needed for the workflow.
- List the events that require escalation before work continues.
- Track examples for two weeks before changing the workflow.
- Save examples of good and bad outputs so the assistant has concrete references.
- Review the workflow monthly and remove permissions that are no longer needed.
Example first-week agenda
Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.
What to review before delegating
Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.
What should an IT virtual assistant handle first?
Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.
Get free IT support review