AI prompts for event audio-visual technicians

I work in event audio-visual technical support. Help me create one ticket summary that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Create a structured ticket summary from a user report so it can be routed without extra back-and-forth.

Source material:
Ticket #4417 came in through the chat widget at 8:52 this morning: "Hey, this is Marcus in Receiving -- I can't log into the purchase-order portal, it just spins on the loading screen and then kicks me back to sign-in. I tried it on my phone too, same thing. I've got a PO for the forklift parts that has to go out before the 11am cutoff or the vendor cancels the order. Can someone look at this before then?" The queue also shows two other open tickets mentioning the purchase-order portal timing out since 8:30 -- one of them from Denise in Shipping.

Return only the finished work:
ticket summary

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one outage update for the Denver floor that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Write one plain-language outage update that says what's affected, what's being done about it, and what people should do right now instead of re-reporting it one at a time.

Source material:
"Hey — got off a call with facilities. VPN's been dropping every eight or ten minutes for the whole Denver floor since about 7:40 this morning, ticket #4412 already has six people piled onto it. Networking's pretty sure it's the firewall rule that went in overnight, still confirming. Nobody's lost any files, this is just getting kicked off the VPN and having to log back in, but Danielle at the front desk has pinged the IT chat four times already asking if this is showing up somewhere. My manager wants a note out to the floor by 9 so people stop re-reporting it one at a time. Can you get that written up?"

Return only the finished work:
1. outage update for the Denver floor
2. what's causing it
3. what to do right now instead of re-reporting it

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one user-friendly explanation with step list that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Draft a user-friendly explanation and step list she can follow on her own.

Source material:
"Dana Okafor in AP (ticket #4523) can't get into the shared invoicing drive, throwing Access Denied (0x80070005) every time she tries to open it from her mapped drive. I found stale cached credentials in Credential Manager under Windows Credentials -- that's what's blocking her. Fix is: open Credential Manager, remove the old entry for the finance file server, disconnect and remap the drive, then sign back in with her normal network login. She's not technical at all, so I need something she can follow herself without calling back, plus a line on what NOT to try (don't have her mess with sharing permissions or hand out her password to anyone) and when to just open a new ticket instead of pushing through it."

Return only the finished work:
user-friendly explanation with step list

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one triage table with escalation recommendation that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Create a triage table and escalation recommendation for the tickets in this handoff.

Source material:
"Handing off the queue before I log off tonight -- ticket #4501, Nadia in Finance is locked out after three bad password attempts and she's got a wire approval due at 9am tomorrow. Ticket #4422, the shared network printer on the 3rd floor near Ops has been down since 1pm and four people have pinged me about it. Ticket #4429, someone on the remote sales team can't reach the VPN, and I just got a chat message that two more people on that team are seeing the same thing. Ticket #4431, Derek in Marketing clicked a link in an email that turned out to be a phishing test he wasn't supposed to click, and he's asking if his laptop needs to be wiped. Give me a rundown of what to jump on first."

Return only the finished work:
triage table with escalation recommendation

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one knowledge base draft that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Turn a resolved help-desk ticket into a knowledge-base article another support tech can follow.

Source material:
"Closing out #4544 -- Priya Chandrasekaran (Finance, 3rd floor) couldn't get the video-call app to pick up her headset after Tuesday's Windows update pushed to her laptop. Turns out the update reset the default audio input back to the laptop's built-in mic, and the app's microphone permission under Windows privacy settings had flipped off too. Fixed it by resetting the input device inside the app's audio settings and re-enabling the app permission, then had her fully quit and reopen the app -- closing the window alone didn't make the permission change stick. Took about twenty minutes. This is the third ticket like this since Tuesday's patch went out, so we should probably get a KB article up before it turns into ten more."

Return only the finished work:
1. knowledge base draft
2. applies-to section
3. step-by-step fix

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one structured diagnostic flow that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Build a structured diagnostic flow for recurring "email works, ERP app doesn't" tickets like Talia's #4482, Ruben's #4465, and Nora's #4471.

Source material:
"Talia Reyes in Accounting (ticket #4482) says email's fine but the Meridian ERP app won't load. On the browser she gets a red 'session expired' banner right after login, but the desktop client just spins on 'Connecting...' and never actually errors out. She thinks she's on VPN but wasn't fully sure when I asked. This is the third ticket like it this week -- Ruben's #4465 had the same browser/desktop split, and Nora's #4471 cleared itself after a reboot before we ever figured out why. Can you build something the whole desk can run through so we're not all improvising different questions every time?"

Return only the finished work:
structured diagnostic flow

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one reusable support-triage prompt that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Build a reusable triage prompt that sorts incoming support tickets like this one into categories, flags anything that needs escalation, and gives safe next steps without exposing sensitive details.

Source material:
"Leah Bennett on the claims team just opened ticket #4577 -- she says she can't get into the shared drive for the Meridian account, keeps throwing 'access denied,' and she's on a deadline to send the reconciliation packet by 3pm. She also pasted her whole error screenshot into the ticket notes, which includes her username, her manager's name, and what looks like a partial account number from a customer record. Two other people on her team, Griffin and Sam, are apparently locked out of the same drive too, but only Leah opened a ticket. I need something I can hand to whoever's on triage today that sorts this the right way without repeating any of that sensitive stuff back verbatim."

Return only the finished work:
reusable support-triage prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.

I work in event audio-visual technical support. Help me create one service desk metrics plan that I can review and edit before use.

Relevant context:
- Role: Event Audio-Visual Technician
- Work context: You run cue-to-cue with a stage manager an hour before doors, write the equipment list for a client who keeps changing the room layout, and explain to a panicked planner why the livestream feed dropped mid-keynote.

Task:
Build a metrics plan that shows whether AI-assisted ticket replies are actually accurate and safe, not just faster, before Jonas presents to the director.

Source material:
"Hey -- we're six weeks into letting tier-1 lean on Copilot for ticket replies, and I need real numbers before Thursday's director meeting. My gut says it's working, Wren's open queue dropped from 40 to 22, but I've also caught two replies that told users to just disable their antivirus, and ticket #48211 got reopened four times because the AI's fix didn't match our actual VPN setup. I don't just want 'are we faster,' I want 'are we accurate and safe.' Put something together I can hand to the director Thursday."

Return only the finished work:
service desk metrics plan

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.