JAMES BALATTI · PERSONAL TECH SUPPORT

James Balatti • James.Virtual.Support

Technology support.

Hands-on help with the systems your business depends on, from hosting and email to day-to-day operations.

I can help you work out what’s broken, what needs regular upkeep, and where a better workflow would save time.

Working in Lillooet, British ColumbiaDecember 2026 and January 2027. Vancouver-area work by appointment only. Availability is confirmed individually.

01 / Capabilities

What I can help with.

Use these as starting points. If the issue crosses several systems, we can trace where the problem starts before committing to a fix.

01 / INFRASTRUCTURE

Systems & network administration

Diagnose device, server and network problems and document the systems people rely on.

  • Connection, Wi-Fi and access troubleshooting
  • Configuration review, system inventory and handoff notes

02 / WEB HOSTING

Linux, cPanel & WHM

Work through hosting issues and plan changes with backups and rollback in mind.

  • Account setup, hosting checks and migration planning
  • SSL, resource use and backup or restore readiness

03 / WEBSITES

WordPress maintenance

Keep sites running and deal with failures after updates or configuration changes.

  • Core, theme and plugin maintenance
  • Backup review, staged changes and recovery coordination

04 / DOMAINS & COMMUNICATION

DNS & business email

Trace problems across the domain, hosting provider and mailbox service.

  • DNS records, domain moves and email configuration
  • Mail delivery, SPF, DKIM and DMARC review

05 / WHEN THINGS BREAK

Incident coordination

Record what happened, prioritize the impact and coordinate next steps across owners and providers.

  • Scope the issue and keep a timeline of decisions
  • Plan recovery, verify service and document follow-up

06 / BUSINESS OPERATIONS

Practical AI & workflow support

Identify repeatable work worth simplifying and keep people in control of important decisions.

  • Start with one workflow, such as intake or status updates
  • Prototype with sample data and build in review before rollout

02 / Working together

Before any change.

We agree on what I can access, who approves a change, and what success looks like. For changes that could interrupt service, we agree on a maintenance window and a way back first.

Keep access details private.

Do not put passwords, private keys, recovery codes, payment details or customer records in a project brief. If access is needed, agree on a secure method, limit access to the work, and remove it when the work is complete.

03 / Project checklist

What to prepare.

Use this list to make a short brief for a first conversation. Email a short project summary to start a conversation. An enquiry does not reserve time.

  • What isn’t working or what you want to improve, in your own words.
  • When it started, who’s affected, and whether anything changed first.
  • The relevant platform or provider, if known, and what you’ve already tried.
  • Your deadline, time zone, and whether remote or on-site support would help.

Scope, price and timing are agreed directly before work starts. An enquiry is not an appointment.

Ask about a support project

Tell me what you need help with and your general location. Please don’t send passwords or private records.

Email a support enquiry