# An IT service desk rebuilt in three phases: tickets, runbook, automation and the team that runs it

An IT service desk is the one place every IT request in a company goes, from a password reset to a server that is down. Goldenroz sets up or rebuilds the service desk inside your organization: the ticketing system, the written procedures, the automation for repeat requests and the structure of the team across tier 1, 2 and 3. The work is led by Shai Goldenberg, our CTO, who managed the help desk of an industrial company with about 400 users for four years. Each phase has a written scope and a fixed price, quoted after a free scoping call.

**Fixed price per phase, quoted after a scoping call**

Updated: 2026-11-18. By Shai Goldenberg.

## What usually goes wrong

- **A new IT leader inherits a mess:** A CIO or IT director starts a new role and finds no working queue, no written procedures and a team that waits to be told what to do.
- **Requests arrive by every channel:** Phone, email, chat and the corridor. Nobody can say how many requests came in last month or how long they took.
- **The knowledge is in two people's heads:** When one of them is on leave, a routine fault takes a day. When one of them resigns, it takes a quarter.
- **Tier 1 with nothing behind it:** The first line can reset a password. Anything that touches a server, a switch or the directory sits in a queue with no engineer assigned.
- **Vendors billed by the hour with no ceiling:** Each call to an outside technician is another invoice, and the same fault is paid for again next month.

## What is included

- **Assessment of the current state:** What is opened today, through which channel, who handles it and how long it takes. Mapped by tier, with the gaps listed in priority order.
- **Ticketing system:** A new system or the existing one set up again: a short category tree, routing rules, priorities and target times that you define. The tool is chosen together with you.
- **Automation for repeat requests:** Password reset, new employee setup, employee exit and access requests handled by a form and a workflow, so the team stops typing the same steps.
- **Runbook and internal knowledge base:** Short written procedures: what to do when the mail server stops, when a user is locked out, when a site loses its connection. Written so that a new technician can follow them.
- **Team structure:** Role definitions for tier 1, 2 and 3, a handover rule between them, an on-call arrangement, and technical interviews for candidates you bring.
- **Monthly support after the build:** Remote guidance for the team lead, tier 3 work on servers and network, and a monthly report for management: opened, closed, time to resolve and what keeps coming back.

## How an IT service desk works, from a request to a closed ticket

A user reports a problem through one channel: a portal, an email address or a phone number. The system opens a ticket, gives it a category and a priority, and sends it to tier 1. Think of the front desk at a clinic. Every patient is registered in the same place, and the desk decides who sees them.

Tier 1 handles what can be solved with a procedure: passwords, access, a printer, a laptop. Tier 2 handles the systems themselves: mail, the directory, business applications, the network. Tier 3 handles servers, storage, security and outside vendors. A ticket moves up only when the tier below has written down what it checked.

The split decides the cost. A password reset handled by a server engineer is expensive. A server fault handled by a first-line technician takes all day. A service desk that works sends each request to the cheapest person who can close it.

## Service desk outsourcing or a team you own

Service desk outsourcing moves the first line to an outside call center that answers by script. It suits organizations with a high volume of simple requests. It breaks down when a ticket needs someone who knows your servers, because the script ends and the ticket comes back to you.

Help desk outsourcing is priced per user, per ticket or per month. Before signing, ask who handles tier 2 and 3, who owns the ticket history, and what happens to the knowledge base if you leave.

Goldenroz does not operate a call center. We build the service desk as your own: the system, the procedures and the accounts are in your name, and your staff answer the users. After the build we stay on a monthly scope for the work your team cannot cover. Organizations that want the whole environment run for them can look at our [managed IT services](https://goldenroz.com/managed-it-services/) retainer.

## The first 90 days of a service desk rebuild

Weeks 1 to 3 are the assessment. We read the last months of requests wherever they live, sit with the technicians, and list every system the desk is expected to support. You receive a written current state and a work plan in priority order. That document is yours whether or not you continue.

Weeks 4 to 10 are the build. The ticketing system goes live with the IT team first. The five most frequent requests get a form and a workflow. The first procedures are written from real tickets. A date is set after which requests are accepted only through the desk.

Weeks 11 to 13 are handover. We read the first month of data with IT management, adjust categories and targets, and agree the monthly scope. A larger tool rollout across several sites is described on our [ITSM implementation](https://goldenroz.com/itsm-implementation/) page.

## What it costs

Each phase is quoted separately at a fixed price after a free one-hour scoping call. We do not publish figures for this service yet, because the price depends on the number of users, sites and systems. Software subscriptions are paid by you directly to the vendor.

- Phase 1: assessment: Fixed price, quoted after the call (Two to three weeks: current state and a work plan in priority order)
- Phase 2: build: Fixed price, quoted after phase 1 (Ticketing, automation, runbook, knowledge base and team structure)
- Phase 3: monthly support: Monthly fee for a written scope (Remote guidance for the team, tier 3 work and a monthly report)
- Scoping call: $0 (One hour with Shai)

## Who it is not for

- Companies that want an outside call center to answer their users. We do not operate one.
- Teams with a few requests a day. A shared mailbox with rules is enough.
- Buyers who need a certified ServiceNow partner or formal ITIL training.

## Questions buyers ask

### What is an IT service desk?

It is the single point of contact between a company's employees and its IT team. Every request and fault is recorded as a ticket, sent to the right person and tracked until it is closed. A help desk fixes faults. A service desk also handles requests, access, onboarding and changes.

### What are tier 1, tier 2 and tier 3 support?

Tier 1 solves common requests with a written procedure, such as passwords and access. Tier 2 handles systems: mail, directory, applications and network. Tier 3 handles servers, storage, security and vendors. A ticket moves up only when the lower tier cannot close it.

### How long does it take to rebuild a service desk?

Plan for about three months: two to three weeks of assessment, six to eight weeks of build and a few weeks of handover. The pace depends on how many sites and systems the desk supports and how quickly decisions are made on your side.

### How much does it cost?

Each phase has a fixed price, quoted after a free one-hour scoping call. We do not publish a figure for this service yet. The ticketing software subscription is paid by you to the vendor.

### Do you hire the team for us?

We define the roles and run technical interviews for candidates you bring. Recruiting and employment stay with you.

### Which ticketing system do you use?

The one that fits your size and budget. We compare two or three options in writing and you choose. Goldenroz is not a reseller or certified partner of any ticketing product.

---
Page: https://goldenroz.com/service-desk-setup/
Book a free one-hour call: https://calendly.com/daniarozin/daniel-rozin-consultation-1-hour-clone
