NZ SME tech checklist
A practical baseline: domains, email, backups, admin ownership, and "what to confirm before you pay for anything".
Local hub
A calm order to work through common SME website and email problems without needing technical vocabulary. This page links to the most useful reading paths and checklists already published on this site.
Start here
If you are dealing with a real incident or a time crunch, a short reading path beats a long theory doc. These pages are designed to be scanned, acted on, and shared internally without handing over account credentials.
A practical baseline: domains, email, backups, admin ownership, and "what to confirm before you pay for anything".
Launch hygiene, site structure, and search basics, without marketing fluff or ranking promises.
Control points and safe change workflow: registrar ownership, DNS, SPF/DKIM/DMARC, and simple deliverability checks.
Incidents
Treat mailbox takeover like a containment problem first. Then check for persistence (forwarding, rules, delegates, third-party app access).
A reading path: reset access, remove persistence, verify admin control, then recover deliverability.
First 15 minutes, same-day clean-up, and prevention baseline for NZ SMEs.
Support notes for tenant control, MFA recovery, admin ownership, and safe handover.
Reliability
Many "email problems" are really connectivity or DNS problems. These checklists focus on evidence and reversible steps.
Where to look first: router, Wi-Fi, ISP issues, VoIP basics, and sensible escalation.
A step-by-step checklist for dead zones, interference, and speed reality checks.
Common causes, evidence to capture, and safe "try this before you call support" steps.
Local footprint
The goal is a clean local footprint that matches reality: consistent entity details, predictable contact methods, and pages that help customers understand what you do.
How to keep names, addresses, phones, and profiles consistent without chasing gimmicks.
What this site covers: practical IT support, websites, DNS/email, and SME reliability work.
Local service notes and safe engagement boundaries (backup-first, documentation-first).
Safety
A lot of recovery work is slowed down by accidental data leakage. These notes help teams share context safely.
Practical boundaries: passwords, MFA codes, private keys, invoices, customer lists, and account recovery details.
How this site treats contact messages and privacy-sensitive information.
If a checklist finds a real problem, send a short summary and keep credentials out of the message.