Area 02 · Operations and infrastructure

Support plans and SLA

Beneath the legal language, any service level agreement settles two matters: the delay before an engineer takes on your issue, and the moment your staff can carry on working. Below you will find the differences between our three plans, the point at which timing begins and a way to verify our numbers independently.

15 min
our fastest response
3
plans on offer
8:00-18:00
Mon-Fri CET on every plan
24/7
on-call line included in Premium

Start, Business and Premium at a glance

Let the price of lost working time guide you, not the size of your payroll. Should a single outage of your shop or accounting package outweigh a monthly subscription, Start leaves you exposed.

Pricing and plans

Start

4-hour response

Weekdays 8:00-18:00 CET, a ceiling of 10 users, from PLN 1,900/month excl. VAT. Right for small teams where half a day of delay does not stop sales.

Ask about Start
Recommended

Business

1-hour response

Weekdays 8:00-18:00 CET, with servers plus Microsoft 365 covered, PLN 3,900/month excl. VAT. Nights and weekends can be added through 24/7 IT support.

Calculate

Premium

15-minute response

Duty line day and night, dedicated engineers familiar with your systems, a named account manager and SLA reporting each month. From PLN 7,500/month excl. VAT.

Let us talk

How priorities are set

Priority is driven by consequences: the number of staff hit and whether selling, manufacturing or serving customers has stopped. Whether the ticket comes from the CEO or an intern makes no difference.

Response: 15 min, 1 h or 4 h Critical Nobody can work: mail, accounting, KSeF invoicing or your online store has failed
Ahead of everything but critical High A whole team or an important application is unavailable, such as warehouse label printing
First come, first served Normal A single person is affected but has a way to keep working
Scheduled together Planned Onboarding a recruit, adjusting access rights, a how-to about Teams

Timing begins at the moment of registration, regardless of engineer availability. Response time is measured in working hours, Mon-Fri 8:00-18:00 CET. Premium clients, along with anyone using 24/7 IT support, have critical incidents measured continuously, even on Christmas Eve or New Year’s Day.

A ticket’s journey and how we time it

Email to office@apply.pl, a portal request or the duty line named in your contract: the route makes no difference, since each ticket moves through four identical stages with a timestamp recorded at every step.

01

Logging

A reference number and a registration time are assigned. Response timing runs from there.

02

Response

An engineer assesses the impact, sets the priority and contacts you with a plan. An automatic acknowledgement email does not count as a response.

03

Fix or workaround

Simple issues are resolved remotely on the spot. For harder ones we restore working capacity with a workaround first and schedule the permanent repair. Waiting on you or a third-party vendor pauses the clock.

04

Closure and root cause

Closure waits for your confirmation that the fix holds. Recurring faults trigger a dedicated investigation into why.

Questions and answers

Response time ends once an engineer is actively on the case and in touch with you, knows what has happened and tells you the next step. Resolution time ends when your staff can work again, even if only thanks to a workaround. Response time is written into the contract because it depends on us. For resolution we agree target times per priority, and any periods spent waiting on an internet provider or software vendor appear separately in the report.

Each month the ticketing system calculates what share of requests in every priority received a response on time. Only hours covered by your plan count, so a ticket raised at 17:30 on a Friday under Start is due a response by 11:30 on Monday. How the result is assessed is agreed in the contract.

Every miss shows up in the monthly report. You also receive a written explanation of the cause and a plan to stop it recurring. If you need further contract terms for that situation, we discuss them individually when the agreement is drawn up.

Our engineer suggests a level by applying the agreed criteria, yet the decision is yours. Tell us the consequences are worse and the priority goes up with no debate; the audit trail records who altered it and at what time.

Yes, through an annex, with the switch date agreed between us. For example, an online retailer might step up from Business to Premium before November and drop back once the Christmas rush is over. Moving down is equally possible when the reports show the faster response was never needed.

They show that IT is run in a controlled way and that incidents are handled by documented rules. Companies covered by the amended Polish National Cybersecurity System Act (KSC) may include them in documentation presented to auditors or the competent regulator.

Match the plan to your cost of downtime

Tell us which systems must never stop and roughly what an hour without them costs you. We will suggest a plan that does not charge you for speed you will never use.

Hours
Mon-Fri 8:00-18:00 CET, reply within one working day
Meetings
Online via Teams or Google Meet

We set strictly necessary cookies only: they keep the site running and remember the city you chose. Nothing here is used for advertising or tracking. More in our privacy policy.