Official User Manual & Getting Started Guide
Welcome to the ITSM Financial Command Center! The platform gives IT leadership a single, executive-level view of operations. Connect your ticketing system — Zendesk, Jira, ServiceNow, or a custom REST API — and see your ticket queues, Service Level Agreement (SLA) health, and exact financial revenue at risk in one place. Premium accounts connect one ticketing platform; the free trial and Enterprise can connect several at once and see them merged into a single view.
The ITSM Financial Command Center isn't just a tool for agents—it's a strategic asset for IT leadership. By centralizing operations, the platform delivers immediate, measurable impact on your bottom line and service quality:
When you first visit the site, you will be prompted to log in or register. To create a new account:
noreply@itsmdashboard.dev.The platform supports multiple ways to connect to your existing ticketing systems securely. Go to the dashboard and look for the "ITSM Connection Settings" configuration panel.
We use an Enterprise-Grade OAuth 2.0 flow to securely connect your Zendesk environment without you handling sensitive API tokens.
mycompany if your URL is mycompany.zendesk.com).refresh_token in the background, keeping your connection alive automatically even when tokens expire.You can also connect directly to Atlassian's Jira platform.
You can also connect to your ServiceNow instance securely.
dev12345), Username, and Password.If you use a proprietary or in-house ticketing system, you can use our dynamic Custom REST API engine to pull in your tickets.
endpointUrl, HTTP method, and necessary headers (e.g. Bearer tokens).mappings block to tell the engine exactly how to translate your API's JSON keys into our standardized fields (e.g., map your system's "subject" to our "title").Once connected, your dashboard will populate with customizable widgets. Built on a fluid CSS Flexbox engine, you have ultimate layout control:
Use the Dark | Light toggle in the header to switch the entire portal between a light professional theme (the default) and a dark theme. Your choice is remembered on your device and applies everywhere — both dashboards, settings, and the sign-in screens.
Our platform analyzes your current queue. At the top of your screen, you will see a dynamic "Executive Insights" banner that gives you a human-readable summary of your workload.
Click "Go to Strategic View" to enter the executive console. Here, operational metrics are translated into financial impact:
Revenue at Risk (Strategic Dashboard). Every ticket that is not yet Resolved or Closed is checked against your configured capabilities. A ticket counts towards a capability when its service field matches the capability name (case-insensitive, partial matches allowed). The service field is the component field in Zendesk, component names in Jira, and the Business Service / Configuration Item in ServiceNow. Each matching ticket contributes:
Impact (£) = Capability Base Value × Priority Multiplier
| Ticket Priority | Multiplier |
|---|---|
| Critical | 1.0 (full base value) |
| High | 0.5 |
| Medium | 0.05 |
| Low | 0.01 |
Each capability's Revenue at Risk is the sum of its ticket impacts, and the headline figure is the total across all capabilities. Example: a £100,000 capability with one open Critical and two open Medium tickets shows £100,000 × 1.0 + £100,000 × 0.05 × 2 = £110,000 at risk. Tickets whose service field doesn't match any configured capability are not counted.
Est. SLA Liability (Classic Dashboard). This applies your configured penalty model to the age of open tickets. A Critical ticket starts accruing after it has been open for 4 hours; a High ticket after 24 hours. Once over its threshold, a ticket costs:
Penalty (£) = Base Penalty + (full days open × Daily Penalty), capped at your Max Cap
The KPI is the sum across all open Critical and High tickets (Medium/Low never contribute). Example: a Critical ticket open for 50 hours with a £1,000 base, £500/day and £5,000 cap costs £1,000 + (2 × £500) = £2,000. Until SLA settings are configured, this card shows an "Action Required: Configure SLA" prompt instead of a value.
Resolution times (MTTR and the category charts). Every resolution time is measured in working hours — 08:00 to 18:00 UK time, Monday to Friday — over the last 90 days. A ticket raised at 17:00 on Friday and closed at 09:00 on Monday counts as 2 hours, not 64, because nobody worked the weekend. Public holidays are not excluded, since they differ by country. Days shown alongside these figures are working days of 10 hours, so “2.0d” means 20 working hours.
If a ticket’s timestamps are inconsistent — resolved before it was created, which happens with migrated tickets or clock differences between systems — it still counts towards ticket volumes, but is left out of the resolution-time averages, because its duration cannot be known. Enterprise breakdowns tell you how many were set aside.
At Risk of SLA Breach (Classic Dashboard). Separately from the penalty model, this counter uses your ITSM platform's own SLA deadlines: it counts open tickets whose SLA target expires within the next 4 hours. Tickets that have already breached, or that carry no SLA deadline from the platform, are not counted.
Weekly figures use calendar weeks, Monday to Sunday, UK time. The Resource Planning Forecaster and the Backlog Clearance Rate both bucket by the same weeks your ITSM platform reports on, so a figure here can be checked directly against a report from Zendesk, Jira or ServiceNow. Each week is labelled by its commencing date — “3 Aug” means Monday 3 August 00:00 to Sunday 9 August 23:59.
The current week is shown but excluded from every average and from the trend line, because it holds only the days that have happened so far — counting a Tuesday as a full week would make output look like it had collapsed. Charts also show two projected weeks, which carry a forecast only.
When a ticket counts as resolved. We use the date your platform records as the solve date. For Zendesk that is the solved timestamp from its own ticket metrics; if a ticket predates those metrics or your plan does not include them, we fall back to an estimate from the last-updated date, which can place a ticket a few days out. Reopened and re-solved tickets count on their most recent solve date.
On the Enterprise plan, nine KPI cards across both dashboards become interactive — they show a small "View breakdown →" hint and open a detailed drill-down explaining exactly how the figure was produced:
Two charts on the Strategic dashboard have their own "View breakdown →" and "View resource planning →" links:
Both the Executive Dashboard and the Strategic Dashboard have an "Export Report" button (top right). Clicking it opens a menu with two options:
.pptx presentation of the dashboard's KPIs and charts — ideal for board packs and stakeholder updates. The Executive deck summarises your SLA KPIs (health score, breaches, ticket age, and estimated £ liability); the Strategic deck summarises business-capability risk, XLA health, team productivity (MTTR/FCR), and the resource forecast.Your account starts with a 7-Day Free Trial that includes every feature except Single Sign-On — so you can evaluate the Enterprise capabilities, not just the basics, before deciding. After 7 days your dashboard locks to protect your data streams, and you will be prompted to choose a plan to continue.
support@itsmdashboard.dev.
If you already subscribe to Premium, the Enterprise card shows Upgrade to Enterprise rather than a checkout button. This changes your existing subscription instead of creating a second one, so you are never billed twice.
Cancel at any time from Settings → Manage Billing, which opens Stripe's secure billing portal. There you can also update your card, download invoices, or renew a subscription you previously set to cancel.
We believe you should have complete control over your data. All account management tools are located in the Settings menu (accessible from the top right corner).
To request a copy of your personal data (profile, settings, and connection details) under your GDPR right to access and portability, email us at privacy@itsmdashboard.dev. We will provide it within 30 days.
If you no longer wish to use the service, you can permanently delete your account by clicking the red "Delete Account" button in Settings. If your access has lapsed and you cannot reach Settings, the same option is available as "Delete my account and data" on the screen you land on — you never need to contact us to remove your own data.
If you have an active subscription, deleting your account cancels it immediately — you will not be billed again and you do not need to cancel separately in Stripe. Because cancellation is immediate, any days you have already paid for in the current month are not refunded. If your intention is only to stop paying, use Settings → Manage Billing instead: that keeps your access and your data until the period ends.
One thing is deliberately kept: your invoices and payment records. UK tax and company law require us to retain sales records for several years, so those remain in Stripe even after your account is erased. Your profile, credentials, connections and dashboard configuration are all permanently deleted.
Every dashboard has a "Contact Us" link in the footer — clicking it opens an email to our support team. You can also write to us directly:
All service emails (welcome, password reset, trial reminders, deletion confirmations) are sent from noreply@itsmdashboard.dev — and if you reply to any of them, your reply reaches the support team automatically.
For system administrators, there is a hidden Admin Control Panel accessible by navigating directly to /admin in your browser.
Only users who have the is_admin: true flag in their Supabase authentication metadata are permitted to view this screen. Attempting to access it as a standard user will result in a 403 Forbidden error.