The IT department
you never hired
Infotechbang watches every device, licence and IT request a small business runs on, sorts the noise, and suggests the fix. One agent. One board. Nothing touches a machine until someone with admin rights says so.
#Everything above came out of one agent and one dashboard.
##What it is, in the shortest honest form
- Name
- infotechbang - keeps every device, licence and IT request a business runs on in one place.
- Synopsis
- Install one agent per device. Point your IT inbox at it. Read one board.
- Description
What it watches. The agent reports the state of each machine on a 15-minute cycle: model and serial, disk and battery health, installed software and versions, patch level, licence keys the vendor exposes, assigned user and last check-in. That inventory is what makes everything else possible - a ticket about a slow laptop arrives already knowing the laptop is four years old with a failing drive.
What it sorts. Requests land by email, WhatsApp or the web form. Each is classified by type and priority, matched against tickets that looked like it before, and tied to the device or user involved. Where a past resolution fits, it is offered as a suggested fix with the ticket it came from. The queue arrives ordered, not just collected.
What it will not do. It will not change anything on a device on its own. Suggestions sit and wait. An admin approves a named action on a named machine, and only then does it run, with before-and-after state recorded. There is no screen recording, no keystroke logging and no access to personal files - not as a setting, but as a design decision.
- Exit status
0when every device has checked in, no critical patch is pending and no ticket has breached its response window. Anything else is listed, with the reason.
##Suggestions, with their reasons attached
A ticket is not handed to a model and hoped over. It is classified, matched against your own resolution history, tied to the asset it concerns, and then paused.
Seven seconds of work, written down. The suggestion names the ticket it learned from, so you can check whether the precedent was any good before you accept it.
Approval gate
Nothing runs on a device until someone with admin rights approves it. The approval, the approver and the device state on either side are all kept.
##Five jobs nobody at a 40-person company owns
Tickets, kit, licences, patches and people joining or leaving. Usually spread across an inbox, a spreadsheet and whoever is best with computers. Here they share one record.
Helpdesk that sorts itself
Requests arrive by email, WhatsApp or the web form. Each one is classified, prioritised, matched against past tickets and given a suggested fix drawn from what actually worked last time.
4 of 5 tickets sorted without a humanEvery device, on one page
Serial, model, disk health, installed software, warranty end date, assigned user and location. Collected by the agent, not by a spreadsheet someone forgot to update in March.
Refreshed every 15 minutesLicences counted against installs
Seats purchased on one side, real installs on the other. Renewals flagged 30 days out, unused seats flagged before you pay for them again.
Both over-use and wastePatching you can hold back
A full patch inventory with criticals surfaced first. Nothing installs until someone approves the ring, and every rollout records what it replaced.
Approval-based rolloutJoiners and leavers, in order
A leaver checklist that lists every account, licence and device to reclaim, with each step confirmed by an admin and timestamped for the audit trail.
Nothing left behindMany clients, one board
For teams who look after other companies: every client org side by side, with contract hours used, open tickets and the devices that need attention today.
White-label client reports##Three commands and a forwarding rule
No appliance to rack, no agent certificate to mint, no directory migration. If you can run an installer and edit a mail rule, you are done before lunch.
Install the agent on one device
Pick a platform, run it once, and the machine appears on the board. Roll the rest out by group policy, MDM or a shared link.
winget install Infotechbang.Agent --accept-package-agreements
infotechbang-agent enrol --workspace acme-traders --key ITB-XXXX-XXXX
# agent 4.2.1 enrolled desk-04
# mode read-only
# first report in 12sSend your IT requests somewhere useful
Forward the inbox people already write to. WhatsApp intake is a QR scan from the dashboard, and the web form needs nothing at all.
forward it-help@acme-traders.com -> acme-traders@in.infotechbang.com
# intake live email, whatsapp, web form
# first ticket #2240 classified in 1.4s
# threads kept replies stay on the same ticketDecide who can approve what
Everyone else can raise and read. Approval rights are the only setting that actually matters on day one.
invite ravi.k@acme-traders.com role=admin approvals: yes invite ops@acme-traders.com role=operator approvals: patches only invite everyone@acme-traders.com role=requester # 3 roles set admin, operator, requester # approval queue routed to ravi.k
##If IT is what you sell, not what you need
One board across every client you look after, with the contract hours you have already burned sitting next to the tickets that burned them.
| Client org | Devices | Open tickets | Contract hours | Needs attention |
|---|---|---|---|---|
| northgate-legal | 64 | 3 | 61/72h | steady |
| acme-traders | 50 | 5 | 38/40h | queue building |
| bluefin-logistics | 128 | 11 | 131/120h | over contract |
| srinivas-clinics | 22 | 1 | 9/24h | steady |
Switch client without switching login
One account, scoped per client org. Data never crosses between them, and a technician only sees the orgs they are assigned.
Reports that go out with your name on them
Monthly device, licence and ticket summaries, white-labelled, generated from the same records your technicians worked from.
Hours that argue for themselves
Time attaches to tickets and approvals as they happen, so a renewal conversation starts from a log rather than a recollection.
##Latest three entries
##The questions we get asked before the demo
QDoes the agent record screens or keystrokes?
No. The agent reads device and software state: hardware identifiers, installed packages and versions, patch level, disk and battery health, licence keys where the vendor exposes them, and whether the machine checked in.
There is no screen capture, no keystroke capture, no clipboard access, no browser history and no reading of personal files. These are not switched off by default - they are not built.
QWhat can the agent change on a device?
Nothing, until an admin approves a specific action on a specific device. The default install is read-only.
Once approved, the action runs with its scope written down in advance: restart a service, clear a print queue, install an approved patch, revoke a session. Every run is logged with who approved it and what the device looked like before and after.
QCan we self-host it?
The agent and the dashboard run from our infrastructure on all three plans. A self-managed deployment is available for teams with a regulatory reason to keep the database inside their own network, priced per client org and handled through a contract rather than a signup form.
Contact us with your constraint and we will tell you honestly whether it is a fit.
QWhat happens to our data if we cancel?
You can export everything at any time, not just on the way out: devices, tickets with full history, licences, patch records and the approval log, as CSV and JSON.
After cancellation the workspace stays readable for 30 days so you can pull what you need. It is then deleted, backups included, within a further 30 days.
QWe already have a ticketing tool. Is this a replacement?
Often it is, because the value is in tickets and assets sitting in the same place - a printer complaint that already knows which printer, on which floor, under which warranty.
If you are keeping an existing tool for contractual reasons, the inventory, licence and patch sides stand on their own and will not fight with it.
QHow long until it is actually useful?
Two devices reporting in is enough to see a real status board, which is usually ten minutes. Licence and patch pictures firm up once most of the fleet has checked in, typically the same afternoon.
Ticket suggestions get sharper as resolutions accumulate. The first fortnight is mostly the system learning your estate; after that it is suggesting fixes from your own history.
$infotechbang init --trial 14d --card none