What to include in an IT support request

A useful IT support request explains what has stopped working, who is affected and what the business cannot do. You do not need to diagnose the fault or know the technical terminology. Clear observations help the support team choose the next step.

Start with the business impact

Explain whether one person, a department or the whole business is affected. Name the activity that has stopped: sending invoices, accessing shared files, taking orders or signing into a business system. Include any deadline and whether a safe workaround exists.

This helps an engineer understand urgency. It does not replace your agreed support arrangements or guarantee a particular resolution time. Read our guide to IT support response times for the difference between a response and a fix.

Use this support request checklist

• Contact: your name, business, callback number and availability.
• Location: office, home or another site, and whether you are using Wi-Fi, a cable or remote access.
• System: the device, application or service affected. Include an asset label if you have one.
• Symptoms: what you expected to happen and what happened instead.
• Timing: when it began, whether it happens every time and any recent change.
• Impact: affected people and the work that cannot continue.
• Evidence: the exact error message or a screenshot with sensitive information removed.
• Previous work: safe checks already completed and any earlier ticket reference.

Example of a clear support request

Subject: Shared files unavailable for the accounts team

Since 9:15am, three people in our Bury office cannot open the accounts folder. Email still works, but we cannot prepare today's invoices. The error says “Access denied”. We have not changed permissions. Our manager is available on the usual business number until noon. A screenshot with client details removed is attached.

This example describes observations and impact. It does not guess whether the cause is a server fault, an account problem or a permissions change.

What should you leave out?

Do not send passwords, recovery codes or multifactor authentication codes. Avoid attaching confidential customer records when an error message will do. Use the support route your business has agreed, and check any request for remote access if you are unsure who is asking.

For a suspected security incident, tell the support team immediately through the agreed incident route. Follow your organisation's security procedure and the team's instructions. Do not delay reporting while trying to produce a perfect screenshot or troubleshoot the incident yourself.

What if the issue is urgent or keeps returning?

For an urgent incident, use the escalation contact in your agreement and explain that work has stopped. Outside normal hours, use the out-of-hours route if your arrangement includes it. Sending the same request through several channels can make coordination harder; refer to the existing ticket when following up.

If a fault returns, include the earlier reference and describe what changed since the last fix. Keep a short record of dates, symptoms and affected users. Our guide to reactive and proactive support explains how recurring incidents can inform a longer-term improvement plan.

What should a useful support update tell you?

Ask what has been checked, the next action, who owns it and when you will hear again. If a workaround restores service, clarify whether further investigation remains. Before a ticket closes, confirm that the affected activity works and record any follow-up recommendation.

Looking for ongoing support for your business? Explore Tech Savvy Solutions managed IT support or talk to our team about your requirements.