octoja and TANSS
Native TANSS integration — alerts become tickets and close themselves again.
What TANSS is
TANSS is one of the most widely used ticket systems in German IT service providers, and it grew out of that practice. octoja brings its own interface for it — no middleware needed.
What the integration brings
- Set up the connection and check availability at any time
- Import the customer base from the target system
- Map octoja customers onto the structure in the target system
- Alerts create tickets, all-clears close them again
- Delivery log per message, including resending
What changes with TANSS
The interface is not the gain — what no longer happens by hand afterwards is.
Take over the customer base
The customer base can be imported from TANSS instead of maintaining it a second time. Existing customers you map to each other.
The alert becomes a ticket
A check that trips creates a ticket carrying the device, the customer and the check history. When it recovers, the ticket closes by itself.
No flood of messages
The per-channel alert latch keeps 40 check runs from producing 40 tickets. Escalation follows the hit rate, not every blip.
Traceable delivery
A delivery log shows per message whether it arrived — and lets you resend it if it did not.
Connected in three steps
We walk through the exact sequence together during trial access.
Define the alert channel
You decide which checks create a ticket at all — by severity and hit rate, not on every blip.
Set service hours
Set weekdays and times per channel. Into the ticket system during the day, by phone to the on-call engineer at night.
Verify the mapping
Map customers and sites from octoja onto the structure in the target system so the ticket lands with the right tenant.
Other systems in the German market
See the TANSS integration against your own estate
During trial access we set up the alert channel together and you check on real devices whether the ticket arrives the way your dispatch needs it.