The service desk and the asset register, in one system

Described in terms of what happens on a Tuesday afternoon rather than what it sounds like in a comparison grid.

The organising idea is simple: the ticket, the device, the person and the lifecycle case are the same record. That is why the register stays accurate — it updates as a by-product of the work, instead of being a separate chore that competes with it.

The hardware estate

The part no service desk product does properly.

A lifecycle, not a list

Sixteen states from draft through procured, in stock, assigned, under repair, returned and retired to disposed, with rules about what may follow what. An illegal move is refused and tells you which moves are legal, so the register cannot drift into a state nobody can explain.

Serial unique across every status, so a returned-and-reissued machine cannot appear twice
Owned, rented and leased tracked separately, with monthly rent and system value
Purchase, warranty and AMC dates that produce reminders instead of surprises
Bulk assign, move and re-locate with a preview of exactly what will change

Handover and return documents that generate themselves

Assign a device and the handover PDF is produced with your logo, the employee's details, the configuration, the condition and signature blocks. The same on return. No more typing a Word template for each machine.

Damage, repair and recovery

A damage case runs from inspection through quote and approval to recovery or waiver, with receipts attached, the vendor linked, and finance notified when recovery is approved. Exit-time assessment feeds straight into the offboarding case.

Dispatch your employee can follow

Courier, AWB and tracking events, with the employee watching progress from the help centre and confirming receipt with a photo at the end — which resolves the linked ticket automatically.

Bulk import dispatches from CSV with a dry run and AWB de-duplication
Optional hourly sync from a Google Sheet your logistics team already keeps

People, joining and leaving

Employee 360

One page per person: devices held, every ticket raised, licences assigned, dispatches, lifecycle cases and the complete history of everything they have ever been given. It is the screen you will open in an audit, and the one that makes an exit conversation short.

Onboarding that verifies itself

A joiner checklist with manual ticks and, beside them, a "verified by the system" card computed from live data — does the employee record exist, is the manager's email there, has a mailbox appeared, is an asset allocated, are licences assigned. The candidate can ask the chat assistant whether their system is ready and get the same answer from the same data.

Offboarding that actually closes

Tasks by team, a last working day that can be revised with history, and a hard rule: the case cannot be completed until the assets are back. The override exists, needs a permission and a typed reason, and appears in a report.

Tokenised exit page for the employee: interview, address, book the return
Manager acknowledgement by link, no login required
Optional auto-suspend of the directory account on the last working day

Handling requests

Tickets with a real lifecycle

Twelve statuses with a state machine, internal notes kept separate from replies, merge, link, watchers, a full timeline and a satisfaction rating after resolution — and a device panel that links the ticket to the actual machine in the register.

One queue, four channels

Email over IMAP with correct Message-ID threading and loop detection, the public help centre, live chat and the API all produce the same ticket, with the channel recorded.

SLAs with real business hours

Targets per priority, working hours per weekday, Indian public holidays pre-loaded, clocks that pause while you wait on the requester, and a panel that explains exactly why a deadline is what it is.

The five ITIL registers

Incidents, problems, changes, service requests and security incidents, with change approvals, a known-error database, and a scheduling conflict check that also looks at which machines are already away for repair.

Money and vendors

Vendors, contracts and performance

Ten vendor types with GSTIN and PAN validation, contract status and expiry, documents, and a performance page showing repair turnaround, damage cost and rent exposure per vendor — the numbers you want before a renewal conversation.

Subscriptions and licence allocation

Who holds which licence, what it costs, when it renews, and which seats nobody has used. Licences can be filled automatically from Microsoft 365 — after a dry run that reports counts before it writes anything.

Invoices, read for you

Upload a supplier invoice and it is recorded immediately from pattern matching; a background worker fills the blanks, splits a merged PDF into its parts, links or creates the vendor, and waits for a person to confirm. It never overwrites a money field it already found.

Seeing the estate, and fitting in

Around ninety reports

Helpdesk, HR, asset and workforce, finance, vendor, subscription, chat and endpoint reports — allocation matrix, asset ageing, rent forecast, warranty and AMC risk, damage and recovery, department-wise summary, owned versus rented mix, and employee asset history.

Pin to your dashboard, export to CSV, Excel, Word or PDF
Schedule one to arrive by email daily, weekly or monthly
Build your own from allow-listed datasets — user input never reaches SQL

Integrations that stay yours

Google Workspace, Microsoft 365, CrowdStrike Falcon and Google Sheets connect with your own credentials, read-mostly, off by default, and each does a dry run reporting counts before it writes a row into your business tables.

Reconcile the register against what your endpoint agent can actually see
Find licences still assigned to people who have left
Security alerts become incidents joined to the device, the person and their manager

API, import and export

A documented REST API with OAuth2, idempotent writes and signed webhooks; an import wizard that takes your existing spreadsheet with column mapping, a row-by-row error preview and a rollback; and a full export of everything, at any time, at no charge.

Usable on a phone, in a stockroom

Installable as an app, with tables that become card lists, 44-pixel targets and forms that do not zoom. Issuing and returning a device is meant to be done one-handed while standing at a desk, because that is where it actually happens.

Questions about how it works

Can we import our existing asset spreadsheet?

That is the expected way to start. CSV or Excel, map your columns to ours, see the errors row by row before anything is written, and roll the whole batch back if it is not what you wanted.

Do we have to use the integrations?

No. They are optional, off by default, and most useful once your register is populated. The product is complete without any of them.

Can we run IT and HR desks together?

Yes — two queues with separate branding and permissions, one login and one bill.