Free support
0 ₽
Basic consultations by phone and email without a contract. We reply in turn during business hours and guarantee no deadlines.
Ask a questionThe level is chosen by the cost of downtime, not by the size of the company. If an hour without 1C costs more than a month of support, the basic level is not enough.
Free support
0 ₽
Basic consultations by phone and email without a contract. We reply in turn during business hours and guarantee no deadlines.
Ask a questionStandard 24/7 support
response within 1 hour
Requests accepted around the clock, with an on-duty shift at night and at weekends. Response and recovery times are fixed in the contract.
CalculatePremium with a dedicated team
15-minute response
Our own engineers who know your infrastructure, a personal manager and a monthly SLA compliance report.
Discuss the termsPriority is assigned by the impact on the business, not by who submitted the request. Both deadlines, response and recovery, follow from the priority.
The response time is counted from the moment the request is registered, not from the moment an engineer becomes free. So a request submitted at 3 in the morning falls under the same target as a daytime one, on a 24/7 level.
Every request goes through the same four steps regardless of the channel: phone, email or the portal.
The request gets a number and a timestamp. From that second the SLA response clock is running.
The duty engineer assesses the impact on the business and assigns a priority using the matrix above.
The first line handles the routine and anything complex goes to a specialist engineer. You can see the status at any moment.
A request is closed once you confirm it. Recurring incidents are reviewed separately.
The breach is recorded in the monthly report and under the contract we pay a penalty, usually calculated as a percentage of the monthly fee for that period. The obligation is one-sided: the penalties are in your favour, not ours.
The initial priority is set by the duty engineer using the matrix, but you can raise it. If you believe the issue is more critical than we judged, just say so: we will not argue and will raise the priority.
No. Response is when an engineer picks up the request and contacts you. Recovery is when the service works again. The second is always longer and is affected by factors outside our control, such as waiting for a spare part or for the provider to reply. Such pauses are not counted in the SLA.
Yes, moving to a higher level is arranged by a supplementary agreement and takes effect from the following month. Moving down works the same way, though we usually suggest first understanding why the chosen level turned out to be more than you needed.
Once a month you receive a report: how many requests there were, at which priorities, where the targets were met, where they were not and why. The report is generated from the tracking system rather than written by hand.
Tell us what is critical for you and what an hour of downtime costs. We will propose a level where you do not overpay for speed you do not need.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.