{"id":344553,"date":"2026-07-24T10:00:47","date_gmt":"2026-07-24T10:00:47","guid":{"rendered":"https:\/\/scanda.com.mx\/?p=344553"},"modified":"2026-07-29T02:00:10","modified_gmt":"2026-07-29T02:00:10","slug":"reducir-visitas-tecnicas-diagnostico-remoto","status":"publish","type":"post","link":"https:\/\/scanda.com.mx\/en\/reduce-technical-visits-for-remote-diagnostics\/","title":{"rendered":"How to reduce unnecessary technical visits with remote diagnosis?"},"content":{"rendered":"<p class=\"wp-block-paragraph\">Remote diagnostics reduces technical visits when it connects reliable inventory, telemetry, secure access, automation, and operational knowledge. The goal is not to prevent in-person support, but to reserve it for incidents that truly require physical intervention, reducing MTTR, order costs, reoccurrences, and user downtime.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Taxonomic definitions<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Remote diagnosis<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Process by which the support team identifies the likely cause of an incident without physically going to the site. It uses information such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Device status.<\/li>\n\n\n\n<li>System logs.<\/li>\n\n\n\n<li>Hardware and software telemetry.<\/li>\n\n\n\n<li>Use of CPU, memory, storage, and network.<\/li>\n\n\n\n<li>Versions and patches installed.<\/li>\n\n\n\n<li>Security events.<\/li>\n\n\n\n<li>Incident history.<\/li>\n\n\n\n<li>Endpoint configuration.<\/li>\n\n\n\n<li>Connectivity with applications and services.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Remote diagnosis does not simply mean \u201cconnecting to the device\u201d. It must generate sufficient evidence to decide whether the incident can be resolved, automated, escalated, or requires a visit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. Remote remediation<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remote execution of corrective actions on a technological asset. This may include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Controlled restart of services.<\/li>\n\n\n\n<li>Space release.<\/li>\n\n\n\n<li>Application of configurations.<\/li>\n\n\n\n<li>Reinstatement of agents.<\/li>\n\n\n\n<li>Software distribution.<\/li>\n\n\n\n<li>Renewal of certificates.<\/li>\n\n\n\n<li>Restoration of policies.<\/li>\n\n\n\n<li>Application of patches.<\/li>\n\n\n\n<li>Isolation of compromised endpoints.<\/li>\n\n\n\n<li>Execution of authorized runbooks or scripts.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. Rate of dispatch avoidance<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An indicator that measures the percentage of face-to-face orders avoided thanks to remote diagnosis or resolution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Formula:<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Visits avoided \u00f7 incidents eligible for remote care \u00d7 100<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should not be used as a standalone metric. A high rate accompanied by reoccurrences, dissatisfaction, or unavailability may indicate that necessary visits are being avoided.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Comparative table: models of technical care<\/strong><\/h4>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Variable<\/strong><\/td><td><strong>Model \u201cvisits first\u201d<\/strong><\/td><td><strong>Model remote-first<\/strong><\/td><td><strong>Predictive and automated model<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Technical activation<\/td><td>With limited information<\/td><td>After the remote diagnosis<\/td><td>Only when automation cannot prevent or solve<\/td><\/tr><tr><td>Inventory<\/td><td>Manual or outdated<\/td><td>Integrated with CMDB and UEM<\/td><td>Continuously updated with telemetry<\/td><\/tr><tr><td>Diagnosis<\/td><td>Mainly on site<\/td><td>Remote before the office<\/td><td>Proactive through events and anomalies<\/td><\/tr><tr><td>Resolution<\/td><td>Dependent on the technician<\/td><td>Remote remediation or informed visit<\/td><td>Self-healing, runbooks, and operational AI<\/td><\/tr><tr><td>Spare parts<\/td><td>They are identified during the visit<\/td><td>They are validated before the transfer<\/td><td>They are predicted by history and condition<\/td><\/tr><tr><td>First-time fix<\/td><td>Variable<\/td><td>Mayor by previous evidence<\/td><td>Optimized through analytics<\/td><\/tr><tr><td>Cost per incident<\/td><td>High and unpredictable<\/td><td>Controlled<\/td><td>Optimized by automation<\/td><\/tr><tr><td>Risk of a second visit<\/td><td>High<\/td><td>Medium or low<\/td><td>Low<\/td><\/tr><tr><td>User experience<\/td><td>Prolonged waiting<\/td><td>Faster resolution<\/td><td>Prevention of interruptions<\/td><\/tr><tr><td>Executive visibility<\/td><td>Closed orders<\/td><td>MTTR, remote resolution and cost<\/td><td>Productivity, availability and trends<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00a0<strong>Why unnecessary technical visits affect business<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A technical visit does not only represent the cost of a transfer. Its full cost includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Time of Service Desk staff.<\/li>\n\n\n\n<li>Hours of the field coach.<\/li>\n\n\n\n<li>Travel expenses, transportation or mileage.<\/li>\n\n\n\n<li>Coordination and assignment.<\/li>\n\n\n\n<li>Spare parts logistics.<\/li>\n\n\n\n<li>Time to access the location.<\/li>\n\n\n\n<li>Accumulated hours of unavailability.<\/li>\n\n\n\n<li>Lost user productivity.<\/li>\n\n\n\n<li>Sales, production or attention withheld.<\/li>\n\n\n\n<li>Risk of a second visit.<\/li>\n\n\n\n<li>Penalties associated with SLA.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In a distributed operation, a model based on \u201csending someone to check\u201d scales poorly. Each new store, branch, plant, hotel, clinic, cashier, or point of sale multiplies the potential number of trips.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Furthermore, when the technician arrives without knowing the configuration, the history, the warranty, or the repairs required, the visit becomes an activity of diagnosis rather than resolution. It is the technological equivalent of calling the plumber without telling him where the leak is: he will come, yes; fixing it right away is another matter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In operational cases documented by Kenos, the unified management of POS, kiosks, and endpoints achieved a 37% reduction in MTTR, complete inventory, and fewer unscheduled visits. In multi-site Field Service operations, a 25% reduction in operational cost and 90% control over assets were reported.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What causes lead to avoidable visits<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lack of reliable inventory<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The support team does not know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Model and serial number.<\/li>\n\n\n\n<li>Operating system.<\/li>\n\n\n\n<li>Software installed.<\/li>\n\n\n\n<li>State of guarantee.<\/li>\n\n\n\n<li>Current location.<\/li>\n\n\n\n<li>Responsible user.<\/li>\n\n\n\n<li>Maintenance history.<\/li>\n\n\n\n<li>Network configuration.<\/li>\n\n\n\n<li>Level of patching.<\/li>\n\n\n\n<li>Relationship with other assets.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Without this information, the office is used to \u201cdiscover\u201d the environment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Tickets with insufficient information<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Requests such as \u201cit doesn\u2019t work\u201d, \u201cit\u2019s slow\u201d or \u201cI don\u2019t have a system\u201d do not allow us to determine:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which service is affected.<\/li>\n\n\n\n<li>Since when?.<\/li>\n\n\n\n<li>How many users it affects.<\/li>\n\n\n\n<li>Whether the problem is local or general.<\/li>\n\n\n\n<li>If there is connectivity.<\/li>\n\n\n\n<li>What error message appears.<\/li>\n\n\n\n<li>What changes have occurred recently.<\/li>\n\n\n\n<li>What actions have already been attempted.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Disconnected tools<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When ITSM, UEM, observability, CMDB, security, and Field Service operate as silos, the agent must consult different consoles or request information manually.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The result is predictable:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Greater time for diagnosis.<\/li>\n\n\n\n<li>Unnecessary escalations.<\/li>\n\n\n\n<li>Work duplication.<\/li>\n\n\n\n<li>Decisions of dispatch without evidence.<\/li>\n\n\n\n<li>Different information between the Service Desk and field technicians.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lack of runbooks<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The recurring problems are analyzed from scratch again. Without standardized procedures, the result depends on the memory of the agent or the technician available.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Poorly designed shipping rules<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some organizations send technicians based solely on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The user's insistence.<\/li>\n\n\n\n<li>The hierarchy of who reports.<\/li>\n\n\n\n<li>The ticket's age.<\/li>\n\n\n\n<li>The imminent non-compliance with the SLA.<\/li>\n\n\n\n<li>The lack of response from the first level.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These conditions may justify an escalation, but they do not prove that physical presence is necessary.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to implement a remote-first model<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Build a reliable operational inventory<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first requirement is to know what is being supported.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The inventory must include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hardware.<\/li>\n\n\n\n<li>Software.<\/li>\n\n\n\n<li>Operating systems.<\/li>\n\n\n\n<li>Versions.<\/li>\n\n\n\n<li>Guarantees.<\/li>\n\n\n\n<li>Critical applications.<\/li>\n\n\n\n<li>Locations.<\/li>\n\n\n\n<li>Users.<\/li>\n\n\n\n<li>Peripherals.<\/li>\n\n\n\n<li>Administrative agents.<\/li>\n\n\n\n<li>State of security.<\/li>\n\n\n\n<li>Departments.<\/li>\n\n\n\n<li>Compatible spare parts.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The information must be updated automatically through Endpoint Management tools, asset discovery, and reconciliation with the CMDB.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An inventory that is updated once a year serves for historical auditing, not for diagnosing an incident that occurred this morning.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. Categorizing incidents that are candidates for remote resolution<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Not all incidents should be treated equally. A taxonomy is necessary.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>High resolution resolution viability remotely<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Passwords and access.<\/li>\n\n\n\n<li>Incorrect settings.<\/li>\n\n\n\n<li>Services suspended.<\/li>\n\n\n\n<li>Applications blocked.<\/li>\n\n\n\n<li>Caches or storage is saturated.<\/li>\n\n\n\n<li>Outdated agents.<\/li>\n\n\n\n<li>Printing errors related to software.<\/li>\n\n\n\n<li>Installation or reinstalling applications.<\/li>\n\n\n\n<li>VPN configuration.<\/li>\n\n\n\n<li>Implementation of policies.<\/li>\n\n\n\n<li>Certificate errors.<\/li>\n\n\n\n<li>Performance problems.<\/li>\n\n\n\n<li>Pending patches.<\/li>\n\n\n\n<li>Synchronization problems.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Conditional viability<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Intermittent network failure.<\/li>\n\n\n\n<li>Unrecognized peripherals.<\/li>\n\n\n\n<li>Power problems.<\/li>\n\n\n\n<li>Printers with physical alerts.<\/li>\n\n\n\n<li>POS or kiosks with degradation.<\/li>\n\n\n\n<li>Discs with errors.<\/li>\n\n\n\n<li>Overheating.<\/li>\n\n\n\n<li>Problems with local links.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These incidents can be diagnosed remotely, although they may eventually require in-person intervention.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Low resolution resolution feasibility<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Team without energy.<\/li>\n\n\n\n<li>Physical injury.<\/li>\n\n\n\n<li>Wiring is broken.<\/li>\n\n\n\n<li>Broken screen.<\/li>\n\n\n\n<li>Replacement of components.<\/li>\n\n\n\n<li>Theft or loss.<\/li>\n\n\n\n<li>Spill of liquids.<\/li>\n\n\n\n<li>Team that does not turn on and lacks off-field management.<\/li>\n\n\n\n<li>Physical facilities.<\/li>\n\n\n\n<li>Mechanical maintenance.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Even in these cases, the previous diagnosis helps to send the right technician with the necessary tools and equipment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. Defining a minimum package of evidence<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before authorizing a visit, the ticket must contain:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Affected asset.<\/li>\n\n\n\n<li>Location.<\/li>\n\n\n\n<li>User or local responsible.<\/li>\n\n\n\n<li>Business service affected.<\/li>\n\n\n\n<li>Starting time.<\/li>\n\n\n\n<li>Visual evidence or error message.<\/li>\n\n\n\n<li>State of connectivity.<\/li>\n\n\n\n<li>Telemetry of the endpoint.<\/li>\n\n\n\n<li>Recent changes.<\/li>\n\n\n\n<li>Actions taken.<\/li>\n\n\n\n<li>Result of the runbooks.<\/li>\n\n\n\n<li>Hypothesis of cause.<\/li>\n\n\n\n<li>Possible rework.<\/li>\n\n\n\n<li>Priority level.<\/li>\n\n\n\n<li>Maximum tolerable time of interruption.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This control prevents the visit from being used as a substitute for diagnosis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>4. Integrate Service Desk, UEM and Field Service<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The recommended flow is:<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>The user reports the incident through the portal, chat, voice, email, or an authorized channel.<\/li>\n\n\n\n<li>The ITSM identifies the user, the active device, the location, and the affected service.<\/li>\n\n\n\n<li>The UEM platform checks the status of the device.<\/li>\n\n\n\n<li>Observability and security add relevant events.<\/li>\n\n\n\n<li>The agent executes the corresponding runbook.<\/li>\n\n\n\n<li>Automation attempts a safe remedy.<\/li>\n\n\n\n<li>If it is not resolved, it is determined whether it requires logical escalation or physical presence.<\/li>\n\n\n\n<li>Field Service receives the order with the required evidence, skills, and equipment.<\/li>\n\n\n\n<li>The technician documents the solution and updates the knowledge base.<\/li>\n\n\n\n<li>Problem Management analyzes recurrences and opportunities for automation.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Kenos articulates Service Desk, Endpoint Management, Field Service, automation, analytics, and AI under a single governance model, with shared metrics and an Outcome Owner responsible for the result.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>5. Automate repetitive problems<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The initial candidates must be selected by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>High volume.<\/li>\n\n\n\n<li>Low complexity.<\/li>\n\n\n\n<li>Stable procedure.<\/li>\n\n\n\n<li>Risk controlled.<\/li>\n\n\n\n<li>High success rate.<\/li>\n\n\n\n<li>Reverse capability.<\/li>\n\n\n\n<li>Significant impact in time or cost.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Restarting an authorized service.<\/li>\n\n\n\n<li>Clean up temporary files.<\/li>\n\n\n\n<li>Renew policies.<\/li>\n\n\n\n<li>Reinstall an agent.<\/li>\n\n\n\n<li>Validate connectivity.<\/li>\n\n\n\n<li>Repairing an application.<\/li>\n\n\n\n<li>Correcting configurations.<\/li>\n\n\n\n<li>Apply an update.<\/li>\n\n\n\n<li>Unleash a tail.<\/li>\n\n\n\n<li>Restoring a component.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Each automation must include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Entry conditions.<\/li>\n\n\n\n<li>Previous validations.<\/li>\n\n\n\n<li>Permits required.<\/li>\n\n\n\n<li>Share registration.<\/li>\n\n\n\n<li>Criteria for success.<\/li>\n\n\n\n<li>Reversal mechanism.<\/li>\n\n\n\n<li>Escalation in case of failure.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>6. Implement a control gate for dispatching<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An in-person order should be authorized when at least one condition is met:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>There is evidence of physical harm.<\/li>\n\n\n\n<li>The asset cannot be administered remotely.<\/li>\n\n\n\n<li>Recovery requires replacement.<\/li>\n\n\n\n<li>Local connectivity prevents access.<\/li>\n\n\n\n<li>The intervention involves wiring or infrastructure.<\/li>\n\n\n\n<li>The runbook was executed unsuccessfully.<\/li>\n\n\n\n<li>The recovery time would far exceed the tolerable impact.<\/li>\n\n\n\n<li>There is a contractual or regulatory obligation.<\/li>\n\n\n\n<li>The risk of continuing to operate exceeds the cost of the visit.<\/li>\n\n\n\n<li>Custody or physical evidence is required.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The rule should not be \u201cdo not send technicians,\u201d but \u201csend them with a hypothesis, a refinement, and an expected result.\u201d.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>7. Protect remote access<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Remote diagnosis also creates risks. The model must apply:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Individual identities.<\/li>\n\n\n\n<li>Multi-factor authentication.<\/li>\n\n\n\n<li>Access based on roles.<\/li>\n\n\n\n<li>Minimum privileges.<\/li>\n\n\n\n<li>Recorded sessions.<\/li>\n\n\n\n<li>User approval when appropriate.<\/li>\n\n\n\n<li>Encryption of communications.<\/li>\n\n\n\n<li>Restrictions based on location or device.<\/li>\n\n\n\n<li>Temporary access.<\/li>\n\n\n\n<li>Separation of functions.<\/li>\n\n\n\n<li>Registration on the ticket.<\/li>\n\n\n\n<li>Automatic revocation of privileges.<\/li>\n\n\n\n<li>Integration with EDR or XDR.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A generic shared account should never be used to manage all devices. It reduces access and increases the security incident cost.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to measure the financial impact<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Operational indicators<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Percentage of remote resolution.<\/li>\n\n\n\n<li>Visits avoided.<\/li>\n\n\n\n<li>Remote MTTR.<\/li>\n\n\n\n<li>MTTR in person.<\/li>\n\n\n\n<li>First contact resolution.<\/li>\n\n\n\n<li>First-time fix.<\/li>\n\n\n\n<li>Reincidences at 7, 15 and 30 days.<\/li>\n\n\n\n<li>Faultless orders found.<\/li>\n\n\n\n<li>Second visit.<\/li>\n\n\n\n<li>Travel time.<\/li>\n\n\n\n<li>User waiting time.<\/li>\n\n\n\n<li>Compliance with SLA.<\/li>\n\n\n\n<li>User experience.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Economic indicators<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Total cost per visit.<\/li>\n\n\n\n<li>Cost per incident.<\/li>\n\n\n\n<li>Cost per location.<\/li>\n\n\n\n<li>Cost per asset.<\/li>\n\n\n\n<li>Productive hours recovered.<\/li>\n\n\n\n<li>Avoided penalties.<\/li>\n\n\n\n<li>Cost of urgent spare parts.<\/li>\n\n\n\n<li>Spending by suppliers.<\/li>\n\n\n\n<li>TCO of the service.<\/li>\n\n\n\n<li>Estimated impact on EBITDA.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Direct savings formula<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Visits avoided \u00d7 average total cost per visit<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The total cost must take into account transportation, hours, coordination, spare parts, suppliers, and administration.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Formula of recovered productivity<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hours of unavailability avoided \u00d7 affected users \u00d7 labor cost per hour<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For point of sale, production, or customer service, the marginal contribution or the potential revenue committed must be added.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Relevant data for the decision<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>In a distributed retail operation documented by Kenos, a 37% reduction in MTTR, complete inventory, and fewer unscheduled visits were achieved.<\/li>\n\n\n\n<li>In Field Service multidesks, a reduction of 25% in operational cost and 90% in asset control was documented.<\/li>\n\n\n\n<li>In Service Desk, 30% automation was achieved and a 20% reduction in TCO was achieved.<\/li>\n\n\n\n<li>The operation reported by Kenos includes more than 600,000 monthly monitoring points, 25,000 points of sale and 98% asset aggressiveness.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These data should not be used as a universal promise. They serve as evidence of what can be achieved when inventory, remote support, automation, and field care are managed as a single operation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The role of Scanda<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Scanda facilitates the transition from a reactive support to a frictionless productivity model through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Diagnosis of maturity.<\/li>\n\n\n\n<li>Inventory normalization.<\/li>\n\n\n\n<li>Integration of ITSM, CMDB, UEM and Field Service.<\/li>\n\n\n\n<li>Design of taxonomies.<\/li>\n\n\n\n<li>Automation of repetitive incidents.<\/li>\n\n\n\n<li>Implementation of runbooks.<\/li>\n\n\n\n<li>Government of remote access.<\/li>\n\n\n\n<li>Executive boards.<\/li>\n\n\n\n<li>Analytic of recurrences.<\/li>\n\n\n\n<li>Priority given to impact.<\/li>\n\n\n\n<li>Supplier management.<\/li>\n\n\n\n<li>Continuous improvement.<\/li>\n\n\n\n<li>Controlled use of AI for classification, recommendation, and remediation.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The Scanda model is not limited to installing tools. It assigns a Business Advisor or Outcome Owner to connect availability, productivity, security, experience, and cost with the indicators reviewed by the management.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Predictive conclusion<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Organizations with distributed operations will move towards models where technical visits are the informed exception and not the default response. The combination of telemetry, UEM, observability, runbooks, AI, and Field Service will enable resolving more incidents before deploying personnel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Companies that do not incorporate these capabilities will continue to pay for in-person diagnostics, follow-up visits, and wasted time that could have been avoided. The cost will not only appear in the IT budget: it will be reflected in productivity, sales, production, experience, and operating margin.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>FAQ<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. Can remote diagnosis eliminate all technical visits?<\/strong> No. Its goal is to eliminate avoidable visits and better prepare for those that are necessary. Physical damage, replacements, wiring, power, and infrastructure interventions will still require a presence. The difference is that the technician will arrive with the appropriate information, skills, and spare parts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. What technology does a company need to start?<\/strong> At a minimum, it needs ITSM, reliable inventory, remote endpoint management, access controls, telemetry, and a knowledge base. For scaling, it is recommended to integrate CMDB, UEM, observability, automation, and Field Service Management.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. How is the ROI of remote diagnosis demonstrated?<\/strong> The baseline of visits, MTTR, cost per order, reoccurrences, and non-productive hours are compared with the subsequent period. The economic benefit includes avoided visits, reduced suppliers, lower unavailability, and improved productivity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How many of your technical visits begin without a complete diagnosis?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Scanda can analyze your tickets, assets, locations, field orders, and service levels to identify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incidents that can be resolved remotely.<\/li>\n\n\n\n<li>Visits that could be avoided.<\/li>\n\n\n\n<li>Problems candidates for automation.<\/li>\n\n\n\n<li>Causes of recidivism.<\/li>\n\n\n\n<li>Opportunities to improve first-time fix.<\/li>\n\n\n\n<li>Potential impact on MTTR, productivity, and TCO.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Schedule an executive session with Scanda and build a 90-day roadmap to reduce friction, unnecessary visits, and support costs.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"<p>El diagn\u00f3stico remoto reduce visitas t\u00e9cnicas cuando conecta inventario confiable, telemetr\u00eda, acceso seguro, automatizaci\u00f3n y conocimiento operativo. El objetivo no es impedir el soporte presencial, sino reservarlo para incidentes que realmente requieren intervenci\u00f3n f\u00edsica, disminuyendo MTTR, costo por orden, reincidencias y horas improductivas del usuario. Definiciones taxon\u00f3micas 1. Diagn\u00f3stico remoto Proceso mediante el cual el [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":344554,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-344553","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/posts\/344553","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/comments?post=344553"}],"version-history":[{"count":1,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/posts\/344553\/revisions"}],"predecessor-version":[{"id":344555,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/posts\/344553\/revisions\/344555"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/media\/344554"}],"wp:attachment":[{"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/media?parent=344553"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/categories?post=344553"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scanda.com.mx\/en\/wp-json\/wp\/v2\/tags?post=344553"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}