Features · Service desk
A service desk, not an afterthought
Request types, a branded customer portal, queues, SLAs, approvals and an email channel — Jira Service Management territory, self-hosted.
The customer portal and help centre need Professional. Compare editions
Your service desk lives beside your tickets, not in a separate product. Start a project from the service-desk template and customers get a portal to raise and follow requests, agents get queues with SLA timers, and the whole thing runs on the same workflow engine, query language and automation as the rest of Iskue. Email and Slack feed the same queues, and Teams gets notifications.
What you get
- Request types and smart forms — customers pick what they need; forms with sections, conditional questions, attachments and answers that land in validated custom fields — translatable into the customer's language.
- A portal customers like — per-project branding and announcements, a help centre grouping your portals by topic, open or restricted access with approved domains, participants and organization sharing, and an embeddable widget for your own site.
- Queues built for agents — columns and sorting per queue, SLA timers as columns, starred queues, bulk actions, merge, similar requests, canned responses and out-of-office delegation.
- SLAs that pause — start, pause and stop conditions, goals chosen by TQL, several business-hour calendars, timers on the ticket, in queues and on the portal, and breached() / running() / remaining() in TQL.
- Approvals in the workflow — attach an approval step to a status: users, groups or customers approve — all, any, a quorum or a percentage — in the app, on the portal or by email, and the ticket moves on by itself.
- A real email channel — up to 10 intake addresses per project, attachments and CC participants, allow and block lists, and loop and auto-reply protection with a 30-day email log.
- Knowledge base and CSAT — publish chosen articles to the portal with suggestions while customers type and a deflection report; customers rate resolved requests 1–5 from a single-use link.
Service desk in action
SLA timers, live on the ticket
How SLA timers run
An SLA is a named metric with start, pause and stop conditions. Its goals are an ordered list of TQL queries with a target and a calendar each, so priority-1 incidents and access requests can have different targets under one metric. Paused time does not count, a reopened ticket resumes its clock rather than restarting it, and a sweep every five minutes notifies each breach exactly once — safely across cluster nodes. A threshold trigger lets automation act before the breach.
Customers, not accounts
Customers never need an Iskue account. They reach the portal through capability links, by email or from a chat channel, and see only their own requests, the ones they participate in, and those shared with their organization — never internal notes, and never a restricted ticket through sharing. Agents decide who can post public replies: without that permission, a collaborator writes internal notes only.
Email that doesn't loop
Inbound mail is screened before it becomes a ticket: auto-replies, bulk mail, bounces, mail from the desk's own addresses and senders over the hourly cap are dropped and logged. Outbound mail is marked auto-generated and replies thread back to the right ticket by plus-addressing. On a restricted portal, an unknown sender lands in the access-request queue instead of opening a ticket.
Query your SLAs
project = SUP AND breached("Time to resolution")
requestType = "Get IT help" AND running("Time to first response")
ORDER BY remaining("Time to first response") ASCSee Iskue on your own screen
A demo takes half an hour. A pilot runs on your servers, with your data, from day one.