When small business IT support becomes a problem, the fastest fix is not always the first fix you find online. A safer approach is to confirm what changed, protect anything that still works and troubleshoot in a sequence that preserves recovery options.
Write down exactly what is failing, when it started and who is affected. Save the exact error message. Test from another device or connection where appropriate.
If a live business service is affected, consider web hosting migration before making broad changes.
Look for plugin or theme updates, password changes, DNS edits, hosting migrations, PHP upgrades, security rules or mailbox configuration changes. Use the timeline to narrow the investigation rather than assuming.
Before editing files, databases or DNS, confirm you have a usable backup or another recovery path. For security incidents, preserve relevant logs before cleanup.
Where compromise is suspected, AWS setup should consider credentials, vulnerable software and the original entry point, not just suspicious files.
Start with domain resolution, SSL, hosting response and account status. Then move into WordPress, plugins, the database and individual devices. This avoids troubleshooting the application when the fault sits elsewhere.
Record important settings, make one controlled change and test again. Multiple simultaneous changes make it difficult to identify what fixed or worsened the issue.
For infrastructure changes such as technical support, keep a short record of old and new values so rollback remains possible.
A homepage loading does not prove a website is healthy. Test forms, logins, checkout, inbound and outbound email, mobile access, SSL and other functions the business relies on.
Document the cause and recovery steps. Keep domain, hosting and email ownership clear, maintain backups and updates, and record DNS settings and important third-party services.
Also see Hacked WordPress Site and Microsoft 365 Mailbox Full for related checks and preventative steps.
Start with a map of who owns the domain, hosting, Microsoft 365 or Google Workspace tenant, DNS provider, website administrator accounts and other critical services. Record supplier contacts, renewal responsibility and recovery methods. This prevents a common support problem where nobody knows which account actually controls a service.
Document nameservers and important DNS records, including MX and email-authentication records. For email, record the platform, administrator account ownership, licence arrangement and any shared mailboxes or forwarding rules. Sensitive credentials should remain in an appropriate password manager rather than an ordinary shared document.
Good documentation should explain where backups are stored, how often they run, who can restore them and what to do if the primary administrator is unavailable. Include key website integrations and third-party services so a future technician can understand dependencies without discovering them during an outage.
Assign responsibility for reviewing the document after supplier changes, migrations and staff departures. Add a last-reviewed date so an engineer can judge whether information is current. The goal is not a huge technical manual; it is a concise map that lets an authorised person find the right system, owner and recovery path quickly when something fails.
For small business IT support, diagnose before repairing. Confirm the scope, protect recovery options, check recent changes, test systematically and verify the full service afterwards.
IT documentation often sits alongside wider operational and digital requirements. XGEN Group connects businesses with specialist engineering and digital service capabilities.