Know where to send a problem, where to chat with support, how to write a request that gets answered fast, and frequently asked for documents and how-to's.
Some content is still placeholder — swap in your FAQ link and chatbot URL when readyEverything on this page in one glance — click any button to jump straight there.
Get a quick answer from our IT assistant, or start a ticket directly.
Have a tech question? Chat with our Staff Longhorn Helpdesk!
Find the right help for the right technology — organized by support team and category.
| Student & Customer Systems | Network Access & Shared Folders | Software / Hardware | |
|---|---|---|---|
| UTHS Technology Support |
|
Network / Folders
|
Software
|
| LAITS Support |
— |
Network / Folders
|
Software
|
| UT Enterprise Technology Support |
— |
Network / Folders
|
Software
|
When emailing the technology support inbox at UTHSTechnology@austin.utexas.edu, include the following so we can resolve your issue as quickly as possible. Requests missing key details often need a follow-up email before we can even begin troubleshooting — including this information up front saves everyone time.
| Tag | When to use it |
|---|---|
| URGENT | Something is actively blocking instruction, testing, or a time-sensitive deadline (e.g., a class is happening right now and a tool is down). |
| ACTION REQUIRED | We need to do something specific (reset a password, grant access, fix a setting) but it isn't blocking anything this minute. |
| FYI | You're flagging something for awareness: no response or fix needed right now. |
Start your subject line with one of the tags above, followed by a short description.
If multiple people are on the email (e.g., cc'd staff, other techs), say clearly what you need and who needs to do it. Don't assume it's obvious from context.
Tell us exactly which platform is affected. "It's not working" could mean a dozen different things.
Include the full name and UTEID (or Skyward namekey) of every affected person. This is the single fastest way to speed up a ticket — without it, we often have to email back just to ask who you mean. If this affects a whole class or group, say so and (if possible) attach a roster of affected users.
Let us know which program this relates to, since some systems and permissions differ by program.
Please avoid forwarding a long email thread with only "See below" or "Please advise." Instead, write a short, self-contained summary at the top. Include: what error message (if any) are you seeing, what is your screen showing (or not showing), and what have you already tried.
Screenshots or screen recordings — especially for error messages, layout issues, or anything visual — tell us more in 5 seconds than several sentences of description. Always include the exact URL where the issue is occurring (e.g., the specific Canvas course link, the Skyward page, the Proctorio session link). Bold or clearly mark the link so it's easy to find in your email.
Before you hit send, confirm your email includes:
This will link out to the FAQ document.
Quick answers to common tech questions — link coming soon.