Frequently asked questions

BlueNova provides support in English and Spanish on weekdays from 09:00 to 18:00 CET. Any other language or out-of-hours coverage is defined in the contracted scope and agreed hours, so confirm it before relying on it.

The service is structured with a help desk and ticket management, with agreed communication channels and remote support. When the situation requires it, on-site assistance is available to speed up resolution.

SLAs are defined by criticality within the managed services model. Priority attention is given, cases are tracked, and escalation is applied when necessary to meet committed response times.

Yes, within the contracted scope, security and continuity are integrated: monitoring, protection, and backups. This helps reduce risks while incidents are being handled and corrective actions are carried out.

When the case requires it, escalation is carried out to specialists and/or third parties according to the agreed model. The goal is to resolve issues with technical judgment without blocking operations due to a lack of expertise.

BlueNova confirms English and Spanish support on weekdays from 09:00 to 18:00 CET. Confirm any other language or out-of-hours coverage before depending on it.

Ask the user directly and record the preference in the request so routing does not rely on location or assumptions.

The goal, impact, steps tried, exact error text, affected assets and next owner. Keep commands and identifiers exact.

A reviewed glossary keeps recurring terms consistent and helps preserve meaning across support conversations and knowledge articles.

Have a fluent reviewer validate technical terms and ask representative users to follow the instructions, then record ownership and revision date.

They are the set of activities to maintain, manage, and resolve a company's technology environment. They include helpdesk, maintenance, infrastructure support, and application support.

It is an organized way of providing assistance and maintenance for systems and devices. Scope, delivery mode (remote/on-site), service levels, and contracting terms are typically defined.

It refers to technical assistance (support) and maintenance and improvement tasks (services). The goal is to reduce downtime, ensure performance, and manage risks.

It is the assistance for diagnosing and resolving incidents and requests. It can cover hardware, software, networks, WiFi, and configuration, with ticket management and reporting.

A concise description, affected service, impact, urgency, useful error details and a safe way to follow up. Do not include passwords or unnecessary personal data.

First response records an initial acknowledgement or action. Resolution records when the issue is considered addressed under the agreed process. Define both consistently.

Escalate when impact, security risk, specialist access or elapsed time crosses an agreed trigger, and transfer ownership with the evidence already collected.

Backlog age, ticket volume by type, reopen rate and response or resolution times can help when definitions and scope are consistent.

Use an agreed inventory, knowledge transfer, access approvals, routing rehearsal, named owners and a process for open issues.

The salary range varies depending on experience, specialization (L1, L2, infrastructure), and work mode (on-site or remote). To estimate a realistic budget, it is advisable to compare similar profiles and the level of responsibility of the role.

IT support is the service that helps users and teams resolve incidents and keep systems running. It includes a help desk, diagnostics, technical escalation, and preventive maintenance.

It is the part of the service focused on resolving technical problems: applications, networks, servers, devices, and communications. It is usually organized by tiers (T1, T2, T3) to ensure response times and quality.

The best-known European employment network is EURES. It is used for information and searching for job opportunities across different countries.

List covered users, locations, systems, channels, operating hours, languages, exclusions and escalation ownership.

Ask for a location and time-zone matrix, named service hours, language availability and an example escalation path. Verify each item against the written scope.

They use different skills and access levels. Defining the boundary clarifies routing, approval and responsibility for complex changes.

Include inventories, access, knowledge transfer, open risks, acceptance criteria, owners and a fallback route.

No. Confirm which work is remote, where on-site visits are available, how they are arranged and what response expectations apply.

You need a vulnerability management program with periodic scanning, risk-based prioritization, and remediation with verification. Complement this with layered hardening and update tracking to reduce exposure.

A scan identifies known weaknesses in an automated way; a penetration test validates exploitability within a defined scope; a red team simulates more realistic attacks to assess detection and response. The choice depends on the objective and the level of risk.

The response includes containment, eradication, and recovery, with defined roles and timelines. Recovery is supported by tested backups and restoration procedures to minimize impact.

Yes, through control mapping, documentation, and operational evidence. The goal is to align technical and governance measures with applicable requirements and data protection standards.

In hybrid environments, controls are integrated across cloud and on-premise systems, and validated through testing and configuration verification. For OT/IoT, a specific scope and security criteria adapted to the environment are required.

Inventory critical assets, review access, check patching and backups, then assess incident-response readiness.

Depending on the agreed scope, it can include log collection, alert triage, investigation and an escalation process. Confirm hours and responsibilities in writing.

Vulnerability management is continuous: identify, prioritise, remediate, and verify fixes. Penetration testing is periodic and risk-based, focusing on validating exploitability and improving controls.

Compliance depends on the organisation’s obligations and actual operations. A provider can contribute controls and evidence, but any compliance claim must be checked in context.

Access management improvements typically include MFA/SSO rollout and role-based access reviews. Least-privilege is assessed by analysing identities, permissions, and privileged access paths, then tightening entitlements.

IT infrastructure is the set of technological resources that support an organization's systems: networks, servers, storage, devices, and associated services. Its purpose is to enable applications and processes to operate with availability, performance, and security.

It is the set of activities involved in operating and maintaining infrastructure in a controlled manner: monitoring, preventive maintenance, change and incident management, and security tasks such as patching and access control. Its aim is to reduce risks and improve continuity.

It is a model in which a provider assumes operational responsibility for the infrastructure, with defined processes and routines. It typically includes monitoring, support, maintenance, reporting, and compliance with agreed SLAs.

These are outsourced services designed to maintain and proactively improve IT environments. They usually cover continuous operations, task automation, incident response, security, and business continuity, with defined metrics and deliverables.

Typically it covers servers, operating systems, storage, network connectivity, monitoring, and operational processes like help desk, incident handling and maintenance. For hybrid setups, it also includes cloud workload operations and continuity practices.

A managed service should define monitoring coverage, alert severity levels, triage steps and escalation routes. SLAs should specify response and resolution targets, plus how incidents move between tiers.

Yes, the best approach provides consistent operational controls across on-prem and cloud. This includes unified monitoring, access governance, and coordinated maintenance and recovery across environments.

Define the service scope, hours, priorities, contact channels, escalation rules and responsibilities in writing.

Expect layered security controls, backup strategy and disaster recovery readiness aligned to your data protection needs. Reporting should show backup health, recovery testing approach and compliance-relevant evidence.

Repetitive tasks and operational decisions can be automated: lead classification, assisted responses, incident triage, draft generation, and coordination between systems. The key is to define the workflow and measure the impact.

Common examples include lead follow-up via email and WhatsApp, chatbots with escalation to support, appointment reminders with calendar integration, and content automation with approval workflows. All integrated with CRM and existing tools.

They are platforms and workflows that combine rules, triggers, and intelligence to execute processes. They can be orchestrated with tools like Make or n8n, or integrated with systems such as Odoo and CRM.

A practical way to group them is: process automation (workflows), customer service automation (chatbots and self-service), decision automation (prioritization and prediction), and content/marketing automation (generation and scheduling).

It is not always required, but in most cases it provides traceability and improves the quality of workflows. If you already have a CRM, integration is usually the point of greatest return.

Start with an AI readiness assessment to confirm data quality, integration feasibility, and governance requirements. Then define 1–2 high-impact workflows for a pilot with clear success metrics.

Most organisations should begin with a pilot to validate assumptions, acceptance criteria, and ROI baselines. Full implementation follows once the workflow is reliable, secure, and measurable.

Agree on a baseline and track metrics such as time saved, throughput, reduced overhead, error rates, and revenue or pipeline impact. Report on a fixed cadence with transparent methodology.

Project delivery focuses on a defined scope and timeline (e.g., pilot and production release). A retainer supports ongoing optimisation, new automations, monitoring, and continuous governance.

At minimum, name business owners and data owners. Integrations, access and ongoing maintenance also need clear ownership.

They are the set of activities for designing, implementing, operating, and maintaining a company's connectivity. They include monitoring, change management, security, and incident response to sustain performance and availability.

They are the set of components and elements that enable communication between users, applications, and devices. They include physical foundations, active equipment, configuration, and in many cases, security layers.

It is an offering that manages a complete technology environment so that it operates in line with business objectives. In networking, this translates into continuous operation, preventive maintenance, and risk control.

They are typically grouped into design and engineering, implementation and integration, operations (monitoring and fault management), and security. Proactive maintenance and continuity are also included.

Typically, services include discovery and assessment, engineering and design, installation and integration, validation, and then managed monitoring and maintenance. The goal is to keep connectivity reliable, secure and aligned to business needs.

Monitoring can identify faults and performance changes. Any availability improvement depends on how alerts are acted on, maintenance procedures and the network design; monitoring does not guarantee uptime.

Yes. A complete service usually covers both wired and wireless, including access point placement, integration with the switching/routing layer, and validation of coverage and performance for real user traffic.

Many providers can implement SDN/SD-WAN to improve traffic control, segmentation and application performance. Security benefits come from consistent policy enforcement and better isolation between users, devices and applications.

Look for clear delivery stages, operational coverage, proactive maintenance capability, and trust signals such as experience, operational centres and measurable service outcomes. Also confirm security integration and support model fit for your locations.

They are managed services that operate infrastructure and applications in cloud environments, including support, security, and continuity. The provider takes on operational tasks with an SLA, while the client retains control of the business direction.

The most common ones are grouped into IaaS (infrastructure), PaaS (platform), SaaS (applications), and management services such as backup, security, and continuity. In Cloud IT Services, these are combined with operations and support.

They are typically described as IaaS, PaaS, SaaS, and management/operations services (such as backup, DR, security, and monitoring). A managed offering integrates several of these with clearly defined responsibilities.

It depends on the objective, but SaaS for productivity, IaaS for infrastructure flexibility, and managed security and continuity services are frequently highlighted. The key is that they are aligned with SLA, compliance, and RTO/RPO requirements.

SaaS delivers the full application as a service, with the provider handling most operations. PaaS gives a platform for building and running apps, while IaaS provides infrastructure where you manage more of the stack. The key difference is the responsibility split and operational burden.

Most cloud services scale on demand and follow pay-as-you-go consumption models. In managed delivery, governance and monitoring help prevent cost surprises by setting budgets, alerts and optimisation actions. This turns scalability into predictable operational planning.

Security is shared, but responsibilities vary by service model. Providers typically secure the underlying infrastructure, while customers manage identity, access policies, data handling and configuration. Managed services make this operational through controls, monitoring and documented processes.

Yes. A robust IT Cloud Services approach combines backup, replication and tested recovery procedures. Managed delivery should include lifecycle policies, recovery objectives, and periodic recovery drills to prove readiness—not just store backups.

Expect a structured lifecycle: discovery and assessment, target architecture and governance, migration planning, transition into managed operations, and continuous improvement. The engagement should define SLAs, escalation paths, security controls and cost governance for day-to-day running.

It is a comprehensive project that designs and installs a voice and data infrastructure with a standardized architecture. It includes cabling, telecommunications rooms, panels, testing, and documentation to facilitate maintenance and expansions.

They are activities that encompass evaluation, design, installation, certification, repair, and maintenance of the connectivity infrastructure. In structured cabling, they are aimed at ensuring performance and operational order.

MDF (Main Distribution Frame) is the main telecommunications distribution point. IDF (Intermediate Distribution Frame) are intermediate points that distribute connectivity to areas or floors, improving organization and scalability.

Voice, data, and network connectivity services can be supported, as well as integrations with security systems and other low-voltage services depending on the design. The choice of fiber or copper depends on the role and requirements of each segment.

Typically it includes design/planning, cable pathway and outlet layout, installation of copper and/or fibre, labelling, and end-to-end testing. A good scope also includes documentation and remediation if results do not meet the required standard.

Agree the appropriate test methods and limits before work begins. Request measured results for each copper or fibre link, with identifiers, equipment details and any remediation records.

The right choice depends on required speeds, channel length, interference environment, and future upgrade plans. A structured cabling design should map your application needs to the appropriate category and installation practices.

Yes, when the cabling design accounts for PoE power delivery, cable performance, and correct topology. The installer should confirm that the channel meets the required electrical and performance criteria for your PoE device mix.

A reliable partner provides a documented link map, test baselines, and a remediation process. For urgent issues, fault isolation uses the test evidence to identify the failing segment quickly, then repairs are verified with retesting.