Request a quote
Emergency SectorsCareers About us Blog Get in touch
Three IT engineers at dual-monitor desks in an Amsterdam canal house at dusk, one with a headset explaining something

1st, 2nd and 3rd line support: what each line should fix

First line, 2nd line support, third line: every service desk proposal uses the terms, and almost none says what they mean for you. This is not about job descriptions. It is the buyer’s side: what you can expect from each line, where a ticket gets stuck between two of them, and what to ask before you sign.

6 min read Written by the ITproposal team
Short answer

The lines differ in knowledge and access rights, not in importance. How much the first line is allowed to fix decides how fast most tickets are closed.

A ticket should keep one owner as it moves between lines; the person who raised it should never have to start again.

Third line often sits with a manufacturer or software vendor. Agree who holds that contract and who makes the call.

1st, 2nd and 3rd line support: how it is divided

The split into lines says how much knowledge and which rights are needed to resolve a ticket. It is not a ranking and not a measure of how important the ticket is: a critical outage can be fixed by first line, a small question can need all three.

  • First line: takes every ticket, logs it, asks the right questions and resolves what can be done remotely with a set procedure. Passwords, access, a printer that needs adding again, a setting in Outlook.
  • Second line: specialists with more knowledge and more admin rights. A fault in the network, on a server, in the Microsoft 365 configuration, or a device that has to be looked at on site.
  • Third line: where second line cannot go further because the answer lies with the maker: the hardware manufacturer, the software vendor, or an architect who knows the design.

Some organisations also speak of line zero: what users can do themselves with a knowledge base or a self-service portal. That only works if the articles are right and somebody keeps them up to date.

What first line may fix decides the whole service desk

Most tickets are simple, and the fastest answer is the one given at first contact. Whether that happens depends less on the people in first line than on what they are allowed to do. A first line without admin rights is a switchboard: it notes the ticket, passes it on, and the user waits for someone else.

Agree which actions first line may carry out itself. Resetting a password or a second factor after an identity check, granting mailbox access after approval, reinstalling a standard application, removing a lost device from management. Every action on that list is one ticket fewer that has to wait.

Two things make that safe. Set procedures, so everyone in first line does the same thing. And an identity check that a convincing voice on the phone cannot talk its way past: whoever may reset a password has to be certain who it is for.

2nd line support and escalation: no starting over

In practice things go wrong not within a line but between them. A ticket goes to second line, which asks the same questions again, and the user explains for the third time what is going on. Or worse: the ticket bounces back and forth because nobody thinks it is theirs.

  • One owner. The service desk owns the ticket until it is resolved, even when the work sits with another line or a supplier. The user has one point of contact.
  • A complete ticket at handover. What was asked, what has already been tried, screenshots and error messages. Whoever picks it up starts where the last person stopped.
  • Escalating on knowledge and escalating on urgency are two different things. The first goes to a specialist because the knowledge is missing; the second goes to a manager because it is taking too long or affecting too much. Agree when each happens.

Third line often sits outside your supplier

Many people picture third line as the supplier’s best engineer. More often it is a different organisation: the manufacturer deciding on a warranty replacement, the vendor of your finance or line-of-business software, or Microsoft itself when the service has a problem.

That raises three questions worth answering up front:

  • Who holds the support contract? A software vendor only helps customers with a valid contract, and that is usually in your organisation’s name.
  • Who may call on your behalf? Agree whether the service desk may open and follow up the case with the vendor, and what authorisation that needs.
  • Where is the case number kept? In the ticket, so the issue stays one story even with an outside party, and the time spent waiting for them is visible.

What to look for per line in a proposal

“First and second line support” on a proposal says little until it says what is included. Check these points:

  • Which lines are included and which are billed separately. Above all: is second-line work in the price, or charged by the hour on top?
  • Remote or on site. Second-line work on a device or network sometimes has to happen on location; does it say who comes and how quickly?
  • Hours of cover per line. First line may be reachable for longer than the specialists; know what happens out of hours to a ticket that needs second line.
  • Which rights first line gets in your environment, and who grants them.
  • Reporting per line: how many tickets were resolved at first contact, how many were escalated, and how long they waited with an outside party.

Response and resolution times belong in the service level agreement; how to write one you can rely on is in SLAs you can actually meet.

Your own IT person in the line model

Many organisations do not outsource everything. There is an in-house IT person, an application manager or a few key users who help colleagues. That is valuable as long as it is clear who is which line; otherwise users call both and the same work gets done twice.

  • In-house IT as second line for your own applications, with the outsourced service desk as first line and for the infrastructure.
  • Key users as line zero for questions about using a package, with a clear boundary: faults always go to the service desk.
  • One ticketing system that both sides work in, or pass tickets through, so nothing disappears into a mailbox.

Write the split down in a single table: for each type of ticket, who takes it, who resolves it and who it is passed to. That table prevents more arguments than any contract.

Where our work stops

What we do. We provide first and second line for your devices, network, servers and Microsoft 365, on site in every country where needed. We keep ownership of a ticket until it is resolved, even when it sits with a manufacturer or software vendor, and we open and follow up that case on your behalf if you authorise us to.

What we do not do. We are not the vendor of your finance, ERP or line-of-business software and we do not change another product’s code; third line for such an application is that vendor, under your contract with them. Whether a faulty device is replaced under warranty is the manufacturer’s decision. We make sure the issue reaches them complete and that you do not have to chase it.

Frequently asked

Questions we get about this

The five that come up most often.

What is 1st line support?

First line support is the first point of contact of a service desk. It takes every ticket, logs it and resolves what can be done remotely with a set procedure, such as passwords, access and simple settings. Anything that needs more knowledge or rights goes to second line with a complete ticket.

What does 2nd line support do?

Second line consists of specialists with more knowledge and more admin rights than first line. It handles faults in the network, on servers, in the cloud configuration or on a device that has to be looked at on site. If second line cannot resolve it either, the ticket goes to third line.

What is 3rd line support?

Third line support is the last step, where the answer lies with the maker: the hardware manufacturer, the software vendor or an architect who knows the design. It is often a different organisation from your IT supplier. That is why it has to be clear who holds the support contract and who opens the case with that party.

How many tickets should first line resolve itself?

There is no fixed number, because it depends on your environment and on which actions first line is allowed to carry out. More useful than one figure is the trend and the reason behind each escalation. If first line keeps escalating the same kind of ticket, it is missing a right or a set procedure.

Who calls the software vendor when third line is needed?

That is agreed in advance. If you authorise us, we open and follow up the case with the vendor and keep the case number in the ticket. The support contract with that vendor stays with your organisation, and only the vendor changes its software.

Related services

Further reading

What the lines in your service desk connect to.

Shall we put your lines on paper?

Send us how tickets come in today and who resolves them. We will turn it into a split per line, with what first line may do and who calls third line.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call