Frequently Asked Questions
Clear answers to the most common questions.
SLA (Response and Resolution Times)
Critical?
Maximum of 4 h for the initial response, subject to the terms of the contract.
Standard?
Between 24 and 48 h maximum for the initial response, subject to the terms of the contract.
What is the actual average time?
Practically immediate when the client's operations are halted.
What are your business hours?
Monday to Friday, from 8:00 AM to 7:00 PM, and Saturdays from 10:00 AM to 1:30 PM and 4:00 PM to 7:00 PM.
Proactivity
- NinjaOne to keep the entire IT infrastructure monitored, updated, and supervised. Specific software with highly restricted access for critical environments, such as hypervisors and the network core.
How many problems do we detect before they impact the client?
We proactively install all updates, perform preventive consultancy, review equipment status, and monitor system security.
Do we include:
Monthly review?
Yes
Reports?
Quarterly
Improvement proposals?
Yes
Security and Backups
- We always manage them based on recommendations and best practices, agreed upon with the client regarding the extent to which they want us to assist with backups.
How do we manage backups?
- NinjaOne to keep the entire IT infrastructure monitored, updated, and supervised.
- Specific software with highly restricted access for critical environments, such as hypervisors and the network core.
Do we perform recovery simulations?
Yes (frequency is agreed upon with the client)
Is cybersecurity included or is it an extra?
Our IT support proposals always include a next-generation cybersecurity solution integrated with our monitoring systems. We work with both traditional antivirus and advanced EDR/XDR solutions that provide a global view of the client's network.
Cloud and Traditional Infrastructure
On which platform do you deploy infrastructures?
As a Proxmox Silver Partner, we always deploy infrastructures on this platform, adapting to the needs of each client.
Where can the infrastructures be hosted?
Depending on the client's needs, we can deploy the infrastructure in a local DC, a client DC, or a hyperscaler such as OVHCloud.
Are the servers shared or dedicated?
We work on physical servers that are 100% dedicated to the project and managed directly by us.
Do you have an option for smaller infrastructures?
Yes. For smaller infrastructures, such as environments with 2 or 3 virtual servers, we offer the possibility of deploying them on Telemàtic's managed cloud.
What solutions do you offer for collaboration and modern work?
Our primary solution is Microsoft 365. We help clients implement or migrate their email system and collaboration tools to improve efficiency and productivity.
Do you also handle Microsoft 365 backups?
Yes. We also handle Microsoft 365 backups, a necessary service that is not always considered but is important for protecting company information.
Team and Assignment
Transparency and Reporting
Monthly reports?
Yes, depending on the negotiated contract.
Resolved tickets?
Yes, within the SLAs established according to the agreed conditions.
Response times?
Yes, within the SLAs established according to the agreed conditions.
Pricing Model
Case Studies and References
Scalability
What if we go from 10 to 50 users?
We resize the project and adapt to the new situation.
What if we open new offices?
We resize the project and adapt to the new situation.
Contract and Exit
Incident Reporting Procedure
This is the only valid channel to activate the support service.
Step 1. Access the Support Portal
Access our website www.telematic.tech and click the button (at the top right):
Open Ticket
You can also send an email to:
suport@gruptelematic.net (the system will automatically generate the ticket)
Step 2. Detailed Description of the Incident
To speed up the resolution, please indicate:
- Company and contact person
- Affected equipment or user
- Clear description of the problem
- Error message (if any) (share screen)
Step 3. Classification and Response According to SLA
Once the ticket is received:
- It is registered in the system
- It is classified according to criticality
- The response time is activated according to your SLA (by contract type)
Critical Incident
Total service interruption or general impact.
Priority activation according to the contracted SLA.
General Incident
Partial or individual impact.
Management within established timeframes.
To guarantee:
- Compliance with response times
- Registration and traceability
- Internal coordination of the technical team
If it is a critical incident that completely halts your activity, you can:
- Open the ticket immediately
- Clearly indicate "CRITICAL INCIDENT" in the title



