Technical Support Handbook

The role of technical support in web & IT environments

Technical support is the quiet infrastructure behind every web and IT project. Well-designed systems still fail if users cannot rely on their computers, networks or basic tools.

In the Dianthos approach, support work aimed to:

• Keep systems operating reliably for day-to-day business.
• Restore service quickly and methodically when problems occurred.
• Prevent recurring incidents through maintenance and improvements.
• Explain issues in a way that helped users feel informed, not powerless.

Support was treated as an essential part of engineering, not as an afterthought.

Defining scope, responsibilities & service levels

Clarity on what “support” includes prevents frustration. Before taking responsibility for systems, we aimed to define scope and expectations in simple terms.

Typical scope elements

• Devices: desktops, laptops, basic servers, printers and networking equipment.
• Software: operating systems, office suites, browsers, antivirus, standard utilities.
• Services: email accounts, internet access, shared folders and backups.
• Exclusions: unsupported legacy systems or specialised third-party software without access.

Service levels in practical terms

• Target response times for different incident types (critical vs. minor).
• Working hours and any emergency arrangements.
• Preferred contact channels and information required when reporting issues.
• Clear understanding of what is best-effort vs. guaranteed.

Even informal agreements benefited from a short written summary shared with all stakeholders.

Incident handling & troubleshooting method

Consistent troubleshooting reduces downtime and avoids random attempts that may cause further issues. Over time, a simple method proved effective in most situations.

Basic troubleshooting steps

• Clarify the symptom: what exactly happens, and since when?
• Check what changed recently: updates, new software, hardware moves.
• Isolate: determine whether the problem is local, network-wide or service-specific.
• Test hypotheses in controlled steps, documenting each one.
• Once resolved, confirm with the user and note the root cause where identifiable.

We encouraged users to describe errors precisely (messages, screenshots, timings) to improve the quality and speed of diagnosis.

Workstation & laptop support

A large portion of support work was centred on individual machines: desktops and laptops used in daily work. Problems here had immediate impact on productivity.

Typical activities

• Hardware diagnostics for disks, memory, power supplies and peripherals.
• Operating system installation, reinstallations (“format”) and upgrades.
• Driver installation and resolution of compatibility issues.
• Basic upgrades: RAM, storage, cooling improvements where feasible.
• Data migration between old and new machines.

A key practice was to separate user data from system files as much as possible, simplifying recovery and reinstallations when necessary.

Networks, connectivity & remote access

Network issues often appeared as “the internet is down” or “the system is slow”. Structured checks helped distinguish between local, provider and service-level problems.

Network support tasks

• Setting up and securing wired and wireless networks in offices and homes.
• Configuring routers, switches and basic firewall settings.
• Testing connectivity step by step: device → router → provider → external services.
• Resolving IP conflicts, DNS issues and basic routing problems.

Remote support

• Using remote desktop tools with user consent and clear procedures.
• Securing remote access with appropriate authentication and limits.
• Recording key changes made during remote sessions.

Clear diagrams of small networks, even informal ones, simplified future troubleshooting.

Preventive maintenance & backups

Many emergencies can be avoided with routine checks and a simple backup strategy. Technical support becomes much more effective when prevention is taken seriously.

Maintenance routines

• Periodic review of disk space, health indicators and system logs.
• Cleaning of temporary files and unnecessary startup programs.
• Physical cleaning of machines prone to overheating (dust, fans).
• Verifying that antivirus and security tools are active and updated.

Backups

• Identifying critical data: documents, databases, email stores, configuration files.
• Deciding on backup media and frequency appropriate to the organisation.
• Automating backups as far as possible to avoid human error.
• Testing restores regularly to confirm that backups actually work.

We considered backups successful only when restoration had been demonstrated at least once.

Security, malware & recovery

Security incidents range from mild (adware, unwanted toolbars) to severe (ransomware, data leaks). Technical support is often the first line of response.

Basic security practices

• Keeping operating systems and critical applications reasonably up to date.
• Using reputable antivirus and anti-malware tools, configured correctly.
• Encouraging strong, unique passwords and secure storage practices.
• Educating users about suspicious emails, attachments and links.

Handling infections and incidents

• Isolating affected machines from the network when necessary.
• Attempting cleaning only after assessing the severity and feasibility.
• Restoring from known-good backups when compromise was serious or uncertain.
• Documenting incidents and, where appropriate, recommending policy changes.

A conservative attitude (“better to restore than to risk hidden damage”) often saved time in the long run.

Tools, documentation & knowledge capture

Over years of support work, a small set of tools and documents proved repeatedly useful. The objective was to make solutions reproducible and not dependent on memory alone.

Typical tools

• Hardware diagnostics and monitoring utilities.
• Disk imaging and cloning software for deployments and recovery.
• Remote support tools with logging and secure access.
• Script collections for recurring tasks where appropriate.

Documentation practices

• Maintaining simple inventories of devices and key configurations.
• Recording Wi-Fi credentials, router access and service portals securely.
• Keeping brief “how-to” notes for recurring procedures.
• Storing documentation where it can be found quickly during incidents.

Even a modest, well-maintained knowledge base can significantly reduce resolution times.

User communication & local field work

Many support activities were carried out on-site, particularly in the wider Kalamata region. In such contexts, communication style and practical arrangements were as important as the technical work itself.

Communication principles

• Explaining problems and solutions in plain language, avoiding unnecessary jargon.
• Being honest about uncertainty and when further investigation was needed.
• Agreeing on next steps and, where possible, on estimated timeframes.
• Providing short, written summaries for significant interventions.

On-site support specifics

• Preparing checklists before visits to make efficient use of time.
• Testing solutions before leaving the site, with the user present.
• Noting follow-up actions that could be done remotely.

The aim was to build trust over time, so that users reported issues early instead of waiting until systems failed completely.