Selection
Choosing a ticket system as an IT service provider: what to look for
For IT service providers the ticket system is the backbone of daily business. The choice decides whether requests run cleanly, whether effort is billed correctly and whether the numbers at month end hold up. These criteria help with the decision.
1. Email and portal intake
Most requests arrive by email. A good system turns incoming mail into tickets automatically, matches them to the right customer through the sender domain and threads replies onto the existing ticket instead of creating duplicates. A customer portal - ideally without password management - takes further load off.
2. SLA control
Response and resolution times should be definable per priority and take business hours and public holidays into account. Hierarchical assignment matters: a customer-specific SLA overrides the default, so premium customers get the times they were promised.
3. The link to contract and budget
Decisive for a service provider: can recorded time be booked straight onto a maintenance contract with budget and hourly rate? Only then does month-end billing arise by itself - without assembling it afterwards.
4. Inventory and monitoring integration
The device involved should attach itself to the ticket from the inventory (through OCS Inventory or OPSI, for instance). A monitoring integration turns an alert into a ticket with one click - shorter response times included.
5. GDPR, hosting and pricing model
Because customer data is processed, the hosting location and GDPR compliance are central criteria for the processing agreement. On price, look at the model: one price with every function is more predictable than per-technician or per-device tiers with paid add-ons.
Frequently asked questions
What is the most important criterion for an IT service provider?
The unbroken path from the email through the ticket and the SLA deadline to contract-linked time tracking and billing. If that chain breaks, work is duplicated and billable hours are lost.
Should the ticket system bring its own RMM?
Not necessarily. Many service providers use specialised RMM and monitoring tools and connect them. What matters more is that the ticket system integrates those tools - turning monitoring alerts into tickets, for example.
Why does the hosting location matter?
When customer data is processed, hosting in Germany makes GDPR-compliant processing easier and avoids the complexity of third-country transfers.
What to watch for in the pricing model?
Transparency and scaling: a fixed price per user including all functions is more predictable than models with add-on surcharges that grow as your needs do.
Related in IDA
Try IDA free for 30 days
No payment details, ready in minutes - hosted in Germany.