A support ticket gives you and the support team one shared place to track a request from beginning to end. It keeps messages, troubleshooting notes, scheduling, actions taken, and resolution history together so everyone knows what has already happened and what needs to happen next.
It also provides support continuity. If the original support engineer is unavailable, another qualified engineer can review the ticket history and determine how to continue.
The process is intentionally simple: Submit → Confirm → Assign → Work Together → Resolve → Close
You do not need to understand the ticketing system to get great support. Use the option that best matches what you need.
| What You Need | Best Next Step |
|---|---|
| Help right now | Call first, regardless of priority. |
| You have new information, the priority changed, or you want an update sooner | Reply to the existing ticket or call. |
| You want a scheduled time to work with support | Book a support appointment. |
| The support team needs something from you | Reply with the requested information, access, approval, testing result, or decision. A short response is often enough. |
| The request appears stuck or needs different expertise | Ask for an update or request escalation. |
| The ticket was closed but you still need help | Reply to the closure email or call. Support can continue. |
Business users can contact the support team using phone, email, the IT Support Panel, and other approved support methods. The best method depends on how quickly you need help and how you prefer to communicate.
If you want help as quickly as possible, calling is always the best first step regardless of the request’s priority. You can call the support desk 24 hours a day, 7 days a week to create a ticket, continue an existing request, request an update, or ask for assistance from a support engineer. This is especially important for urgent, time-sensitive, or downtime-related requests, but you do not need to wait for an issue to become urgent before calling.
Email works well when immediate assistance is not needed and you prefer to send the request for review. Email requests are processed Monday through Friday, 7:00 AM to 7:00 PM Central Time. Requests received outside these processing hours are reviewed the next business day.
Simple rule: If you want support right now, call. If the request can wait for normal processing, email is perfectly fine.
When you email the support team, an automated confirmation is sent back immediately.
The confirmation normally includes:
Take a quick look at the confirmation. If something is incorrect or you forgot an important detail, simply reply to the ticket email. Your reply is automatically added to the same ticket so the communication and history stay together. There is no need to create another request.
Your ticket number makes it easy for any support engineer to locate the request. If you call and do not have the ticket number, that is okay. After validating your identity for security purposes, the support engineer can look up your request.
During normal email processing hours, a dispatch lead reviews incoming requests and routes them to the appropriate support engineer or Managed IT Department team. Depending on the team, you may receive another automated update letting you know that the request has been reviewed and is now in the hands of the appropriate support resource. This helps you understand that the request has moved from received to assigned for support.
You do not need to understand every Managed IT Department team before asking for help. Sending a request to the support team is always okay, and dispatch can route it to the correct resource. If you already know the correct team or request path, using it can reduce handoffs and help the request get started faster. Requests sent to the wrong team can still be routed, but additional coordination may add time. If your organization would like help understanding the different teams and common request paths, contact your account manager.
The assigned support engineer reviews the information already provided and contacts you as needed. This may happen by phone, email, a scheduled support appointment, or another approved communication method. When the engineer is actively working on the request, the ticket may be placed into an In Progress status. The engineer continues working until the request is completed or something else is needed before work can continue.
Some requests need different expertise or additional resources. When appropriate, the support engineer may escalate the request to another engineer, a higher support tier, a specialist, or another Managed IT Department team. You can also request escalation if the request appears stalled, becomes more urgent, or needs additional expertise. Escalation does not mean starting over. The ticket keeps the history together so the next engineer or team can see what has already been done and continue from there.
You are always welcome to contact the support team while a request is open.
You can:
You should not have to manage the support ticket yourself. The support team is responsible for managing the workflow, documenting the work, communicating next steps, following up when appropriate, and escalating when needed. Your participation is important when the request needs something only you or your organization can provide. This may include information, access, testing, approval, scheduling, or a business decision. If you want an update sooner, have new information, or need help right now, simply reply or call. This gives you more control over the support experience without making you responsible for managing the ticket.
Support manages the ticket. You help keep the request moving when your information, access, availability, approval, or decision is needed.
The goal is simple: clear communication, clear ownership, and the right people involved at the right time.
You do not need to manage ticket statuses yourself. They simply tell the support team and ticketing system what needs to happen next.
| Status | What It Means | What Happens Next |
|---|---|---|
| In Progress | A support engineer is actively working on the request. | Work continues until the request is completed or something else is needed. |
| Waiting on User Response | The support team needs information, confirmation, or an action from the end user. | Follow-up reminders may occur until the user responds. |
| Waiting for Schedule | A support appointment has already been booked. | Normal no-response reminders stop while everyone waits for the appointment. |
| Waiting on Vendor, Shipping, Parts, or Another Dependency | The next action depends on something other than the end user. | The ticket remains waiting without normal user-response reminders. |
| Resolved | The request has been confirmed as fixed, completed, satisfied, no longer needed, or otherwise resolved. | No additional action is currently needed. |
| Resolved (No Response) | The support team could not receive the response needed to continue after repeated attempts. | The ticket closes for tracking, but the user can reply or call if help is still needed. |
Simple logic: Ticket statuses keep active work, scheduled work, waiting work, completed work, and unanswered requests organized correctly.
Missed calls can slow down even simple requests. If your schedule is busy or difficult to predict, scheduling the support session is often the easiest solution. Support Desk and Operations team members commonly provide booking links, although availability varies by team. If a booking link is not included, simply ask for one. Choose a day and time that works for you. Once the appointment is booked, the ticket is placed into Waiting for Schedule. Normal no-response automations stop while the ticket waits for the scheduled appointment because everyone already knows when the next action will occur.
Keep missing each other? Ask for a booking link and choose a time that works for you.
Not every open request requires immediate action from you or the support engineer.
A ticket may be waiting for:
These tickets are placed into the appropriate waiting status and are not treated as unanswered requests while the support team knowingly waits for the next step. This prevents unnecessary reminders while keeping the ticket and its history organized.
Sometimes an engineer needs information, approval, access, testing, confirmation, or another action from the end user before work can continue. The engineer first makes reasonable attempts to contact you using methods such as phone, email, voicemail, and sometimes SMS when appropriate. The engineer then sends a direct follow-up explaining what information or action is needed to move forward. If there is still no response, the ticket is moved to Waiting on User Response. This begins the automated follow-up process.
| Stage | When | What Happens |
|---|---|---|
| Engineer Follow-Up | When your response is needed | The engineer explains what information, confirmation, or action is needed. Contact may include phone, voicemail, email, and sometimes SMS. |
| Follow-Up #1 | Approximately 3 business days later | If there is still no response, an automated reminder is sent. |
| Follow-Up #2 | Approximately 3 additional business days later | Another reminder is sent if the support team still needs your response. |
| Final Closure | After the follow-up process | A final email is sent and the ticket is closed as Resolved (No Response) if the needed response is still not received. |
At any point during this process, simply reply to the ticket or call the support desk. Once you respond, the no-response process stops and the support team can continue with the request.
Your response can be very simple. Tell us “I still need help” or “This is resolved.” You do not need to write a long response just to keep the ticket moving.
This distinction is important because both statuses close a ticket, but they do not mean the same thing.
A ticket can be marked Resolved when the end user, support engineer, or both have confirmed that no additional action is currently needed.
This can include situations where:
For example, if an engineer completes the work during a live support session and the end user confirms the request is satisfied, the ticket can be resolved immediately.
Resolved (No Response) means the support team needed a response, confirmation, information, or action to continue and could not receive it after the engineer’s direct follow-up and automated follow-up sequence. It does not mean the support engineer independently confirmed that the problem was fixed. Without communication, the support team cannot determine whether the request was successful, unsuccessful, still needed, or no longer needed. The ticket is therefore closed for service-desk tracking until the end user is ready to continue.
Resolved (No Response) does not mean we confirmed the problem was fixed. It means we could not receive the response needed to continue. If you still need help, reply or call.
Keeping completed or unanswered tickets open indefinitely actually makes support harder to manage. Clean ticket closure helps the support team understand which requests are actively being worked, waiting on users, scheduled, waiting on another dependency, successfully completed, or unable to continue because communication stopped. These results also help measure the overall support experience. For example, Repeated Resolved (No Response) tickets may identify a communication or engagement pattern worth reviewing. The purpose of closure is not to prevent anyone from receiving help. It keeps active work clear, maintains accurate service history and statistics, and helps the support team focus attention on requests that are ready to move forward.
Ticket closure is not a barrier to support. If you still need assistance, reply to the closure email or call the support desk.
This is intentionally easy. Reply to the closed-ticket email or call the support desk. The closure email includes instructions for continuing the request if additional help is needed. If the ticket was closed within the previous 7 business days, the original ticket can be reopened and is tracked as a Reopened ticket. The previous messages, notes, troubleshooting, and work stay together so the support team can continue from the existing history. After seven business days, the original ticket remains closed and cannot be reopened. A new ticket is created for the new support activity, and the previous ticket can be linked to it so the support engineer still has the earlier history. This keeps new work separate from older completed work so ticket age, resolution time, reopened-ticket activity, workload, and other service statistics accurately reflect the support experience.
Within 7 business days: Reopen the same ticket.
After 7 business days: A new ticket is created and the previous history remains available for continuity.
Out-of-office situations are handled based on the request, account, availability, and urgency. Depending on the situation, the support team may continue waiting for the end user, place the ticket into an appropriate waiting status, contact the client’s IT Point of Contact for direction, or close the request until the employee becomes available again. For example, an out-of-office response showing that an employee will be unavailable for an extended period may be handled differently for a normal request than for a critical issue. The goal is to keep the service desk accurate while making sure important work does not get lost.
A support ticket belongs to the support process, not just one engineer. Support engineers document the original request, previous communication, troubleshooting, actions already taken, current status, and what needs to happen next. If your original engineer is unavailable and you need help now, do not wait for that specific engineer. Call the support desk so another qualified engineer can review the history and determine how to continue. If the request is not being resolved in a reasonable amount of time or needs different expertise, the engineer may escalate it to another engineer, another support tier, a specialist, or another team. You can also request escalation when needed. The ticket history helps that escalation happen without unnecessarily starting over.
Not every organization wants to interact with IT the same way. Start with the simplest option that works well, and add more structure or onsite involvement only when it improves the experience.
| If This Sounds Like Your Team… | Consider | Why It Helps |
|---|---|---|
| Email works, but managing all the messages is frustrating | IT Support Panel | A cleaner way to view and manage support requests. |
| Your team prefers regularly talking through open requests and decisions | Short Working Meetings | Creates a predictable time to remove roadblocks and make decisions. |
| Remote meetings are not enough and face-to-face interaction helps engagement | Scheduled Onsite Visits | Adds periodic in-person coordination and accountability. |
| You need regular local help or someone physically available | Internal IT Point of Contact | Provides local “boots on the ground” while remaining connected to the broader IT Department. |
| You already have internal IT but need more coverage, expertise, capacity, or structure | Co-Managed IT | Combines internal IT with additional people, teams, tools, escalation, and coverage. |
Email works well for many people, but it can become noisy when several tickets, replies, notifications, and automated messages are involved. If keeping up with support emails is difficult, use the IT Support Panel. The IT Support Panel provides an easier, faster, and less noisy way to view and manage support requests without sorting through long email conversations. You can still call whenever you want immediate assistance or simply prefer to speak with someone directly.
Some leaders and teams simply prefer talking through technology requests with a person instead of managing everything through tickets, email, or other technology. In these situations, short video working meetings can be very effective.
These meetings often last only 5 to 15 minutes and focus on practical items such as:
The goal is not to create another unnecessary meeting. The goal is to create a short, predictable opportunity for the IT and non-IT teams to communicate, make decisions, and remove roadblocks. Working meetings do not replace tickets. Important requests, decisions, actions, and follow-up work should still be documented in the ticketing system so the history remains available to the entire support team.
Working meetings should become less frequent as communication, progress, operational smoothness, and satisfaction improve on both sides.
A typical progression is: Weekly → Bi-Weekly → Monthly → Every Other Month → Quarterly Working Meeting → Quarterly Strategic Review
If weekly meetings are consistently short, there are few open decisions, and both sides feel that communication is working well, move to bi-weekly. Continue reducing the frequency as the environment becomes smoother and more predictable. Eventually, separate working meetings may no longer be needed and can be replaced by the normal quarterly strategic review with your vCIO focused on budgeting, planning, IT strategy, risk, and upcoming business needs.
The best meeting cadence is the least frequent cadence that still keeps communication, decisions, and progress healthy.
Remote support and video meetings are normally the fastest and most efficient way to communicate and coordinate ongoing IT work. However, some organizations benefit from a scheduled onsite cadence (weekly/bi-weekly/monthly/quarterly/bi-annually/annually).
This is most common when:
Scheduled onsite visits are typically a paid service because they require dedicated travel and onsite time. They are generally not needed when remote support and short video meetings are working well, but they can provide another option when an organization benefits from a more traditional in-person experience. Onsite visits still use the same ticketing and documentation process so actions, decisions, and follow-up work remain visible to the full support team. Please contact your account manager for scheduling options, availability, and costs.
Some organizations want or need technology support physically onsite more regularly or every day. In that situation, an internal Level 1 IT Point of Contact (IT POC) can serve as the organization’s “boots on the ground.” This person can help with employee coordination, basic troubleshooting, equipment setup and handling, physical checks, inventory, and other tasks that benefit from local presence. The internal IT POC does not necessarily need to be a senior engineer or IT director. Someone with good technical instincts, strong communication skills, and the ability to follow established processes can often be a great fit. More advanced responsibilities such as cybersecurity, infrastructure, backups, projects, engineering, and IT strategy can continue to be handled by the Managed IT Department.
The IT POC does not always need to be a full-time IT position. Depending on the organization, this responsibility may be full-time, part-time, or assigned to an existing employee who has dedicated time each day to work with the IT Department. Even 30 minutes to 4 hours of dedicated time per day can be helpful when it is used consistently to review open tickets, coordinate onsite needs, complete assigned tasks, and discuss priorities with IT Department leadership. For organizations with enough ongoing work, a full-time role can also work very well. Because the employee remains connected to a larger IT Department for escalation, engineering, standards, projects, and support, they do not have to operate as an isolated solo IT resource. The right amount of time should be based on actual workload. Reviewing open tickets and expectations with IT Department leadership is the best way to determine whether the role should be part-time, shared with another position, or full-time.
The internal IT POC should use the same ticketing, documentation, security, and change-management processes as the Managed IT Department. This keeps the history together, makes ownership clear, and allows the internal IT POC to easily escalate a request when another engineer, support tier, or team is needed. The goal is simple: provide helpful onsite presence without creating a separate IT process or requiring one person to solve everything alone. If your organization is considering an internal IT POC, your account team can help define responsibilities, ticket ownership, communication expectations, escalation paths, and the amount of dedicated time that makes sense.
A solo IT professional or established internal IT department can work alongside the Managed IT Department through a co-managed IT model. Co-managed IT is flexible. The Managed IT Department may cover routine support, monitoring, cybersecurity, backup checks, after-hours coverage, or other operational tasks so internal staff can focus on higher-impact projects and strategy. Or, internal staff may handle the day-to-day work while using the broader IT team for advanced engineering, projects, specialized skills, escalation, training, or additional coverage when needed. It can also provide valuable support during vacations, sick days, staff transitions, heavy workloads, or situations where the internal team simply needs another engineer, specialist, support tier, or team to help move a request forward.
The same ticket workflow remains important. Internal IT and the Managed IT Department should work from shared tickets, documentation, standards, and escalation processes so everyone can see what has already happened, who owns the next action, and when additional help is needed. The goal is not to create separate “internal IT” and “external IT” groups. The goal is to create one coordinated IT team with clearly defined responsibilities and a shared support process. If your organization already has internal IT staff, your account team can help define responsibilities, coverage, escalation paths, and communication expectations so both teams complement each other instead of duplicating work.
The tools, ticketing system, meetings, engineers, cybersecurity systems, and processes all matter. But one of the strongest indicators of a successful IT relationship is much simpler: ongoing engagement. This applies whether the IT department is internal, external, or a combination of both.
The relationship is straightforward: Less engagement → Less communication → Fewer decisions → Slower progress → Lower satisfaction
When important decisions are delayed or communication repeatedly stops, technology work slows down. Over time, unresolved work and delayed decisions can contribute to unnecessary risk, downtime, recurring problems, or other operational issues.
The opposite is also true: Good engagement → Clear communication → Faster decisions → More progress → A better IT experience
Engagement does not mean attending unnecessary meetings or spending large amounts of time managing IT. It means responding when a decision is needed, communicating when something is not working, confirming when something is resolved, and choosing the support method that works best for your organization.
The goal is not more IT interaction. The goal is enough communication and engagement to keep decisions, support, projects, and improvements moving forward.
Leadership has an important role in helping employees understand how to get fast and effective IT support. The support process works best when the same simple expectations are reinforced across the organization.
| Leadership Habit | Why It Helps |
|---|---|
| Encourage employees to call when they want help right now. | Calling is the fastest way to engage the support team regardless of priority. |
| Respond when the support team needs information or a decision. | Even a short response can prevent a ticket from becoming stuck. |
| Schedule support when employee availability is difficult. | Booked appointments reduce repeated missed calls and unnecessary delays. |
| Keep related work in the existing ticket. | The support team can see the complete history instead of piecing together separate requests. |
| Do not wait for one specific engineer when help is needed. | Another qualified engineer or support tier can review the ticket and continue when appropriate. |
| Encourage escalation when a request appears stuck. | Escalation brings in another engineer, specialist, tier, or team when different expertise is needed. |
| Use the IT Support Panel when email becomes difficult to manage. | Employees have another simple way to view and manage their requests. |
Leadership does not need to manage individual IT tickets. The goal is to reinforce a few consistent habits so employees know how to ask for help, respond when action is needed, and keep requests moving. When leadership supports the process, employees engage more consistently, communication improves, and the IT Department can resolve work more predictably.
Yes, if you want the fastest assistance available right now. Calling is the fastest way to reach the support team regardless of priority. Email remains a convenient option when immediate help is not needed.
Yes. You do not need to create another request. Provide the ticket number if you have it. If you do not, the engineer can locate the request after validating your identity.
Yes. Replies are automatically tracked inside the existing ticket.
Absolutely. You can reply to the ticket or call at any time. If you want help right now, calling is the fastest option.
You do not need to follow up just to make sure your ticket is being managed. The support team is responsible for ownership, documentation, next steps, follow-up, and escalation when needed. Your participation is most helpful when the request needs something only you or your organization can provide. This may include information, access, testing, approval, scheduling, or a business decision. You are always welcome to call or reply if you want an update sooner, have new information, your priority changes, or you need help right now. Following up gives you another way to stay engaged and move faster when needed. It is not required for the support team to manage your ticket.
Yes. You can request escalation if a request appears stalled, becomes more urgent, or needs additional expertise. The support engineer may also escalate the request when another engineer, support tier, specialist, or team is better suited to complete the work.
Ask for a booking link and schedule a support appointment. Once the appointment is booked, the ticket is placed into the appropriate scheduled status and normal no-response reminders stop while everyone waits for the appointment.
The support engineer likely needs information, confirmation, or an action from you before work can continue. Reply to any of the ticket messages or call support to continue.
The support team needed a response or action to continue but could not receive one after repeated attempts. This does not mean the engineer independently confirmed that the issue was fixed. If you still need help, reply or call.
No. Ticket closure keeps the service desk organized. Reply or call if you still need assistance. The same ticket can normally be reopened within seven business days. After that, a new ticket is created and the previous history remains available for continuity.
Yes. The ticket contains the support history so another qualified engineer can review what has already happened and determine how to continue whenever possible.
Use the communication method that works best for your organization. Short video working meetings, scheduled onsite visits, or an internal IT Point of Contact can all be considered when additional human coordination or onsite presence would improve the experience.
