The three tiers compared

Base the choice on what an hour of downtime costs, not on headcount. If sixty minutes without e-conomic or your web shop costs more than the monthly fee, Basis will not be enough.

Pricing and plans

Basis

reply within 4 hours

Weekdays 8-17, up to 10 users, from DKK 3,900/month. For smaller offices where waiting half a day is tolerable.

Ask about Basis
Most popular

Standard

reply within 1 hour

Weekdays 8-17 with servers and Microsoft 365 included, DKK 8,900/month. Add 24/7 support if nights and weekends matter too.

Get a price

Premium

reply within 15 minutes

A round-the-clock on-call line, named engineers who know your setup, a dedicated contact and a monthly SLA report. From DKK 18,500/month.

Talk to us

How we set priority

Priority depends on how many people are affected and what it means for the business. The job title of whoever reports it makes no difference.

Reply: 15 min, 1 hour or 4 hours Critical The whole company is stuck: email, finance or the web shop is down
Jumps ahead of all but critical High A department or a key system has stopped working
Handled in order of arrival Normal One user has a problem but can carry on another way
Timing agreed with you Planned A new starter, changed permissions, a Teams question

The clock starts when the ticket is logged, not when a technician happens to be free. Response times apply within your service hours, weekdays 8-17. On Premium and with 24/7 support they apply around the clock, Christmas Eve included.

How a ticket travels

Whether you email office@apply.dk, use the portal or call the on-call line from your agreement, every ticket goes through the same four steps.

01

Logged

The ticket receives a number and a timestamp. All deadlines are measured from that moment.

02

Assessed

The duty technician checks how many people are affected and sets a priority by the rules above.

03

Fixed or escalated

Simple issues are solved straight away over remote access. The rest go to a specialist, and you can follow progress in the portal.

04

Closed and explained

We close a ticket only once you confirm things work. Recurring faults of one kind get their own root cause analysis.

Questions and answers

Response is met once a technician is working on the ticket and in contact with you. Resolution ends when you are back in business. That often hinges on third parties such as a broadband provider or a software vendor, and time spent waiting on them is excluded from the figures.

The technician makes a first call based on the rules, yet you have the final say. Tell us it is more serious than we judged and we raise the priority, no argument.

Yes. The change goes into a short addendum and takes effect from the next month. Moving down is possible as well, though we would first like to look at why the current tier feels too big.

Every month a report comes straight out of the ticketing system: ticket count, priority, and which were answered on time. It is generated automatically, so nobody has tidied up the numbers.

It shows that operations are controlled and how incidents are dealt with. If your organisation falls under NIS2, the reports can form part of the evidence you present to Styrelsen for Samfundssikkerhed or an auditor.

Pick a tier based on the cost of downtime

Tell us which systems must stay up and roughly what an hour without them costs. We will suggest a tier so you never pay for speed you will not use.

Coverage
All of Denmark, delivered remotely

This site uses only essential cookies: they keep pages working and store your chosen town. Read more in our privacy policy.