Access, recovery, and handover
Start with remote IT support NZ for triage, Microsoft 365 support NZ for account/admin recovery, or email security and recovery when suspicious mailbox access is involved.
Services
These pages are the "right starting point" for common SME problems. Each one is written to be usable by a business owner and precise enough to support future troubleshooting, provider escalation, and handover.
Service pages
Start with the page that matches your symptom. If the issue escalates into a provider, DNS, routing, or voice problem, the service pages link to the deeper technical notes and checklists.
Service lanes
Many SME problems overlap: an email issue might be Microsoft 365, DNS, mailbox recovery, or sender authentication. These lanes help you choose the right starting page before passwords, DNS records, devices, or provider tickets are changed.
Start with remote IT support NZ for triage, Microsoft 365 support NZ for account/admin recovery, or email security and recovery when suspicious mailbox access is involved.
Use Website setup/upgrades for inherited or underperforming sites, then pair it with the websites and search basics reading path for service-page, contact-path, and local visibility checks.
Use email deliverability support NZ for SPF, DKIM, DMARC, bounce, and spam-folder symptoms, or domains, DNS, and email when ownership and routing are unclear.
Use DNS and routing support for nameservers, TTL, propagation, MX/TXT records, partial reachability, or networking support when the problem crosses into fibre, VPN, SD-WAN, SIP, or VoIP.
Use IT support Christchurch for local support, computer repair Christchurch for troubleshooting, or laptop repair Christchurch when the issue is device-specific.
Use Christchurch web design and upgrades for practical site work, SEO consulting NZ for crawl/indexing basics, and websites and search basics for launch and handover checks.
Reading paths
If you prefer to work through a checklist first, these reading paths group related articles into a safe order.
Start with control points: registrar, DNS hosting, website routing, and email authentication.
Use when a site needs better metadata, canonical URLs, redirects, analytics, and post-launch checks.
Use when the main problem is access, admin control, device stability, and downtime reduction.
Use when support work involves mailbox access, MFA, phishing cleanup, recovery methods, or handover risk.
Use when the issue is a slow laptop, Windows problem, backup question, upgrade decision, or repair handover.
Use when faults sit between Wi-Fi, router, fibre, SIP, devices, provider settings, or handover notes.
Use when publishing a project site and you want clean canonicals, schema, and a useful proof backlink pattern.
Tools and handover
Service work is easier to maintain when the next check is written down. Use these tools and checklists after a support session, site launch, migration, or DNS/email change so the same issue does not quietly drift back.
Use the launch checklist for forms, redirects, analytics, sitemap checks, schema, mobile layout, backups, and post-launch verification.
Use the calendar for recurring checks across backups, renewals, DNS/email records, Microsoft 365 access, profile accuracy, and analytics.
Use the tools hub when the work needs a reusable checklist, planning aid, or maintenance reference rather than a one-off note.
Use this checklist when the service work touches canonicals, indexing, sitemaps, structured data, internal links, or Search Console validation.
Use this checklist when support work changes registrar access, nameservers, MX records, SPF, DKIM, DMARC, or provider handover notes.
Use the broad checklist when the job spans website, email, phone, account, networking, device, and documentation basics.
Related evidence
For current professional context, start with the About page. For public project notes, start with the Projects hub. For the working method behind small changes, use the practical technology systems note.