As of 13 August 2026, AI can only partly fix your office Wi-Fi connection.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Ask the affected colleague or administrator whether the failure affects one device, several devices, or the whole office, and record when it began and the exact error message.
   2. Gather the device type and operating system, whether wired internet works, whether another approved device connects, and whether anything changed recently, without collecting passwords or network keys.
   3. Open the chatbot and paste the prompt, then add the facts you gathered with private addresses, usernames, customer information and credentials removed.
   4. Run only the low-risk tests the chatbot suggests, such as reconnecting to the approved network, moving near an access point, checking the device's IP status, and comparing another device or wired connection.
   5. Paste back the test results with sensitive values redacted, and ask the chatbot to update the likely cause and give the next single test rather than a list of unapproved network changes.
   6. Compare the proposed diagnosis with the working device, wired connection and outage evidence, then send the chatbot's evidence-based handover to the office IT administrator before changing router, access point, DHCP, DNS, firewall or security settings.
   7. After an administrator-approved fix, test the affected devices, a different user account if appropriate, internal systems and internet access, and record the change and outcome in the office support log.

   Prompt

   Act as a cautious office Wi-Fi troubleshooting assistant for a UK workplace. Do not claim to have accessed or changed any device, network, router, access point, switch, firewall or account. Do not ask for passwords, encryption keys, private customer data, full public IP addresses or other secrets. Do not recommend factory resets, disabling security controls, changing firewall rules, replacing DNS, or changing DHCP or wireless security settings without first explaining the risk and telling me to get approval from the network administrator.
   
   Guide me one step at a time. First ask for only the minimum facts needed: whether the problem affects one device or several, the device type and operating system, the Wi-Fi network name with any sensitive parts removed, when the problem began, the exact error, whether wired internet works, whether other devices work, and whether anything recently changed. Then suggest low-risk tests that I can run and report back, such as moving closer to the access point, reconnecting to the approved network, checking whether the device has an IP address, testing another approved device, and comparing Wi-Fi with wired access. For each test, state what result would mean and what to do next.
   
   Separate likely device, Wi-Fi radio, authentication, DHCP, DNS, access point, switch, firewall, ISP and service-outage causes. Give commands only for my stated operating system, explain what each command reveals, and tell me to redact credentials and sensitive addresses before pasting results. Never invent a network setting or present a guess as a diagnosis. Finish with a short evidence-based handover for the office IT administrator, including tests run, results, affected users or devices, time of failure, and the safest next action.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.