QoreDesk is an enterprise service management platform where the service catalog, the approvals, the assignment rules and the SLAs are all things you configure — not things you commission. Build a process on a canvas, simulate it before you publish, and have it live the same afternoon.
IT · HR · Facilities · Finance — one catalog, one fulfilment engine
Request submitted
Cost over $1,500
Department manager
Provision hardware
THE PROBLEM
Enterprise service management platforms are not short of capability. What they are short of is a path from "we bought it" to "we use it" that doesn't run through a discovery phase, a statement of work and a certified implementation partner.
So the licence starts in January and the first workflow goes live in September. By then the team that asked for it has gone back to a shared mailbox and a spreadsheet. QoreDesk is built around the opposite assumption: that the people who own a process should be able to change it themselves, on a Tuesday, without a release.
PLATFORM
Eleven step types — approval, assignment, notification, condition, wait, webhook, update field, comment, custom task, create sub-ticket and closure — composed on a visual canvas. Definitions are versioned, so publishing a change never loses the version that worked.
Run a request through the workflow you just drew and watch which path it takes — without creating a record, notifying anyone, or touching live data. Find the gap now instead of on Monday.
Publish services with forms built from sixteen field types, including reference pickers into other records and multi-row grids. Reusable variable sets keep the fragments you repeat in one place.
Approval policies evaluate as a stage of the ticket lifecycle, with the rule that a requester can never approve their own request. Assignment rules route work to the right group and agent automatically.
Define targets, watch the countdown on the record where the work is happening, and let a background worker evaluate breaches continuously — so escalation arrives before the breach, not in next month's report.
SAML and OIDC single sign-on, SCIM 2.0 user and group provisioning, granular role and permission policies, agent licensing, and an audit trail that records who changed what.
WHY IT MATTERS
When a process lives in records rather than customisations, adjusting it is an afternoon rather than a release cycle. Teams start improving processes again instead of working around them.
IT, HR, Facilities and Finance publish through the same catalog and the same fulfilment engine, each with their own forms, approvals and service levels. You stop buying a tool per department.
When the portal speaks the employee's language, requests come through the front door instead of arriving as a direct message. What the service desk actually handles becomes measurable.
THE PRODUCT
Drag a step from the palette, draw the connection, configure it in the panel. This is the whole build experience.
Services, not record types. The word "ticket" does not appear anywhere an employee can see.
Every ticket, with the SLA countdown, priority, assignment group and status in one view.
Each catalog item carries its own form, approval policy, assignment group and SLA target.
USE CASES
One request from the hiring manager. Four departments doing the work.
The request everyone raises, with the approval nobody should skip.
Route on value, not on hope.
The classic service desk, without pretending everything is an incident.
HOW IT'S BUILT
Nothing below requires a developer, a script, or a deployment.
Choose what starts the process. Here: any submission of the "Laptop request" catalog item.
Split the path on a field from the request. Here: whether the cost is over $1,500.
The expensive branch goes to the department manager. The cheap one goes straight to fulfilment.
Run a test request through it and watch the path light up. Then publish it as version 2 — version 1 stays available.
HONESTLY
ServiceNow and BMC are broader and more mature than QoreDesk, with two decades of ecosystem behind them. If you need IT operations management, discovery and dependency-mapped CMDB, or a marketplace of certified partners, those platforms are built for that and we are not. What follows is about shape, not scale.
| What you're deciding | QoreDesk | Platforms like ServiceNow and BMC |
|---|---|---|
| Breadth of the platform | Service management: catalog, workflow, approvals, SLAs, tasks, knowledge, portal | Substantially broader, including ITOM, discovery and CMDB |
| Who builds a workflow | An administrator, on a visual canvas | Typically a specialist or certified partner, depending on complexity |
| Testing a process change | Simulation mode, before publishing | Usually a sub-production instance |
| Extending behaviour | Eleven composable step types and outbound webhooks | Scripting and a platform-specific development model |
| Ecosystem and partners | Small and new | Large, mature, and a genuine advantage |
| Best fit | Organisations that want service delivery running in weeks | Enterprises with the scope and budget for a platform programme |
If your requirements genuinely include the left-hand column of things we don't do, buy the other thing. We would rather you did.
PRICING
Everyone who raises a request, tracks it, or approves it uses QoreDesk at no cost. You pay for the people doing the fulfilment work.
$19 / agent / month
For a single team getting off email.
$45 / agent / month
For service delivery across several departments.
Talk to us
For organisations with identity and governance requirements.
Annual billing available. No implementation fee, and no certified partner required to get started.
QoreDesk has a guided setup that walks you through sample data, your team, the service catalog, SLA policies, workflows and portal branding. The product's own target is a working service desk in under an hour. A considered rollout across several departments is a longer conversation, but it is measured in weeks rather than quarters.
Not to build processes. Catalog items, forms, approval policies, assignment rules, SLA definitions, notification rules and workflows are all configured through the interface. You'd want a developer only to integrate an external system, which is what the webhook step is for.
That's the point of the platform. IT, HR, Facilities and Finance publish through the same catalog and fulfilment engine, each with their own forms, approvals and service levels. A single request can fan out into child requests across several departments, with the parent tracking progress.
Workflow definitions are versioned. Publishing a change creates a new version and the previous one remains. You can also run a change through simulation before publishing it at all.
QoreDesk supports SAML and OIDC for authentication and SCIM 2.0 for user and group provisioning, so accounts and group membership can be managed from your identity provider.
QoreDesk is multi-tenant by design. Every record carries a tenant, and tenant context is established on every request rather than being left to individual queries.
Not today. If a dependency-mapped CMDB is a hard requirement, a broader platform is the better choice, and we'd say so on a call.
There is an optional assistant in the employee portal that can answer questions and look things up across portal data. It is off unless you configure a provider, and we would rather sell you the workflow engine than the chatbot.
Start free and build a workflow in an afternoon, or send us the process you dread and we'll show you what it looks like in QoreDesk.