Back to Blog Home

IT requests in a small firm: five request types, one owner each, and a check for the ones nobody picked up

An open laptop showing a calendar and a task dashboard on a round wooden table

A small firm with no IT staff handles an IT request well when every request is one of five types, each type has one named owner and one named backup, spending and access to client data need an approval before any work starts, and one person checks every Monday for requests nobody has claimed. Slack's guide to a self-serve IT help desk copies each request into a triage channel where the IT team claims it, and a firm without an IT team has to name the person who does that claiming. Trio's IT service request form template says a request that costs money, grants access to sensitive data or changes a user's rights should be approved by a manager or system owner before IT starts.

Without those rules, a laptop request is approved by whoever answered the DM first, a request for the shared client folder is granted by the person who happened to be online, and a request that went quiet is found only when the person asking complains in the all-hands channel. With the rules below, nobody has to ask who handles what, spending and client data get a second pair of eyes, and the Monday check takes about fifteen minutes.

What is an IT request process when nobody works in IT?

It is a written answer to four questions for every kind of request: where it is sent, who does the work, who must approve first, and by when somebody must have picked it up. The guides that rank for this topic answer the first question well and the other three for a company that has an IT team.

Most guidance assumes the IT team exists. SherpaDesk's guide to an internal help desk recommends one support address, a portal and a ticket queue, and a named person who sorts new tickets each day so the queue does not become an unassigned pile everyone can see and nobody owns. Siit, an IT service desk vendor, recommends one official intake channel so that a quick DM becomes a tracked ticket instead of bypassing triage, and treating the process as something with an owner and a review cycle. Slack's help request template logs request type, category, priority and details in a tracker and notifies a channel. None of it says who does the sorting at a 25 person firm where the "IT person" is also the operations lead, the bookkeeper or the owner.

A small-company Hacker News thread describes an IT department of one person who works on company-wide projects and is also expected to handle printers and frozen computers, with replies pointing out that the two jobs conflict. That is one author's report from 2016, not a statistic. It shows what happens when one person is both the project worker and the help desk: requests wait for a gap in their day. A written process cannot add hours, but it can make sure a request is claimed, approved when it must be, and visible to the person who holds it.

The five request types, with an owner, a backup and an approval rule

Five types is enough for a firm of this size, because a person asking must be able to tell them apart in a few seconds. SherpaDesk suggests keeping forms to five to eight request types an employee can tell apart. Pick the five below, then rename them to the words your team already uses.

Request typeExamplesOwner (does the work)BackupApproval before work startsNo pickup by
HardwareNew laptop, monitor, headset, replacement chargerOperations leadOffice managerBudget holder, always, because it spends money4 working hours
Software and licensesNew seat, a paid tool, a plan upgradeOperations leadOwnerBudget holder, always, because it spends money4 working hours
Accounts and sign-inNew account, password or MFA reset, a departing person's accountsOutside IT provider or the operations leadOffice managerManager of the person for a new account; none for a reset after identity is confirmed2 working hours
Access to files and client dataShared folder, client workspace, a mailboxWhoever administers that systemOperations leadOwner of the client relationship or the data, always4 working hours
Something is brokenPrinter, Wi-Fi, a frozen laptop, a failed backupOutside IT provider or the operations leadOffice managerNone1 working hour

The roles are examples; put real names in the Owner, Backup and Approval columns, and keep one name per cell. The "No pickup by" column holds starting values, which are a recommendation to adjust after a month of real requests: they are deliberately short, because they measure when somebody claims the request, not when it is finished.

Two things are not on the list. New-hire and departure requests usually come from a manager or from HR rather than from the employee, and SherpaDesk notes that without their own form and approver they arrive by email and get missed. Handle them as an "Accounts and sign-in" request filed by the manager. The accounts and devices a new person needs before the first day are covered in the guide to day one IT access for a new hire.

Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.

Who should approve an IT request?

The approver is the person who carries the risk of the request, and that is rarely the person who does the work. Spending belongs to the budget holder. Access to client data belongs to whoever answers to the client for that data. A change to somebody's rights belongs to their manager or the system owner. The Trio template draws the same line for requests that cost money, grant access to sensitive data or change a user's rights, and requires the approval before IT starts.

Choose the owner of a request type by who can do the work, and choose its approver by what the request puts at risk, so that nobody approves a request they will also carry out. This is a recommendation, not a rule from any of the sources, and it matters most in the smallest firms. In a 15 person firm the operations lead often orders the laptop, creates the account and approves the spend, and then nothing stops a mistaken request or a social-engineering message from going through in one step. Splitting the two roles costs one extra tap and stops the most expensive mistakes.

Write down one backup approver for every request type, because an approval card is decided by whoever presses first and a request that waits for one busy person looks exactly like a request nobody saw. In the Kipwise agent, the approver gets a private card with Approve and Reject buttons, the first press decides, and anyone who presses later is told who decided. If the card is lost, the approver can ask for it again from the agent's App Home. A short approver list is fine, but a one-person list means a holiday stops every purchase. Name the second person before you need one.

A reasonable one-line rule you can paste into the channel description is this: "Spending needs the budget holder, access to client data needs the client owner, and a change to someone's rights needs their manager; everything else needs no approval."

How do you catch an IT request nobody picked up?

You set a no-pickup-by time for each type and you give one person the job of looking. A request in a firm without IT staff almost never fails because it was too hard. It fails because nobody claimed it, and nobody noticed that nobody claimed it.

Give every request type a no-pickup-by time that is much shorter than its completion time, because a request in a firm without IT staff fails at the claiming step long before it misses a deadline. Completion targets are what the ticketing guides focus on. Trio's workbook flags overdue requests and those awaiting approval, and Siit recommends a target completion time by request item, so that a password reset and a laptop purchase never share a clock. Those are good checks for the end of the process. They do not cover a request that has no owner yet, which has no one to be overdue.

The weekly check is the second half of the control, and it takes fifteen minutes on Monday morning. The named sorter, who is the owner of the process, goes through four things in the triage channel and the approval cards:

  1. Requests with no owner. Anything older than its no-pickup-by time gets an owner today.
  2. Requests waiting on an approval. If the approver has not answered, the backup approver is asked.
  3. Requests that were claimed but have had no update for a week. Ask the owner for one line.
  4. The week's numbers: how many requests arrived, how many were closed and how fast the first reply came.

SherpaDesk calls the failure an unassigned pile everyone can see and nobody owns. The Monday check turns that pile into a short list with a date next to each item.

How the request moves through Slack

A person asks in plain words, a person claims the request, and the approver is asked only when the type requires it. Here is a made-up example for a 22 person services firm; the names and the request are illustrative.

  1. Maya, an account manager, messages the Kipwise agent in a DM: "I need a new laptop for Tom, who starts on Monday."
  2. The agent asks a short plain question, "Send this request?", and Maya confirms. The agent files it, gives it a number, and keeps the request card with its state in Maya's own chat. In the channel, the team sees only a neutral "Request #42 was sent" line, never the title or the details.
  3. Because the request type is hardware, it needs an approval first. The budget holder gets a private card: "Maya Ortiz asked for your approval", with Approve and Reject. The first press decides, and Maya sees the result under her request card.
  4. The request lands in the triage channel. The operations lead claims it, orders the laptop and updates the request. A person does the work and marks the request done.
  5. If nobody claims it, or it is about to miss its deadline, the team sees one line in that request's thread in the triage channel, naming who asked and who holds it.
  6. When the operations lead marks it done, Maya gets a 1 to 5 rating card in her own chat.

The same desk takes a request from the "New request" shortcut, from the "Create request" message shortcut, and from the :ticket: emoji on a message, so a request that was first made in a channel does not have to be retyped. A confidential request never appears in a channel; its alerts are private messages.

The owner can ask the agent "how many requests this week, and how are we doing on deadlines?" and receives the numbers privately, which gives you the fourth item of the Monday check without building a spreadsheet. Every Kipwise Agent install puts the team on the Premium plan, and the request desk is part of it, so there is no separate tool to buy. A Kipwise admin switches the request desk on for the workspace.

What goes wrong, and what stays with a person

Four things tend to go wrong, and each has a plain fix.

If the approver for a request type is on leave, the card sits. That is the reason for the backup column. Review the approver list when the roster changes, and again after a long absence.

A request can be too vague to act on. A person writes "my computer is broken". Black Rock's small business IT support request checklist asks the requester for the blocked task, the staff affected, the timing, any evidence and a contact who can verify the fix, and says to keep updates about one issue under its existing request number. Ask for those details in the request type description, and put new details on the same request instead of opening a new one.

An access request can be granted too widely. A request for a shared folder should name the folder, the person and the reason, and the approver should be the one who answers to the client. When in doubt, grant the narrower access first. This one belongs to the approver and never to the agent.

The weekly check can lapse. A check that belongs to everyone will be skipped. Put it in the sorter's calendar, with a recurring Monday slot, and make the sorter the same person who is named in the channel description.

People do the work and decide the approvals: money, access to client data and anything that changes a person's rights keep a named human approver. For approvals in general, the guide to an approval request in a small team's Slack covers cards, deadlines and what to do when an approver does not answer.

How do you know the process works?

You know it works when three numbers are good after a month: the share of requests claimed within their no-pickup-by time, the share of approvals decided within a working day, and the number of requests found by complaint. Aim for the third to be zero.

Run it as a one-month pilot with a short list.

  1. Count the requests that arrived in the month, by type, and move any type that is under a handful a month into "Something is broken".
  2. For each type, compare the no-pickup-by time against when the request was actually claimed. If most requests are claimed in half the time, shorten it. If the sorter keeps missing it, change the owner, not the number.
  3. Read the ratings that come back on done requests, and look at the low ones first.
  4. Count approvals that sat longer than a working day, and add or change the backup for that type.
  5. Review the list of types. A sixth type that keeps appearing in the free text is a new row; a type with no requests is a row to merge.

Treat the five rows as a first draft. SherpaDesk advises tracking your own request types for a month, and your own count is better evidence than any table in an article.

What to do next

Copy the five-row table into a pinned message in your triage channel today, put one name in each Owner, Backup and Approval cell, and set a fifteen minute recurring Monday slot for the person who will do the check. If you want the Slack side set up for you, add the Kipwise agent to Slack and use the free trial: the agent is $10 per user per month with a minimum of three users, and its request desk is part of the Premium plan that comes with it. Ask it "what are my requests?" after the first week to see the first list.

Topics

Related posts

Put an AI teammate in your Slack

Free trial on install: $2 of AI credit for 7 days on the fast model, or $10 for 14 days with all models on a paid Slack plan or for existing Kipwise customers.