Service Desk

Hold the contract on every case.

Take every incident and request from intake to closure, hold the contracted clocks, and prove it afterward. For service desk managers, analysts from L1 to L3, and the customers they serve.

The Service Desk room: agents with headsets at their desks and a lead with a tablet at the queue board on the wall.

The SLA clock holds the contract.

Targets are set per contract, service line, severity and calendar. The clock runs only when the contract says it should, and every pause has a reason the customer can see.

  • Pause and resume, with the reason recorded
  • Business calendars with the Friday-Saturday weekend and Saudi holidays
  • Contract-lapse selection: the right terms on the day the work arrives
  • Each breach raised exactly once, even under load
  • An escalation ladder to people, tiers and Microsoft Support
  • An SLA editor that replays history before a change goes live
Illustrative screen with sample data.

A queue you can run at keyboard speed.

See what is waiting, what is about to breach and who is free. Assign, merge and bulk-update without leaving the list.

  • Saved personal and team views, grouped by customer, rule or asset
  • Keyboard-complete triage with a published shortcut contract
  • Open tabs and unsent drafts restored after a dropped connection
  • Workload shown per person, with clean hand-over at shift change
Illustrative screen with sample data.

From the first email to the last review

Entitlement-aware intake

Coverage is checked first: in the contract, in hours, in scope, with entitlement left. Out-of-scope work goes to a quote or an approval before anyone starts.

Every channel, one case

Portal, email and Teams, the app, and phone, SMS or WhatsApp through your own provider. The channel is recorded on the case.

A co-managed desk

The customer's own IT team takes cases, fixes what it can and hands the rest over. Both sides see who holds the next step and the clock.

Escalate to Microsoft Support

One click builds the pack from the case, the estate, health and change history, records consent and keeps the Microsoft case linked.

Knowledge in the flow

Articles on the case and from the resolution, suggested before a request is sent, and a list of searches that found nothing.

The major incident room

An automatic timeline, customer notices on a cadence, a Teams bridge and a drafted post-incident review a person approves.

A status page per customer

Fed by incidents, Microsoft Service Health and planned maintenance, branded as the operator.

Problems that stay solved

Repeat incidents become a problem, a known error, a fix and a line in the improvement register the customer sees.

A request catalog that fulfills itself

Group membership, licenses and MFA resets fulfilled through Entra ID and Graph after approval, each with an audit record.

Assets without agents

Devices from Intune, users from Entra ID, licenses from Graph and software from Defender, with idle licenses listed.

Service pulse

A short survey at closure, tied to the engineer and the service. A low score opens a follow-up.

Service credits, automatically

A breach mints the credit line in the contract's schedule. The customer sees it when it accrues.

Change, problem and release, under control.

A change calendar with freeze windows and conflicts, an approval queue that works from Outlook, and post-implementation reviews. Azure changes with no approved change record come to light, with the resource, its blast radius and its owner.

How changes reach the estate
Illustrative screen with sample data.

On-call, inside the desk.

The roster follows each contract's coverage window. A page reaches the right person with the right access, wakes a silenced phone, and the acknowledgement is recorded on the case.

The Astrolabium One app

Illustrative screen with sample data.

Know it's handled.

See Astrolabium One on your own estate. Tell us what you run and we will show you the screens that matter to you.