Book an IT reviewOngoing IT support under subscription
Business systems
Data and AI
Our apps
A ticket queue instead of phone calls in the corridor, a shared customer service mailbox with conversation history, a register of laptops and licences. We also show honestly when an open source application is the better fit, and when our Nexa Hub system is.
Requests for help arrive by phone, e-mail, chat and in the corridor. Some are handled on the spot, some get lost, and after a month nobody knows how many there were and how much time they took. The same applies to customer service run from a shared mailbox, where several people answer the same e-mails.
The asset register has a similar problem. A laptop issued to an employee is entered in a spreadsheet nobody updates, and the company learns that the warranty has ended on the day of the failure.
A ticketing system and an asset register are not technically complicated. What takes work is agreeing request categories, response times and responsibilities, plus the first inventory. That is where we start.
Office staff with a company mailbox, external customers or shop-floor workers without an e-mail account. Each of these groups needs a different request channel.
A single IT department is a different configuration from IT, maintenance, HR and administration in one system, each with its own forms and deadlines.
Some systems combine tickets with an asset register, others do one thing. Combining them helps when requests concern specific devices.
Domain sign-in is often a paid module. We show the cost of modules in the quote.
A remote support tool gives wide access to computers. We deploy it with a second sign-in factor and restricted network access.
Every description of features, licences and limits comes from the vendor's materials, read on 2 October 2026. For each application we add our assessment of when it fits. We make the final choice after talking about your case.
A good starting point for most companies
A web-based helpdesk and customer support system.
Our assessment: A good choice for external customer support. We do not develop Zammad; we deploy and maintain the vendor's version.
We deploy it when it fits the case
Management of IT assets and tickets in a service desk model.
Our assessment: Extensive and needs careful configuration. It suits an IT department that wants an asset register and tickets in one system.
A good starting point for most companies
A helpdesk and shared mailbox on your own server.
Our assessment: The simplest route from an office@ mailbox to a queue with assignment and conversation history.
A good starting point for most companies
A register of IT equipment and licences.
Our assessment: It brings order to issuing and returning equipment. Most of the work is the first inventory, not the installation itself.
We deploy it when it fits the case
Remote management of computers and remote desktop through a browser.
Our assessment: It gives wide access to computers, so we deploy it with a second sign-in factor and restricted network access.
Nexa Hub is our own ticketing system for multiple departments, built with warehouses and manufacturing plants in mind: requests from QR codes on machines, a kiosk with an employee number for people without a company mailbox, and deadlines counted in shift hours. It is a commercial product, with the licence and implementation priced individually.
When you need a helpdesk for external customer support or a simple queue for an office IT department, an open source application from the table below will usually be the better fit. When requests concern machines, shop floors and several support departments, compare it with Nexa Hub. We will tell you what fits better, even if it is not our product.
For a small customer service team, a vendor's subscription helpdesk is often the simplest choice: no server, backups or updates on your side. If ticket data can be held by an outside provider, we compare both options using your numbers.
If you use our ongoing IT support, requests to NexaIT go through our own system, with an agent on each workstation. Your own helpdesk is then useful for internal matters and for supporting your customers.
Request types, priorities, response times and responsible people. Written down before installation.
Mailbox, form, staff portal. We connect the ones the team actually uses.
A list of devices, assignment to people, purchase and warranty dates. The most labour-intensive step, so it is planned separately.
A separate environment, HTTPS, accounts and notifications for the team handling requests.
An off-server backup with a restore test, and after a month a review of categories and times based on real requests.
The server, domain and vendor licences are in your company's name. We record response time and fix time separately in the contract, and state the restore time after a test. Service terms
Yes. An asset register without a helpdesk already brings order to issuing equipment and licences, and a ticketing system can be added later.
In most of the systems in the table, yes, through a portal or replies in an e-mail thread. We agree what the customer sees and what is an internal note.
Nexa Hub is our commercial product for multiple departments, with QR codes, a shop-floor kiosk and deadlines counted in shift hours. The open source applications in the table are a better choice for external customer support and simple office queues.
A remote access tool is as secure as its configuration. We deploy it with a second sign-in factor, restricted network access and a connection log.
Other needs
Free · 60 minutes online · no obligation
office@nexait.plMessage us on WhatsApp
We don't use a contact form, but we answer the phone and reply to emails and WhatsApp messages during working hours.