IT. On Autopilot.

Ask us about Charts, numbers and attention lists

Dashboard & AI

Charts, numbers and attention lists

Explore health, alerts, patch trends, online devices, performance, warranties and certificates. Widgets show when readings were taken.

Read the full explanation

What it does

Turn collected device information into a picture you can read quickly. Summary figures show the scale of the environment, charts reveal patterns over time, and attention lists bring the specific computers or tasks needing a closer look into view.

How you can use it

Useful figures. Keep device counts, connection state, health, alerts and open work visible, alongside the available update, warranty and certificate information.
Trends over time. Compare health and performance readings across the chosen period. A trend helps distinguish a recurring problem from one unusual sample.
From overview to investigation. Use attention widgets to move from a headline to the relevant device, alert, incident or approval, with the surrounding context still available.

In practice

A business sees several computers needing attention, opens the affected device list and discovers that the main concern is pending updates rather than a widespread hardware fault.

Controls & availability

The dashboard shows the timing and coverage of its evidence. Offline computers and missing samples do not silently become reassuring green figures.

Ask us about Action widgets & notes

Dashboard & AI

Action widgets & notes

Keep shortcuts to the work queue, device checks, runbooks, Wake-on-LAN and AI close by, alongside your own notes.

Read the full explanation

What it does

A useful dashboard should help you do the next piece of work as well as understand it. Action widgets bring common destinations and supported tasks into the workspace, while notes keep the local context close to the figures.

How you can use it

Practical shortcuts. Put links to the work queue, diagnostic checks, reviewed runbooks, Wake-on-LAN and Vycko AI where they are easy to find.
Notes in context. Keep reminders about a customer, a planned change or a handover alongside the dashboard you use for that work.
Flexible placement. Move and resize these widgets with the rest of the dashboard, making room for a longer note or bringing a frequent action nearer the top.

In practice

A support team keeps a note about a planned office move next to the affected customer’s overview, with shortcuts to device checks and the upcoming automation calendar.

Controls & availability

A shortcut does not grant extra permission. Any action it starts still follows the same customer rules, approval requirements and stop controls as elsewhere in Vycko.

Dashboard & AI

Vycko AI

Ask about a device or an incident. Bring evidence, proposed repairs and follow-up questions into a practical conversation.

Read the full explanation

What it does

Ask a practical question about a computer or an incident and work through the evidence in a conversation. Vycko AI helps connect symptoms, diagnostic results and possible next steps, keeping the investigation attached to the device or support task.

How you can use it

Evidence-led investigation. Bring available device readings, diagnostic checks and incident context into the discussion. Ask follow-up questions when an explanation needs more detail.
Proposed repairs. Review what the AI suggests changing, why it is relevant and what evidence supports it. Supported actions use the platform’s repair and approval workflow.
Progress and handoff. Follow the investigation, action results and verification. When a request needs a technician or a capability is unavailable, that gap remains visible.

In practice

A home user reports that printing has stopped. The support team uses Vycko AI to inspect the relevant service and events, review a proposed repair and check whether printing recovers.

Controls & availability

AI access is scoped to permitted customers, devices and tools. Configured rules determine whether it can observe, request approval or carry out an allowed repair.

Ask us about Vycko AI

Ask us about AI screen assistance

Dashboard & AI

AI screen assistance

Allow screen-based investigation within configured permissions, consent and stop controls. Remote changes stay accountable.

Read the full explanation

What it does

Some problems need the screen as well as background diagnostics. Within its configured access, Vycko AI can use screen-based assistance to investigate visible application behaviour and follow the permitted support workflow.

How you can use it

Visible context. Use the application’s screen to understand an error, a dialog or a step that device telemetry alone cannot explain.
Controlled interaction. Supported screen actions remain tied to the session, customer settings and consent. Changes are accountable through the surrounding support record.
A clear stopping point. Stop controls and the ability to hand work to a technician help when the task becomes sensitive, unclear or unsuitable for further AI interaction.

In practice

An application keeps showing an unfamiliar error dialog. Screen assistance lets the investigation include that message before the team decides whether a repair or manual support is appropriate.

Controls & availability

The AI session has its own restricted capabilities. Technician clipboard, file-transfer and session-chat channels are not provided to AI screen sessions.

Ask us about Repair library & learned fixes

Dashboard & AI

Repair library & learned fixes

Use reviewed, versioned runbooks and recommended repairs. Review proposed fixes and see where an AI request needed human help.

Read the full explanation

What it does

Keep repeatable support procedures in a reviewed library instead of rediscovering them for every incident. A runbook describes a supported check or repair, its parameters and the evidence needed to judge the result.

How you can use it

Reviewed procedures. Choose enabled, versioned runbooks with a defined purpose. The selected version stays associated with the work so the team can see what actually ran.
Useful recommendations. Bring suggested repairs and learned fixes into review, using the current problem and evidence to decide whether the procedure fits.
Verification and learning. Follow the result and any fresh check afterwards. Requests that needed human help can expose gaps and inform improvements to the repair catalogue.
Manage learned fixes. Review retained fixes whose check passed, enable or disable their reuse and set the customers they apply to through the supported administration controls.

In practice

After a recurring service problem has a reviewed repair, the team can reuse that procedure on the next affected computer and inspect the verification result.

Controls & availability

A learned suggestion is not unlimited permission to change devices. The runbook must be applicable, enabled and allowed by the current customer policy.

Ask us about Health monitoring & fleet checks

Monitoring & support

Health monitoring & fleet checks

Keep processor, memory, disk, services, crashes, update and antivirus readings in view. Run fresh device or fleet checks when needed.

Read the full explanation

What it does

Proactive care starts with knowing how the computers are behaving before someone calls. Vycko collects supported health readings and keeps them available at both device and fleet level, helping a support provider spot conditions that deserve investigation.

How you can use it

Everyday health signals. Review processor and memory use, available disk space, relevant services, crashes, updates and antivirus readings where the device supplies them.
Fresh checks when needed. Request a supported device or fleet check to supplement the stored picture when investigating a new symptom or reviewing an environment.
Connected evidence. Move from the health summary into performance history, inventory, alerts and the device’s support record to understand the likely cause.

In practice

A home computer gradually runs low on system-drive space. The support provider can investigate the warning and discuss the appropriate response before routine use is interrupted.

Controls & availability

Readings are collected at intervals and depend on connectivity and agent support. Vycko distinguishes fresh, stale and unavailable evidence; monitoring is not a guarantee against failure.

Ask us about Alerts & notifications

Monitoring & support

Alerts & notifications

Review severity and evidence, assign alerts, acknowledge or snooze them, and track recovery. App and phone notifications keep work visible.

Read the full explanation

What it does

An alert brings together the condition, its severity and the evidence behind it. The queue helps the team decide what matters, who is dealing with it and whether the condition has actually recovered.

How you can use it

Manage the response. Assign, acknowledge or snooze an alert, review its history and follow recovery or reopening when the same fault returns.
Delivery that fits the customer. Configure supported app, phone, email and webhook routes by severity, business hours and recipients. Email delivery is deliberately configured rather than assumed.
Escalation and digests. Use configured escalation for unacknowledged critical alerts and morning summaries to keep important work visible without sending every warning immediately.

In practice

A critical server alert reaches the relevant support team, while a lower-priority workstation warning is reviewed during the next working day under the customer’s routing rules.

Controls & availability

Notification history records delivery outcomes. Planned-work suppression has defined limits, and acknowledging an alert does not prove that its underlying fault has been fixed.

Monitoring & support

Work queue

Bring support requests and work needing a technician into one queue, with the current action and the next step clearly shown.

Read the full explanation

What it does

Bring the work that needs a person into one place. The queue connects customer requests, support conversations and tasks requiring technician attention, giving the team a clearer route from an incoming problem to a next action.

How you can use it

One view of incoming work. Review the available request and device context without searching separate conversations to understand what the customer needs.
A visible next step. See whether the task needs investigation, a response, an approval or another technician action, then open the relevant work record.
Continuity through handoff. Keep the conversation and current activity attached to the request so another authorised colleague can pick it up with useful context.

In practice

A customer submits a slow-laptop request through the portal. It appears in the team’s queue, where a technician can review the description, identify the device and begin investigating.

Controls & availability

Customer requests do not automatically start an AI investigation or grant remote access. The team decides how to handle the work within its existing permissions.

Ask us about Work queue

Ask us about Incidents & evidence

Monitoring & support

Incidents & evidence

Keep diagnostic findings, conversation, jobs, approvals and the outcome together. Follow a chronological activity timeline.

Read the full explanation

What it does

Keep an investigation understandable from start to finish. An incident brings the device context, findings, conversation, jobs, approvals and outcome into a connected record, so the reasoning behind a repair remains available afterwards.

How you can use it

Evidence in one place. Review diagnostic results and relevant device information alongside the reported symptom rather than treating an isolated error as the whole problem.
A chronological timeline. Follow what was checked, what was proposed, which decisions were made and how the work progressed.
An outcome with context. See the repair result and available verification, then retain the record for a customer explanation, repeat fault or technician handover.

In practice

When an application freezes repeatedly, the incident can connect performance readings, event evidence, the chosen repair and the result of the follow-up check.

Controls & availability

A completed job and a verified recovery are different outcomes. The record keeps failed checks and unresolved work visible instead of implying every attempted repair succeeded.

Ask us about Support sessions

Monitoring & support

Support sessions

Start and review remote support sessions. Keep the session history connected to the incident or device.

Read the full explanation

What it does

Start supported remote help and keep a record of the session alongside the device or incident. This gives the team a practical way to understand when assistance happened and return to the associated support context.

How you can use it

Session context. Review the device, support mode and session state, then connect the remote work to the customer’s reported problem.
History for follow-up. Open earlier sessions when a fault returns or a colleague needs to understand the previous support attempt.
Permitted evidence. Where enabled and supported, review recordings or screenshots associated with the work, subject to the customer’s consent and retention settings.

In practice

A technician reconnects to a computer after an intermittent fault returns and uses the linked incident and previous session history to avoid repeating the same investigation.

Controls & availability

Attended, unattended, technician and AI sessions have different permissions. Session history does not itself authorise another connection or reveal restricted recordings.

Ask us about Quick Support

Monitoring & support

Quick Support

Help a Windows computer without installing the managed agent first, through a temporary support session.

Read the full explanation

What it does

Help a Windows computer that does not yet have the managed Vycko agent installed. Quick Support provides a temporary route into an attended support session, useful for a first enquiry or a device that is outside the managed estate.

How you can use it

A temporary support route. Arrange a session with the person at the computer and use the supported screen assistance to investigate their problem.
Useful for first contact. Begin helping before a full managed-agent rollout has been agreed, keeping the immediate support task separate from longer-term enrolment.
A support record. Keep the session connected to the work so the team has context for follow-up or a later discussion about proactive care.

In practice

A home user with an unfamiliar laptop needs help with an application. A technician can arrange Quick Support, then discuss managed care if ongoing monitoring would be useful.

Controls & availability

Quick Support is temporary assistance, not continuous monitoring. Managed-agent capabilities such as eligible administrative file transfers and privacy mode are not automatically available in this session type.

Ask us about Customers, sites & devices

Devices & inventory

Customers, sites & devices

Organise the estate by customer and site, with scoped access, device types, connection state and signed-in users.

Read the full explanation

What it does

Organise computers around the people and places they belong to. Customer and site structure provides the context for support, policies, reporting and access, whether the environment is one household, one business or several managed clients.

How you can use it

A structured estate. Group devices by customer and site, and keep device type, connection state and available signed-in-user information close to the list.
Customer-specific care. Apply the appropriate alert routing, update choices, automation rules and portal settings to the environment being supported.
From fleet to detail. Filter the estate, open an individual computer and move into its hardware, software, security, performance and support views.

In practice

An IT support company can distinguish a client’s head office from its branch, review the branch computers and plan work within that client’s agreed settings.

Controls & availability

Customer scope limits what an account can see and act on. A technician’s access to one client does not automatically give them access to another.

Ask us about Hardware inventory

Devices & inventory

Hardware inventory

Explore processor, memory, firmware, hardware details, storage, battery and available health readings.

Read the full explanation

What it does

Understand the computer behind the reported problem. Hardware inventory brings together the available processor, memory, firmware and storage details, with battery and hardware-health readings where the device supports them.

How you can use it

A useful specification. Review model, serial and component information to identify the machine and assess its suitability for the software it needs to run.
Storage and battery context. Inspect available drive and battery readings when diagnosing limited space, ageing hardware or a laptop that no longer holds its charge.
Inventory connected to support. Use the hardware picture alongside performance history, warranty information and changes instead of working from the customer’s recollection alone.

In practice

Before recommending a memory upgrade for a slow office PC, the technician can confirm its existing specification and compare it with the observed workload.

Controls & availability

Inventory reflects what the agent can collect and when it last reported. A missing hardware-health reading is shown as unavailable, not proof that the component is healthy.

Ask us about Software inventory

Devices & inventory

Software inventory

See installed applications, versions and support or vulnerability findings. Investigate what is installed across an environment.

Read the full explanation

What it does

See the applications and versions reported by a device, then investigate the wider environment when a particular programme matters. This helps explain support issues, plan compatible updates and identify software needing closer review.

How you can use it

Installed application details. Review collected names and versions alongside operating-system information to understand the software environment on a specific computer.
Estate-wide investigation. Find computers reporting an application and compare versions, helping the team judge whether a problem is isolated or affects a wider group.
Links to other evidence. Bring inventory into update planning and configured vulnerability or support-status checks, while keeping uncertain matches available for review.

In practice

When an application vendor reports a problem in one release, the support team can identify the computers reporting that version and review the appropriate update route.

Controls & availability

An installed application is not necessarily eligible for automatic updating. Package support, installation context and customer exclusions still decide what Vycko can change.

Ask us about Performance history

Devices & inventory

Performance history

Read processor and memory history over different time ranges, with gaps and stale readings represented honestly.

Read the full explanation

What it does

A computer can feel slow even when it looks normal at the moment someone checks it. Performance history helps the team look back at processor and memory behaviour and compare periods around the reported symptom.

How you can use it

Different time ranges. Review the available history over a useful period, from a recent problem to a longer-running pattern.
Patterns rather than one reading. Look for repeated peaks or sustained pressure, then connect those observations to processes, events and the applications in use.
Honest gaps. See where samples are missing or old, so a computer that was offline does not appear to have had an uneventful period.

In practice

A business says a workstation becomes slow each afternoon. The technician compares the available history with scheduled tasks and running applications before choosing the next diagnostic check.

Controls & availability

History is sampled evidence rather than a recording of every moment. High CPU or memory use does not automatically trigger a reboot or process termination.

Ask us about Network details

Devices & inventory

Network details

Keep adapters, addresses and connectivity information alongside the device. Check remote access and Wake-on-LAN availability.

Read the full explanation

What it does

Keep the computer’s network information with the rest of its record. Adapter and address details help a technician understand how the device is connected and distinguish a local device problem from a connectivity issue.

How you can use it

Connection context. Review available network adapters, IP addresses and other collected connection details when a computer cannot reach the resources it normally uses.
Useful identification. Use supported address and adapter information to find the right machine across the estate rather than relying only on its display name.
Remote-support planning. Review relevant connectivity and Wake-on-LAN information before arranging a supported connection or a wake attempt.

In practice

A laptop works at home but cannot reach an office service. Its reported adapter and addressing information gives the technician a starting point for a focused network investigation.

Controls & availability

This is device-level network visibility. It does not imply comprehensive monitoring or configuration of every router, switch, printer or other network appliance.

Ask us about Users & groups

Devices & inventory

Users & groups

Review accounts and group membership. Use authorised actions for account access and password resets where supported.

Read the full explanation

What it does

Understand the accounts and group membership on a supported computer and use authorised tools when access needs attention. Keeping this information on the device page helps connect an account issue to the machine being investigated.

How you can use it

Account visibility. Review available local users and groups to understand who has access and which memberships may explain a permission problem.
Targeted management. Use supported, permitted local-account and group actions rather than making a broader change than the support task requires.
Password assistance. Follow the supported password-reset workflow where applicable, with the correct permissions and the additional requirements of the target environment.

In practice

A member of staff cannot use a local resource. The technician reviews the computer’s account and group evidence before deciding whether an authorised membership change is appropriate.

Controls & availability

Local account tools and domain account tasks have different requirements. A domain password reset needs the appropriate supported domain-controller route; device access alone is insufficient.

Ask us about Printers, startup & tasks

Devices & inventory

Printers, startup & tasks

Investigate printers and the available share readings, startup entries and scheduled tasks in dedicated device views.

Read the full explanation

What it does

Look beyond the headline symptom into the components that often explain everyday support problems. Dedicated device views bring printer information, startup entries and scheduled tasks into the same investigation as services and performance.

How you can use it

Printing context. Inspect available printer and relevant share readings when a queue, connection or print-service problem interrupts work.
Startup visibility. Review what is configured to start with the computer or user session when investigating a slow sign-in or unexpected application behaviour.
Scheduled work. Inspect collected tasks and use supported authorised actions where available, linking recurring behaviour to the timing of a task.

In practice

A computer becomes busy shortly after sign-in. The technician compares startup entries and scheduled tasks with performance evidence to decide what needs further investigation.

Controls & availability

Availability varies by device and collected evidence. Disabling a startup entry or task is a change and must follow the relevant permissions and customer rules.

Ask us about Device actions

Devices & inventory

Device actions

Restart, shut down, lock, sign out or message a device within the applicable rules. Refresh inventory and manage agent health.

Read the full explanation

What it does

Handle common device tasks from the support workflow without losing the record of what happened. Vycko offers supported actions for the computer, signed-in session and agent, with the appropriate checks before a disruptive change.

How you can use it

Computer and session actions. Use permitted restart, shutdown, lock, sign-out and message actions where supported, choosing the relevant device and context.
Support-specific tasks. Refresh inventory, request a fresh check, capture an allowed screenshot or use a supported safe-mode workflow when the investigation calls for it.
Agent management. Review agent health and use the supported restart or management route when the collection or connection itself needs attention.

In practice

After an approved update, a technician arranges a restart at an appropriate time and checks the computer’s subsequent connection and update state.

Controls & availability

Actions are capability- and policy-dependent. Restarting or signing someone out can interrupt work, so the customer’s approval and notification requirements still apply.

Ask us about Changes & device notes

Devices & inventory

Changes & device notes

Follow hardware, software and settings changes, with attribution where available. Keep useful notes and history with the device.

Read the full explanation

What it does

When something starts behaving differently, knowing what changed can shorten the investigation. Vycko keeps available hardware, software and settings changes with the device, alongside notes that preserve the human context.

How you can use it

A change timeline. Review detected differences in collected device information and compare their timing with the reported problem.
Available attribution. Where a change relates to a platform action, use the linked job or activity information to understand how it happened.
Useful notes. Keep support observations, known quirks and follow-up information with the machine, making the next handover easier.

In practice

An application begins failing after its reported version changes. The technician can relate the change to the support incident and review any associated update activity.

Controls & availability

A detected difference does not always identify its cause or author. Attribution is shown where available, and private operator notes are not exposed as customer-portal conversations.

Ask us about Warranty tracking

Devices & inventory

Warranty tracking

See warranty details, upcoming expiry and report coverage. Manufacturer lookups depend on configured provider access.

Read the full explanation

What it does

Bring warranty information into proactive care and replacement discussions. Vycko can show available coverage details, highlight approaching expiry and include warranty context in the dashboard, customer views and reports.

How you can use it

Coverage at a glance. Review the stored warranty information alongside the device’s identity and hardware details.
Upcoming decisions. Use expiry views to identify machines that may need a coverage discussion or replacement review before a fault becomes urgent.
Supported lookups and manual records. Use configured manufacturer-provider access where available, and record information manually when an automatic lookup is unsuitable.

In practice

A business reviews laptops approaching the end of coverage and combines their warranty, condition and support history to plan the next purchasing discussion.

Controls & availability

Manufacturer lookups depend on configured access and the provider’s response. A firmware date is not proof of manufacture or a substitute for confirmed warranty coverage.

Ask us about Virtual machines

Devices & inventory

Virtual machines

Read available Hyper-V and VMware host and virtual machine information, including state and capacity. Availability depends on the environment.

Read the full explanation

What it does

Keep supported virtualisation information visible alongside the physical host. Read-only Hyper-V and VMware views help the team understand which virtual machines are present and how their state and available capacity relate to the wider environment.

How you can use it

Host context. Review collected virtualisation-host information so an incident can be investigated with an understanding of the underlying platform.
Virtual-machine visibility. Inspect available guest names, state and resource information, connecting host observations to the machines running on it.
Capacity discussions. Use the supported inventory as evidence when reviewing resource pressure or planning further investigation.

In practice

Several virtual servers become slow at similar times. Host and virtual-machine information helps the support team decide whether to investigate shared capacity before treating each guest separately.

Controls & availability

These views are read-only and depend on supported collectors and configured access. They do not imply that Vycko creates, moves, snapshots or deletes virtual machines.

Ask us about Certificates

Devices & inventory

Certificates

Review collected certificate details and expiry findings, with dashboard and reporting views for attention where needed.

Read the full explanation

What it does

Expired certificates can interrupt services that otherwise appear healthy. Vycko collects supported certificate information and brings relevant expiry findings into device, dashboard and reporting views so the team can plan a response.

How you can use it

Certificate context. Review available validity dates and certificate details, with supported service assignments such as web hosting or remote desktop where they can be identified.
Relevant expiry attention. Focus on watched certificates that appear in use or otherwise meet the monitoring rules, rather than treating every unused expired certificate as an active service fault.
Configurable thresholds. Use the applicable customer settings to decide when approaching expiry needs attention and which device types are monitored.

In practice

A support team sees an in-use server certificate approaching expiry and can arrange renewal work before the associated service starts rejecting connections.

Controls & availability

Certificate collection is read-only. Vycko’s expiry visibility does not automatically renew, issue or install a certificate, and unsupported assignments may remain unknown.

Ask us about Device location

Devices & inventory

Device location

Keep a written room and floor, map the site, and review supported device positions with their source, accuracy and time.

Read the full explanation

What it does

Know where an asset belongs and understand the quality of any reported position. Vycko combines a written device location, site addresses and supported location readings, with maps that distinguish a building from an approximate or precise device position.

How you can use it

A location in words. Record a room, floor or description such as “accounts office, desk four”. This remains useful even when the computer cannot report its position.
Site maps and pins. Add a postal address or place a site pin by hand, giving the team a practical reference for the environment.
Reported positions. Review supported approximate internet-address location and Windows location readings, with the source, time and available accuracy attached to the result.

In practice

A technician finds the correct office workstation from its written room and desk description, while a laptop’s last supported location is shown with its age and accuracy.

Controls & availability

Reported location depends on customer settings, Windows permissions and available positioning. Approximate town-level results are not an exact address; location visibility is restricted by role.

Ask us about Remote screen control

Remote tools

Remote screen control

Connect to a supported device with screen, mouse and keyboard controls, within the customer’s access and consent settings.

Read the full explanation

What it does

Help someone on the screen they are actually using. Supported remote sessions provide the technician with screen, mouse and keyboard access, making it easier to explain a problem, inspect application behaviour and work through a repair together.

How you can use it

A view that fits the task. Select a monitor or a combined view on supported devices, use available display-quality controls and choose the appropriate user session when the environment supports it.
Technician collaboration tools. Use permitted session chat, clipboard or file channels when those capabilities are enabled for the session and customer.
Support through interruption. Use the supported wake, restart and reconnect workflows where available, and keep session history linked to the device or incident.
Privacy mode. Where allowed, temporarily cover the local display and restrict local input during eligible technician work. The person at the computer retains a stop route, including Ctrl+Alt+Delete.
Computer sound. Turn on supported session audio to hear playback or other computer sounds when diagnosing an audio problem. The transmitted sound is not added to the session recording.

In practice

A home user cannot find why an application is failing. The technician views the error with them, explains the next step and follows the agreed support procedure.

Controls & availability

Consent, customer policy and device capabilities govern access. Optional audio and privacy mode have separate requirements, start disabled and remain technician-only.

Ask us about Session recording & screenshots

Remote tools

Session recording & screenshots

Capture permitted session evidence, review recordings and use consented screenshots for a support investigation.

Read the full explanation

What it does

Keep permitted visual evidence of a support investigation. Screenshots can preserve a relevant symptom, while eligible session recordings allow authorised colleagues to review the screen work that took place.

How you can use it

Screenshots with context. Capture a permitted image to support an incident or explain an application error, rather than relying on a remembered description.
Recorded technician sessions. Where enabled, supported and consented, review the visual recording through the session’s history.
Retention controls. Apply the configured customer retention and storage limits so recordings remain subject to an explicit access and lifecycle policy.

In practice

A recurring dialog disappears before a second technician can see it. An allowed screenshot gives the follow-up investigation a clear reference to the original symptom.

Controls & availability

Recording is off by default for customers and applies to eligible technician sessions, never AI sessions. Recordings contain pictures rather than sound; privacy mode and session audio are not recorded.

Ask us about Remote console

Remote tools

Remote console

Use the device’s supported console for authorised investigation and commands, with a transcript and audit history.

Read the full explanation

What it does

Use a supported remote command environment when a technician needs a more direct diagnostic route. The console keeps the session attached to the computer, making the commands and their output available as part of the support work.

How you can use it

Focused investigation. Run authorised commands to inspect the relevant state or gather information that needs a console rather than a dashboard summary.
A readable transcript. Review command output and the session record when interpreting a result or handing the investigation to another technician.
Connected support context. Work from the relevant device so console findings can be considered alongside events, processes, services and incident evidence.

In practice

A technician uses a permitted diagnostic command to investigate a connection problem, then records the result with the incident before choosing a corrective action.

Controls & availability

Console access is permission-dependent and powerful commands can change the machine. The available environment and action controls vary with the operating system and installed agent.

Ask us about File manager & transfers

Remote tools

File manager & transfers

Browse and manage files. Transfer larger files with resumable uploads and downloads, integrity checks and overwrite protection.

Read the full explanation

What it does

Inspect supported device files and move the material needed for a support task without losing the surrounding permissions. The remote file manager helps a technician browse the relevant location and manage an authorised transfer.

How you can use it

Browse and manage. Use supported file operations to inspect folders, locate diagnostic material and carry out permitted management tasks.
Reliable transfer handling. Eligible uploads and downloads support larger-file workflows with resumable transfer, integrity checks and protection against unintended overwrites.
Customer-specific limits. Use the configured upload, download and transfer-size rules rather than assuming every technician session can move any file.

In practice

A technician retrieves an authorised diagnostic log, reviews it with the incident and transfers an approved support file where the customer’s policy permits.

Controls & availability

Administrative-location transfers require an eligible managed-agent technician session. Quick Support and AI screen sessions do not inherit these file-transfer capabilities.

Ask us about Services & processes

Remote tools

Services & processes

Inspect service state and running processes. Make targeted changes under the relevant permissions and keep the action recorded.

Read the full explanation

What it does

Look at the activity behind an application or device symptom. Supported service and process tools let a technician inspect what is running and make a targeted, authorised intervention when the evidence supports it.

How you can use it

Service state. Review available service status and relevant settings when a component has stopped or is behaving unexpectedly.
Running processes. Inspect the available process information to understand which applications or background tasks relate to observed resource pressure.
Targeted actions. Use supported, permitted service or process actions and keep the result associated with the investigation.

In practice

A printing problem may be traced to a stopped print service. The team can review the finding, follow the applicable approval route and check the state after a permitted restart.

Controls & availability

Stopping a process or changing a service can affect other work. High resource use alone does not authorise automatic termination, and protected services are excluded from general automatic remediation.

Remote tools

Event logs

Read device events with useful filters to investigate errors and service behaviour in context.

Read the full explanation

What it does

Use the computer’s recorded events to understand when a problem began and what happened around it. Supported log views bring the evidence into the remote investigation without requiring the person at the device to read technical messages aloud.

How you can use it

Filtered evidence. Narrow the available events by useful criteria to find the errors or service messages relevant to the reported symptom.
Timing and context. Compare an event’s time with changes, performance history and support activity rather than assuming the first visible warning is the cause.
A stronger incident record. Use relevant findings to support the proposed next step and make a follow-up investigation easier to understand.

In practice

An application closes unexpectedly. The technician inspects the relevant events around the reported time and uses those findings to choose a focused diagnostic check.

Controls & availability

Available logs and access depend on the operating system and agent. An event is evidence to interpret, not an automatic diagnosis or permission to run a repair.

Ask us about Event logs

Ask us about Windows Registry tools

Remote tools

Windows Registry tools

Browse and manage supported Registry keys and values, import or export with a preview, and review recorded changes and undo copies.

Read the full explanation

What it does

Give authorised technicians a structured way to investigate supported Windows Registry settings. The tools bring browsing, searching and controlled changes into the device workflow, with previews and recorded context for sensitive work.

How you can use it

Inspection and search. Browse permitted hives and values, inspect their types and use supported searches and registry views to locate a relevant setting.
Previewed changes. Review supported imports and exports before acting, and use the required confirmation for more sensitive operations.
A recoverable record. Retain available change history and undo copies so the technician can understand the prior state and follow the supported recovery route.

In practice

A documented application repair requires reviewing one Registry value. An authorised technician inspects that setting and previews the specific change before applying it.

Controls & availability

These are human-operated Windows tools, not unrestricted AI Registry access. Protected areas such as SAM and SECURITY are excluded, and a saved undo copy is not a full system backup.

Ask us about Windows patch management

Updates & automation

Windows patch management

Scan for missing updates, review failed installs and plan update installation and restarts with customer policies.

Read the full explanation

What it does

Manage Windows updates as a planned support activity. Vycko separates discovery, installation and restart decisions so the team can see what is missing, understand failures and fit the work around the customer’s environment.

How you can use it

Scan and review. Check supported computers for missing updates and inspect available installation history and failed-update evidence.
Plan the rollout. Apply customer update choices, device exclusions and approved schedules, keeping the selected scope visible before installation.
Handle restarts deliberately. Use supported workstation restart notices and review whether a restart is still needed to complete the work. Servers require explicit approval.

In practice

A business reviews missing updates, approves a workstation plan for an agreed window and follows the per-device results, including computers still awaiting restart.

Controls & availability

Scanning is read-only. Installation depends on customer settings, agent capabilities and the approved plan; an excluded device or active stop control prevents the relevant automated work.

Ask us about Application updates & deployment

Updates & automation

Application updates & deployment

Use the application catalogue and supported package deployment, with rollout rings, pacing and stop controls. Confirm supported packages during setup.

Read the full explanation

What it does

Keep supported applications current through the package catalogue and configured rollout workflow. Vycko helps distinguish a package it can manage from an application that is simply present in inventory.

How you can use it

Catalogue and package matching. Review eligible application updates and supported deployment options, using the available package information rather than assuming every programme can be changed.
Rollout controls. Apply pilot rings, pacing and stop choices so a supported application change can be reviewed on a smaller group before proceeding more widely.
Exclusions that matter. Keep self-updating and business-critical applications out of an unsuitable automatic route, using the configured catalogue and customer exclusions.

In practice

A support team reviews a supported package update on a pilot group before planning a wider rollout, with the individual results available for follow-up.

Controls & availability

Windows package management primarily uses supported winget routes. Per-user installations, unknown packages and excluded applications may be ineligible; installation and removal support must be confirmed during setup.

Ask us about Automation calendar

Updates & automation

Automation calendar

Schedule reviewed runbooks across selected devices or groups, preview the plan, and see upcoming work and per-device outcomes.

Read the full explanation

What it does

Make repeatable maintenance visible before it runs. The automation calendar schedules an enabled, reviewed runbook against a defined set of devices, with its plan and eventual results available to the team.

How you can use it

Targets and timing. Choose devices, a customer, a site or a saved group, then schedule a one-off or recurring run in the relevant time zone.
Practical scheduling choices. Configure supported blackout dates, maintenance windows, missed-run handling and what happens when a device is offline.
A plan tied to approval. Review the runbook version, parameters and included or excluded computers. Material changes to that plan require a new approval decision.

In practice

A support provider schedules a reviewed check for a customer’s workstations, excludes an agreed blackout period and reviews the run’s device-by-device results afterwards.

Controls & availability

Schedules use reviewed procedures, not arbitrary free-text instructions. Newly joined devices are not silently added to an already approved plan, and servers require the applicable named approval.

Ask us about Bulk actions

Updates & automation

Bulk actions

Review a multi-device plan before it runs. Use controlled batches and track succeeded, failed and skipped results.

Read the full explanation

What it does

Carry out a supported task across several computers with a reviewable plan. Bulk actions use the same controlled runbook approach as scheduled automation, but run once after a person approves the selected scope.

How you can use it

Preview before starting. See the chosen runbook, parameters and computers, including exclusions and the reasons a device cannot participate.
Controlled batches. Use supported pacing and pilot choices to limit how much work begins at once and decide whether the wider group should proceed.
Results per device. Follow verified, failed, skipped, cancelled or restart-dependent outcomes instead of treating the whole batch as a single success.

In practice

A technician selects an office’s eligible workstations for a reviewed check, approves the displayed plan and inspects the computers that failed or were offline.

Controls & availability

A person approves the bulk plan. Current policy and device eligibility are checked again as work starts; cancellation withdraws unstarted work, while some already-running tasks may need to finish safely.

Ask us about Automatic remediation

Updates & automation

Automatic remediation

Configure reviewed fixes for known alert conditions. Rules decide what may run, what needs approval and when automation must stop.

Read the full explanation

What it does

Handle selected, well-understood alert conditions through reviewed fixes. Automatic remediation is configured deliberately, with per-fix and customer rules, rather than allowing any warning to trigger an unrestricted change.

How you can use it

Targeted supported fixes. Eligible procedures include narrowly scoped service recovery, system-drive housekeeping and specific supported security corrections.
Checks before and after. Require sufficiently fresh evidence, respect cooldowns and attempt limits, then perform the available post-check to see whether the alert condition recovered.
Human follow-up. Keep failed attempts and unresolved alerts visible, stopping repeated automatic attempts when the rules require a technician to investigate.

In practice

An eligible low-disk alert can lead to configured housekeeping of approved temporary or cache locations, followed by a fresh space check.

Controls & availability

Remediation is off until enabled. Housekeeping does not delete personal Desktop, Documents or Downloads files; it does not automatically reboot or kill processes for high CPU or memory use. Servers and shared devices need a person.

Ask us about Maintenance windows

Updates & automation

Maintenance windows

Set maintenance periods for a device, site or customer. Suppress relevant alerts and hold automatic remediation during the window.

Read the full explanation

What it does

Tell the platform when planned work is taking place. A maintenance window gives support activity a defined scope and period, helping the team distinguish expected interruptions from a new fault and hold relevant automation.

How you can use it

The right scope. Set a maintenance period for a supported device, site or customer so the window follows the environment actually being worked on.
Relevant alert handling. Suppress eligible planned-work notifications while retaining the alert context and the reason for suppression.
Coordinated automation. Hold automatic remediation during the applicable window and use supported schedule settings to run work only within its agreed period.

In practice

Before an office network change, the team creates a site window so expected connectivity interruptions do not produce the usual notification pattern.

Controls & availability

Maintenance is not a blanket mute for every serious condition. Defined protection remains for findings such as failing disks, antivirus problems and firewall issues.

Updates & automation

Wake-on-LAN

Check whether a supported device can be woken and use a relay on its network. Review the outcome of each attempt.

Read the full explanation

What it does

Bring an eligible sleeping or powered-down computer back online when its hardware and network support Wake-on-LAN. Vycko uses the supported network-relay route and keeps the attempt visible in the support workflow.

How you can use it

Check eligibility. Review whether the device and network information support a wake attempt instead of assuming every offline computer can be started remotely.
Use a local relay. Send the supported wake request through an available relay on the target network.
Follow the outcome. Review the attempt and whether the computer subsequently connects, then continue the permitted remote-support task if it becomes available.

In practice

A technician needs to perform agreed work on an office workstation after hours and attempts to wake it through an eligible device on the same network.

Controls & availability

Wake-on-LAN depends on firmware, power, adapter settings and an available network relay. A sent wake request is not proof that the computer started successfully.

Ask us about Wake-on-LAN

Ask us about Antivirus, firewall & encryption

Security & controls

Antivirus, firewall & encryption

Review device security readings and encryption state. Use authorised security actions according to the device and policy.

Read the full explanation

What it does

Bring supported endpoint security readings into the same view as device health. The team can review protection and encryption state, investigate missing or outdated evidence and use authorised actions where the device and customer policy allow them.

How you can use it

Protection visibility. Review available antivirus and firewall readings, including relevant findings that need investigation rather than assuming all installed security software is functioning.
Encryption context. Inspect supported disk-encryption state and connect permitted BitLocker actions or recovery-key handling to the device’s controls.
Evidence for follow-up. Use the readings in alerts and readiness reviews, then inspect a fresh result after an eligible corrective action.

In practice

A support provider sees outdated supported antivirus definitions on a workstation and reviews the applicable correction and subsequent reading.

Controls & availability

Supported Windows actions are specific to the reported product and state. Vycko does not replace an antivirus product, and missing security evidence is not presented as proof of protection.

Ask us about Vulnerability & support status

Security & controls

Vulnerability & support status

Identify known application and operating system findings from configured vulnerability data, with exceptions and mappings for review.

Read the full explanation

What it does

Use configured vulnerability and support data to identify software that deserves attention. Vycko relates available application and operating-system information to known findings, helping the team prioritise investigation and update planning.

How you can use it

Known findings. Review the available matches against the configured data sources, with the relevant application or operating-system evidence in context.
Support lifecycle. Identify reported software or systems whose support status may create a maintenance or replacement decision.
Review uncertain matches. Manage supported mappings and exceptions so ambiguous inventory is investigated rather than treated as a perfectly certain match.

In practice

A business review finds machines reporting an unsupported Windows release. The team can check the evidence and discuss an upgrade or replacement plan.

Controls & availability

Coverage depends on inventory quality, configured sources and matching. These checks do not establish that every vulnerability has been found or replace a full security assessment.

Ask us about Cyber Essentials readiness

Security & controls

Cyber Essentials readiness

Review technical readiness from available endpoint evidence and explore supported corrective actions. Readiness evidence is not certification.

Read the full explanation

What it does

Understand the available technical evidence relevant to Cyber Essentials preparation. Vycko brings supported endpoint checks into a readable readiness view, helping the team identify gaps and discuss the corrective work that may be needed.

How you can use it

Evidence and coverage. Review the supported checks with their device coverage and freshness, so a headline is grounded in what has actually been observed.
Findings to investigate. Open the affected devices and supporting readings when a technical condition needs attention.
Supported corrective actions. Where a check has an eligible remedy, review that action through the applicable customer policy and approval workflow.

In practice

A company preparing for an assessment uses the readiness view to investigate endpoint update and protection gaps before discussing its formal assessment with the appropriate provider.

Controls & availability

The feature provides technical evidence and preparation guidance, not certification. Stale, unknown or unsupported checks remain explicit and are not counted as a pass.

Ask us about ISO 27001 technical readiness

Security & controls

ISO 27001 technical readiness

Explore available technical control evidence and a customer checklist for other controls. Unsupported or unknown checks remain explicit.

Read the full explanation

What it does

Connect supported technical evidence to an ISO 27001 readiness discussion without suggesting that endpoint data covers the whole management system. Vycko combines available technical checks with a separate customer checklist for areas requiring organisational evidence.

How you can use it

Supported technical controls. Review the endpoint evidence the platform can judge, with coverage and known limitations shown alongside the finding.
A broader checklist. Record customer input for organisational, people and physical areas that cannot be established from a computer’s telemetry.
Clear gaps. Keep unsupported, not-checked and unknown areas visible so the team knows where additional evidence or specialist work is needed.

In practice

A business uses supported endpoint findings as one input to its readiness work, then gathers the policies, process records and other evidence needed outside Vycko.

Controls & availability

This is a readiness aid, not an ISO 27001 audit, certification or guarantee of conformity. Customer checklist answers and endpoint checks represent different kinds of evidence.

Ask us about Approvals & customer rules

Security & controls

Approvals & customer rules

Define diagnostics-only, approval-required, pre-approved or prohibited actions. Important decisions stay visible and attributable.

Read the full explanation

What it does

Decide what level of autonomy suits each environment. Vycko’s rules distinguish observing a computer from changing it, and make an approval decision specific enough for the person reviewing it to understand the proposed work.

How you can use it

Different action policies. Configure supported diagnostics-only, approval-required, pre-approved or prohibited routes according to the action and customer.
Reviewable proposals. See the intended change, its device scope and relevant evidence before approving or declining a supported plan.
Accountable decisions. Keep the decision and action connected in the record, with additional authentication or explicit server approval where required.

In practice

A household allows routine observation but wants repairs approved. A business uses tighter rules for its server than for eligible workstations.

Controls & availability

Approval applies to the plan that was reviewed. Changes to the material scope, procedure or parameters can invalidate that approval, and current policy is checked again before work starts.

Ask us about Secrets, keys & local passwords

Security & controls

Secrets, keys & local passwords

Keep supported credentials and recovery keys in the vault, with controlled reveal, access records and rotation features.

Read the full explanation

What it does

Keep supported credentials and recovery information within a controlled vault workflow. Vycko separates ordinary device visibility from revealing sensitive values, with customer scope, permissions and records around access.

How you can use it

Protected storage and reveal. Store supported secrets using the vault’s encryption controls and require the applicable authorisation and fresh authentication before revealing a value.
Managed local passwords. Use supported local-administrator password management and rotation workflows rather than sharing one static password across an estate.
Recovery-key handling. Use supported BitLocker recovery-key escrow and related actions where configured, with device context and audit records.

In practice

An authorised technician needs a stored recovery value for an agreed support task, completes the required verification and leaves an auditable access record.

Controls & availability

Vault access is restricted and recorded. Supported key types and rotation depend on the device; Windows BitLocker support does not imply equivalent FileVault recovery-key escrow.

Ask us about Stop controls

Security & controls

Stop controls

Pause the relevant automation, AI work or remote access when the environment needs it. Bound actions to the permitted scope.

Read the full explanation

What it does

Pause the relevant work when the environment or investigation needs a human decision. Stop controls give the team an explicit way to restrict supported automation, AI activity or remote access within the applicable scope.

How you can use it

Scoped restrictions. Apply the relevant control to the affected environment instead of relying on someone to remember a note before starting work.
Observe-only operation. Use supported settings to retain the permitted diagnostic picture while preventing the applicable changing actions.
Checks as work begins. Current stop state is considered by the supported dispatch and start workflow, including relevant scheduled and remediation tasks.

In practice

During investigation of an unexpected application problem, a business pauses applicable automated changes while the team reviews the evidence and agrees the next step.

Controls & availability

A stop request cannot always undo a task already running. Some procedures finish at a safe point, and the resulting record explains work that could not be interrupted.

Ask us about External exposure checks

Security & controls

External exposure checks

Review configured external checks for a customer’s public-facing services, within the customer’s approved scope.

Read the full explanation

What it does

Review supported checks of a customer’s authorised public-facing services. This complements endpoint information by looking at the approved external scope, with findings available for the team to investigate.

How you can use it

Explicit scope. Configure the permitted customer public addresses and retain the authorisation relevant to checking them.
External findings in context. Review the supported exposure results with their target and timing rather than treating a computer’s local security state as the whole picture.
A route to follow-up. Use findings to prioritise investigation of an unexpected public service or configuration and discuss the appropriate corrective work.

In practice

A business authorises checks of its public service addresses. The support team reviews an unexpected exposed service and confirms whether that exposure is intentional.

Controls & availability

External checks are off until configured and authorised, and only the approved scope is eligible. They are not unrestricted network scanning, penetration testing or a guarantee of external security.

Ask us about Customer portal

Customer experience

Customer portal

Give customers their own view of computers, plain-language alerts, work done, reports and readiness information.

Read the full explanation

What it does

Give the people you support a clearer view of their own IT. The portal turns available device and support information into a customer-facing workspace, helping home users and business contacts understand what needs attention and what is being done.

How you can use it

A plain-language overview. Review health, understandable alerts, open requests and recent work, alongside available warranty, certificate and planned-maintenance information.
Computers and reports. Open the permitted computer information, asset register, readiness views and monthly reports without navigating technician-only tools.
A route to the support team. Submit a request, follow its conversation and use the contact information for the provider looking after the environment.

In practice

A home user checks their computer’s overview and sees an open request with the support team’s reply. A business contact reviews its devices before a service meeting.

Controls & availability

Portal accounts are separately scoped to the permitted customer and sites. Remote control, console tools, scripts, vault secrets and internal technician notes are not exposed in the customer workspace.

Ask us about Customer asset register

Customer experience

Customer asset register

Give customers a searchable, read-only inventory of their computers, with filters, phone-friendly views and permitted exports.

Read the full explanation

What it does

Give customers a usable inventory of the computers they own. The portal asset register presents a read-only selection of device information, helping a household keep track of its computers and a business review its estate.

How you can use it

Useful asset records. Review allowed hardware, firmware, operating-system, installed-software, network, security, warranty and written-location information.
Find and compare. Filter by supported site, device type, system, maker or warranty state, and search names, serials, models or installed programme names.
A format for real work. Sort the records, use the phone-friendly asset cards and export the permitted information for a purchasing or inventory discussion.

In practice

A business contact prepares for an equipment review by filtering the asset register to laptops at one site and exporting the relevant inventory.

Controls & availability

The register is read-only and uses an explicit allowlist of customer-visible fields. Confidential operator information is excluded, and the feature can be disabled for a customer.

Ask us about Replacement planning

Customer experience

Replacement planning

Review warranty, operating-system support, estimated age and disk-health indicators to plan an equipment discussion.

Read the full explanation

What it does

Turn inventory and health evidence into a practical equipment conversation. Replacement planning highlights supported indicators that a computer may need review, allowing customers and support teams to plan rather than wait for a failure.

How you can use it

Several reasons for review. Consider available warranty expiry, unsupported Windows versions, estimated age and supported disk-health findings together.
Evidence behind the suggestion. Review the reported reason and relevant device information before treating a machine as a replacement candidate.
Customer conversations. Use the customer-facing view to discuss priorities, budget and timing, then raise a quote request where appropriate.

In practice

A business identifies an out-of-warranty workstation with an unsupported operating system and discusses whether an upgrade or replacement best suits its needs.

Controls & availability

Replacement indicators are prompts for review, not purchase instructions. Age estimates may use firmware or installation dates and are not proven manufacture dates; virtual machines are not judged by physical warranty or age.

Ask us about Requests & conversations

Customer experience

Requests & conversations

Let customers ask for help, starters, leavers or quotes, then follow and reply to requests in the portal.

Read the full explanation

What it does

Let customers ask for help and follow the response in the same place. Structured requests capture useful detail at the start, while the conversation keeps the support team and customer connected as the work progresses.

How you can use it

Helpful request details. Submit the subject, problem, urgency, optional computer and permitted screenshot, giving the team a better starting point than a vague message.
More than faults. Use supported starter, leaver and quote forms to describe planned changes or purchasing needs in a structured way.
Visible replies. Follow customer-visible messages and permitted attachments, with staff replies presented through the support company identity.

In practice

A business submits a starter request with the required information, then follows the support team’s questions and updates through the portal conversation.

Controls & availability

The request enters the work queue without automatically starting AI or a remote session. Internal notes stay internal, and attachment types and access follow the portal’s restrictions.

Ask us about Monthly reports

Customer experience

Monthly reports

Summarise device health, alerts, work completed and outstanding issues, with evidence coverage and available readiness sections.

Read the full explanation

What it does

Explain the value and state of ongoing care in a readable monthly report. Vycko builds a stored snapshot from the available platform evidence, covering the customer’s estate, support activity and work still needing attention.

How you can use it

A view of the month. Review device coverage, health, opened and recovered alerts, repairs, incidents and support-chat outcomes, with the available update and readiness sections.
Outstanding work. Keep unresolved incidents, unrecovered alerts and unsuccessful verification visible so the report supports a useful follow-up discussion.
Delivery and sharing. Use configured scheduled email delivery, customer-portal access and the printable report view, with the applicable access and link settings.

In practice

A support provider uses the report to explain what was handled for a home user, or to discuss a business’s remaining issues and planned work at its monthly review.

Controls & availability

The report is a frozen evidence snapshot and does not query every computer when opened. Missing coverage is described explicitly rather than presented as zero problems.

Ask us about Desktop support chat

Customer experience

Desktop support chat

Give the person at the computer a direct route to ask for help and follow a support conversation, with handoff when needed.

Read the full explanation

What it does

Give the person using a managed computer a direct route to help. Desktop support chat connects the local user’s question to the support workflow, reducing the effort needed to identify the affected machine and explain the problem.

How you can use it

Ask from the computer. Describe the issue while using the affected device, keeping the conversation tied to that support context.
Follow the conversation. Keep replies and the current support progress accessible instead of making the user repeat the problem in a separate channel.
Handoff when needed. Route work to a technician when the supported assistance cannot resolve the question or a person needs to take over.

In practice

A home user opens support chat on the laptop that is behaving unexpectedly, describes the symptom and follows the support team’s response.

Controls & availability

The installed agent and configured support route determine availability. Starting a conversation does not by itself give unrestricted remote control or bypass the customer’s action rules.

Ask us about Mobile dashboard

Customer experience

Mobile dashboard

Use the responsive dashboard on a phone, add it to the home screen and receive supported app notifications.

Read the full explanation

What it does

Keep useful support visibility close when you are away from a desk. The responsive dashboard adapts the platform to a phone, so an authorised operator can review the relevant work and decide what needs attention.

How you can use it

Responsive views. Review supported dashboard, device and work information through layouts suited to a smaller screen.
Home-screen access. Add the supported web app to the phone’s home screen for a more direct route back to the platform.
Supported notifications. Receive configured app notifications when the device, browser and customer route support them, then open the relevant context.

In practice

A technician away from the office receives a configured critical notification, reviews the alert on their phone and decides whether to return to a full support session.

Controls & availability

Phone access uses the same sign-in and customer scope. Notification support and permissions vary by browser and device, and some detailed support tasks are better suited to a larger screen.

Ask us about Agent enrolment & deployment

Administration

Agent enrolment & deployment

Connect one device or prepare site installers for a rollout. Manage enrolment keys, held devices, agent updates and removal.

Read the full explanation

What it does

Connect computers to the managed platform through a deliberate enrolment process. Vycko supports individual setup and site-oriented rollout preparation, with controls over enrolment keys, device admission and the agent lifecycle.

How you can use it

Start small or prepare a rollout. Enrol an individual computer or prepare the supported site installer route for several devices.
Manage admission. Review keys and held devices so computers are associated with the appropriate customer and site before becoming part of ongoing care.
Maintain the agent. Follow supported agent-update, health and removal workflows, keeping the installed capability relevant to the tools being used.

In practice

A support provider starts with one business workstation, confirms the customer setup and then prepares the remaining site’s supported rollout.

Controls & availability

Feature availability depends on the operating system, agent version and granted permissions. Windows has the broadest feature set; Mac and Linux capabilities should be confirmed for the intended workflow.

Ask us about Roles, customer scope & sign-in

Administration

Roles, customer scope & sign-in

Separate administrator, technician and read-only access. Use authenticator sign-in and supported passkeys with scoped customer visibility.

Read the full explanation

What it does

Match platform access to the work a person is responsible for. Roles and customer scope help separate administration, technical support and read-only visibility, while supported stronger sign-in controls protect access to the workspace.

How you can use it

Role-based access. Distinguish administrator, technician and read-only responsibilities rather than giving every account the same tools.
Customer boundaries. Limit the customers and environments an account can see, keeping a multi-client support team’s access aligned with its responsibilities.
Stronger verification. Use supported authenticator sign-in and passkeys, with fresh verification for the sensitive operations that require it.

In practice

A support business gives a technician access to the clients they look after, while an authorised read-only colleague can review the permitted information without changing computers.

Controls & availability

Sign-in is only one layer. Remote tools, approvals, secret reveal and integrations also have their own applicable permission checks; portal users use a separately scoped customer experience.

Ask us about Audit log & CSV exports

Administration

Audit log & CSV exports

Review who changed what and when. Export supported device, inventory, warranty, alert and audit views within the reader’s permissions.

Read the full explanation

What it does

Keep the platform’s decisions and actions reviewable. The audit log records supported activity, while CSV exports make selected estate and support information available for an authorised review outside the dashboard.

How you can use it

Who, what and when. Review available action, approval, policy, access and support events with their relevant customer or device context.
Investigate and explain. Filter the audit view to understand a change, answer a customer question or review how a support task was handled.
Supported exports. Export permitted device, software-inventory, warranty, alert and audit views, following the selected scope and available filters.

In practice

A business asks why a setting changed. The support team reviews the related action and approval record, then shares an appropriate authorised export for the discussion.

Controls & availability

Audit and export access follow the reader’s permissions. An export is a snapshot of the chosen information and does not grant access to hidden customers, secrets or internal data.

Administration

Search

Find customers, devices and incidents from the dashboard, with supported inventory and device search fields.

Read the full explanation

What it does

Find the right computer or record without remembering where it sits in the navigation. Vycko’s supported search connects names and inventory evidence to devices, customers, incidents and useful destinations in the dashboard.

How you can use it

More than device names. Search supported serial, IP, MAC, operating-system, software and other indexed fields to identify machines from the information you have.
A keyboard route. Use the command palette with Ctrl+K or Cmd+K, navigate results with the keyboard and open the relevant page or device section.
Evidence in the result. See useful matching information and its available freshness context, including supported written-location search.

In practice

A technician has an application name rather than a computer name. Search identifies the devices reporting that software and opens the relevant filtered view.

Controls & availability

Search follows customer scope and supported indexed fields. Old matched readings are marked where applicable; a search result does not mean the computer is currently online.

Ask us about Search

Ask us about API, MCP & webhooks

Administration

API, MCP & webhooks

Connect authorised tools through scoped platform access. Manage keys, connected assistants and supported event delivery.

Read the full explanation

What it does

Connect authorised tools to the platform through supported integration routes. API access supports external workflows, MCP connects compatible assistants to permitted capabilities, and webhooks deliver selected platform events to a configured receiver.

How you can use it

Scoped credentials. Manage supported access keys and permissions so an integration receives the relevant scope instead of an unrestricted operator identity.
Connected assistants. Use the available MCP tools within their configured authority, keeping device work subject to the platform’s applicable controls.
Event delivery. Configure supported signed webhook events, review delivery attempts and failures, and manage signing-secret rotation where needed.

In practice

A support business sends selected alert events to an authorised external workflow, while a connected assistant uses permitted platform tools to help investigate a device.

Controls & availability

Available actions depend on the integration’s permission and current catalogue. Webhook receivers must verify signatures and handle retries; an integration does not bypass customer policy or approval requirements.

Ask us about Platform settings & usage

Administration

Platform settings & usage

Manage policies, AI controls, update settings, catalogue entries, remote access, portal settings and platform usage.

Read the full explanation

What it does

Configure the platform around the service you want to provide. Settings bring the supported customer policies, technical controls and delivery choices into a manageable workspace, while usage information helps administrators understand platform activity.

How you can use it

Care and automation choices. Manage relevant AI controls, alerts, update policies, remediation settings and reviewed catalogue entries.
Access and customer experience. Configure supported remote-access, portal, reporting and integration settings for the intended environment.
Administration and review. Manage available agent, vulnerability-data and warranty-provider settings, and inspect the supported usage or cost information.

In practice

An administrator prepares a new customer by reviewing its action rules, update choices, notification routing and portal access before the managed devices are rolled out.

Controls & availability

Sensitive settings require the applicable administrator permissions and verification. Enabling a setting does not add a capability that the device, agent or configured provider does not support.