AI Prompts for IT Support

Help me with defensive cybersecurity support. Task: Build a suspicious-message evidence packet for authorized security review. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]; [anonymized suspicious message and observable warning signs]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with defensive cybersecurity support. Task: Create a device-loss reporting checklist grounded in company policy. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with defensive cybersecurity support. Task: Explain multifactor authentication choices without collecting recovery codes. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with defensive cybersecurity support. Task: Build a security-update prioritization discussion from official advisories. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with defensive cybersecurity support. Task: Draft a safe incident timeline using observable facts. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with defensive cybersecurity support. Task: Compare legitimate support contact with a social-engineering approach. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with defensive cybersecurity support. Task: Create a least-privilege access review using fictional roles. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with defensive cybersecurity support. Task: Compare password-manager recovery scenarios without exposing account secrets. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]; [fictional recovery scenarios and the password manager's official guidance]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with defensive cybersecurity support. Task: Build a checklist for reporting a suspected account compromise. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with defensive cybersecurity support. Task: Review a security claim for unsupported guarantees and missing scope. My inputs: [organization guidance]; [fictional or anonymized scenario]; [device context]; [response scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with account and access support. Task: Separate authentication failure from authorization denial. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with account and access support. Task: Create an account-lockout investigation note for authorized support. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with account and access support. Task: Explain role-based access using a fictional team example. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with account and access support. Task: Draft an access request with purpose owner and expiration fields. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with account and access support. Task: Build a joiner-mover-leaver checklist from organization policy. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with account and access support. Task: Compare a session-expiry issue with an invalid-credential symptom. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with account and access support. Task: Create a permissions-review table that flags excessive access. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with account and access support. Task: Explain recovery-channel checks without requesting verification secrets. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with account and access support. Task: Draft an escalation record for an inaccessible shared resource. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with account and access support. Task: Build a periodic-access-review checklist with accountable approvers. My inputs: [service name]; [anonymized error]; [user role]; [approved access policy]; [recent changes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with mobile device support. Task: Build a mobile-app crash record with reproduction and version details. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with mobile device support. Task: Compare mobile-data and Wi-Fi symptoms using the same application. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with mobile device support. Task: Create a notification-permission review without broad permission grants. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with mobile device support. Task: Plan a battery-use investigation from visible usage statistics. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with mobile device support. Task: Compare device-only and cloud-synced copies before proposing a mobile storage change. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]; [anonymized local file inventory and documented cloud-sync status]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with mobile device support. Task: Explain cloud photo synchronization separately from device backup. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with mobile device support. Task: Create an update-readiness checklist with a verified backup question. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with mobile device support. Task: Compare charging-device evidence without diagnosing unseen hardware. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with mobile device support. Task: Build a lost-device reporting plan from official organizational guidance. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with mobile device support. Task: Draft a managed-phone escalation note respecting admin restrictions. My inputs: [phone model]; [OS version]; [app version]; [exact symptom]; [managed-device policy]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with help-desk documentation and triage. Task: Turn a vague complaint into a reproducible support ticket. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with help-desk documentation and triage. Task: Create a triage matrix using impact and urgency separately. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with help-desk documentation and triage. Task: Build a ticket timeline showing actions results and owner changes. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with help-desk documentation and triage. Task: Draft a user update that explains progress without false certainty. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with help-desk documentation and triage. Task: Create a knowledge-base article from a verified resolution record. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with help-desk documentation and triage. Task: Compare a workaround with a root-cause fix in ticket notes. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with help-desk documentation and triage. Task: Draft an escalation package with the minimum useful evidence. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with help-desk documentation and triage. Task: Build a closure checklist that includes user outcome verification. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with help-desk documentation and triage. Task: Identify repeated-ticket patterns without exposing personal information. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with help-desk documentation and triage. Task: Create a post-incident review separating facts assumptions and lessons. My inputs: [anonymized ticket details]; [support policy]; [service scope]; [priority criteria]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with cloud file and collaboration support. Task: Separate link visibility from actual file permissions. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with cloud file and collaboration support. Task: Build a file-sync conflict investigation using version history. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with cloud file and collaboration support. Task: Create a shared-folder ownership review with expiry questions. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with cloud file and collaboration support. Task: Explain online-only files and local copies using service documentation. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with cloud file and collaboration support. Task: Draft a collaboration handover checklist that preserves access accountability. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with cloud file and collaboration support. Task: Reconstruct a file-conflict timeline to identify the authoritative version. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]; [file version history conflict timestamps and known edit ownership]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with cloud file and collaboration support. Task: Create an external-sharing review based on organization policy. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with cloud file and collaboration support. Task: Build a support note for an inaccessible shared document. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with cloud file and collaboration support. Task: Explain retention recycle-bin and version-history differences. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with cloud file and collaboration support. Task: Create a safe migration checklist including verification and rollback. My inputs: [service and version]; [anonymized sharing setup]; [error text]; [access policy]; [change history]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.