Every helpdesk promises fast response times. The hard part isn't writing that promise down — it's enforcing it automatically, per tenant, without hardcoding a single organisation's rules into the application.

When we built the Ticket Management System (TMS) module on One Platform, the brief was simple to state and difficult to deliver: every tenant needed its own SLA tiers, its own escalation path, and its own notion of "urgent" — all running on the same shared codebase as seven other modules. You can see the module itself in our Multi-Tenant Helpdesk Platform case study.

The Problem With Hardcoded SLAs

The obvious first approach is to define fixed tiers — Urgent, High, Normal — with fixed response windows, and ship it. That works for exactly one tenant. The second tenant that signs up wants a four-tier system. The third wants escalation to skip a level for a specific department. Hardcoding any of that means a fork, and forks are how "one platform" quietly becomes six platforms nobody wants to maintain.

What We Made Configurable Per Tenant

  • Auto-assignment strategy — Round Robin, Load Balanced, or Skill-Based, set per department
  • SLA tiers and breach thresholds, monitored continuously and escalated automatically
  • Tenant branding applied across the portal and every notification email

Where the Logic Actually Lives

The pattern that made this manageable was keeping SLA rules as tenant-scoped configuration, not application logic. A dedicated monitoring service walks open tickets against each tenant's configured thresholds, and when a breach is imminent, the notification layer — already wired for SMTP and generic REST providers — fires the escalation. The ticketing service itself never needs to know whose rules it's enforcing.

"The moment SLA rules stopped being 'if' statements and became rows in a settings table, onboarding a new tenant stopped being an engineering task."

— Platform Engineering, cloudsoftera

Escalation, Not Just Alerts

Breaches route to a manager automatically, not just to a log line someone might notice later.

Same Auth Layer, No Exceptions

Every SLA rule still respects the role and tenant boundaries enforced upstream by auth-service.

What This Means for New Tenants

A new client onboarding onto TMS today doesn't wait on a development sprint to get their SLA structure right. Their rules, their branding, and their routing strategy are set through configuration screens — the same codebase serving every other tenant on the platform, unchanged.