Infrastructure and support · Tajikistan
IT support for organisations. Workstations, networks and staff requests within an agreed area of responsibility.
01 / Service scope
Support starts with boundaries: the systems covered, who has access and which tasks need a separate project. The contract should describe actual work, not a promise to solve every issue instantly.
Staff assistance and basic maintenance.
We list computers, software and typical requests, clarifying updates, peripheral connections and specialist software suppliers’ involvement. Passwords and access are transferred through agreed channels, never the general website form.
Networks, servers and backups.
We record connection diagrams, equipment owners and administration boundaries. Having a backup does not prove recoverability: the test method and frequency need checking. Replacement, upgrades and emergency work are defined separately.
Clear channels and agreed expectations.
Agree support hours, priorities, response times and on-site needs. A server outage and connecting a mouse have different impacts. Response and resolution time are different measures; both depend on the contract and external factors, including parts and connectivity providers.
02 / Process
The details needed to get started.
Review staff numbers, workstations, servers, networking and applications. Discuss current requests and coordination with your IT specialist.
A clear scope and estimate.
Define supported systems, access, request channels and exclusions. Response time and resolution time are agreed as separate conditions.
Agree costs and changes before proceeding.
Agree recurring support and separate project tasks. Access to systems is provided through an approved process rather than the public form.
Check the result against the agreed task.
Verify the completed task and record follow-up actions. Infrastructure changes and new responsibilities are discussed separately.
03 / Result
Support should provide an agreed process and clear responsibility for systems. Requests, access, changes and visit conditions should follow your contract.
04 / Pricing
Cost depends on users, locations, critical systems and support hours. Visits, upgrades, emergency work and third-party involvement are identified within the agreed scope.
We handle enquiries from almost all of Tajikistan. Delivery, handover or an on-site visit, if needed, are agreed for your city in advance. Terms depend on the address, task and specialist availability; this page does not imply identical service times in every locality.
05 / Useful information
Yes, tasks and access can be divided. Define who makes decisions, approves changes and works with suppliers.
Support hours and out-of-hours availability are defined in the contract. This page does not promise a 24/7 SLA.
User and site counts, critical systems, current problems and required hours. An equipment inventory without passwords is useful.
Response means starting to handle a request; resolution means restoring the agreed function. Conditions may differ by priority; parts, providers and site access affect resolution time.
Let’s discuss the next step
State user and site counts, key applications, servers and current issues. Add business hours and any internal IT specialist’s role; do not send passwords.
+992 44 655 00 00info@nekon.tj
