
Service where nobody has to chase.
Every request becomes a ticket, with client, project and time booked. Your client keeps sending emails as usual, your team works in order, and every hour booked is ready to invoice.
The problem
Special requests are part of your business. Without a system, they cost you money.
If you work for large clients and industry, you know this: alongside the contract there are special requests, small adjustments, bug reports and questions only one particular person can answer. Each request on its own is small. Together they are a large part of your work.
While there are only a few, email works. With every new client it gets harder to keep track: who is on it, what is done, and how much time did it take? What isn’t captured as a ticket doesn’t get booked. And what isn’t booked, you can’t invoice.
Nothing has to change for your client. Anyone who doesn’t like tickets keeps writing to your support address. On your side, it arrives as a ticket.
When you work this closely with clients, service is part of your product. Smaller providers in particular win here against large ones, because they respond faster and more personally. To keep that working with thirty clients, you need a system in which every request takes the same path. That keeps a close client relationship stable for years.
What you should know about every client
- Which requests are open right now?
- Who is working on them right now?
- How much of the maintenance contract is used up?
- Which hours haven’t been invoiced yet?
In Leadtime, this is on the ticket and the project, without anyone keeping a list.
What it looks like
The Service area in three minutes, in the real app.
From the support project and the ticket to the helpdesk inbox. Jump straight to the part you care about.
Video transcript
Introduction
This video shows in four steps how you handle your clients' requests in Leadtime: the support project, working on a ticket, time and client access, and finally the helpdesk that turns emails into tickets.
The support project
Every client has a support project. Here you see how many hours have gone into it so far and how many requests are open right now. And here it says that the client has access to this project themselves.
Working on a ticket
Every request is a ticket. The board shows what is new, what is being worked on and what is waiting for a reply. Each card shows the priority, the kind of request, who is on it and the time booked so far. Let's open a ticket. A client reports that several users can no longer log in to a server. The right-hand column holds the ticket's key data, for example the priority. Below that is who is responsible. You can also assign the ticket to an agent. It works with the permissions of its role and books its time on the ticket. Further down are the estimated effort and whether the ticket is billed against a support retainer. If the fix needs a quote, you create it here as an express quote, right on the ticket. You book the work itself with “Book time”, also right on the ticket.
Time and client access
The project brings all bookings together: who worked on what, on which day, with daily totals. In the project settings you decide whether your client may open it and which documentation pages they see.
The helpdesk
To have requests arrive by themselves, connect your support mailbox. Leadtime checks it every minute and turns new emails into tickets. Your team's replies go out from the same mailbox. New tickets get your defaults: which project they land in, the type, the status and who is responsible. That keeps every request in one place, from the mailbox to the booked time. Closed tickets with booked time are suggested for invoicing later, in the invoice review.
Photo: The managing director of an IT service provider stands with a printed list next to a colleague’s support desk, looking thoughtfully across the room.
Managing director of an IT service provider
“How many hours of support are we actually giving away every month?”
How every hour booked gets invoicedHow Leadtime solves it
Every request becomes a ticket. Nothing changes for your client.
In Leadtime, tickets are ordinary tasks. They go through the same planning as your projects, time is booked on the ticket, and everything billable is waiting in the invoice review.
From email to invoice: one ticket, no back and forth.
If a ticket turns into a bigger undertaking, you set up a project for it.
More on projectsHelpdesk
Your client sends an email. You receive a ticket.
Connect your support inbox, whether Google, Microsoft 365 or IMAP. Every email becomes a ticket, and your rules per client put it straight into the right project. If you like, your client gets an acknowledgement straight away, and your reply from the ticket reaches them as an ordinary email.
What you get: Requests no longer get stuck in individual inboxes, and your client doesn’t have to learn anything new.
Tickets in the plan
This morning’s ticket is work too. Now it’s in the plan.
Tickets sit in the same planning as your projects, with assignee, estimate and time booked. So project management can see why Pia’s week is suddenly full, and support doesn’t have to beg for time.
What you get: Support and projects share the same people. Whoever plans sees both and can say honestly what still fits this week.
Support contingents
How much of the maintenance contract is left? From now on a number, not a hunch.
A contingent has hours, a price and a period, and the time you book on tickets assigned to it is deducted from it. You can carry over what’s left in the period if you like. Anything beyond it shows up as not covered in the invoice review.
What you get: Extra work gets invoiced instead of given away, and your client sees the time booked on every ticket.
Photo: A client sits relaxed at his laptop, reading a message with a smile.
IT manager at a client
“Where can I actually see what happened to my request?”
How your client sees the statusClient portal
Your client sees for themselves what is going on and what they still need to do.
The client portal is guest access. Invite your clients as guests at no extra cost. They see a home page with your logo, their open items and the projects you share. What you discuss internally stays internal.
What you get: Fewer calls asking “How far along are you?”. Your client checks whenever it suits them and sees what is waiting on them.


- Your logo, your colourPlus your own welcome, as text or an image. Your client knows at a glance whose portal this is.
- For you to doWhatever is currently with the client, with a due date: an approval, a form, a detail your team is waiting for.
- Shared projectsOngoing support or a one-off project, with open tasks and pages from your documentation. You decide which pages they see.
Working with your client
Your client enters it, your team gets it done. Both see the same status of the task.
In shared projects, your clients create tasks themselves, fill in forms, comment and see the time booked. On your side, that is instantly a ticket in the right project.
What you get: Nobody has to retype emails, and you settle questions right on the ticket instead of on the phone.
- 1Ms Lehner reports a new starter
- 2On your side: a ticket, already with Pia
- 3Pia does it, Ms Lehner reads it at once
Your client sees
You see
Objects
Which server was that again? The ticket knows.
Servers, printers, firewalls, licences: whatever you look after for your clients, you set up as an object, with your own types, fields and statuses. On the ticket you see which device it concerns, and on the device every ticket it has ever had.
What you get: Whoever takes the ticket sees the device’s history and doesn’t start from scratch.
What you save
A routine ticket in 2 minutes instead of 20.
Example: an IT service provider with 20 employees and 250 tickets a month, 30 per cent of them routine. The agent solves the routine question with your documentation, and your team checks the answer.*
270fewer hours a year spent on routine tickets
10×faster per routine ticket20 minutes today, 2 with Leadtime, your team’s working time
€13,000less in staff costs a yearapproximately, at €75,000 per full-time role and 1,600 hours a year
* Model calculation for the “routine ticket” process with our calculator and mid-range assumptions, not a promise of results. In the model, the other tickets get a little shorter too, because client, project and contingent are already assigned.
Everything at a glance
Every feature for service and support.
Each feature comes with a sentence on what it does for you.
Connect your inbox
Your support inbox on Google, Microsoft 365 or any IMAP server becomes your helpdesk.
Every email becomes a ticket
Every client email becomes a ticket, and none gets lost between three inboxes.
Rules per client
Each client has its own helpdesk rules, for example which project its tickets go into.
Reply from the ticket
You reply in the ticket, and your client gets an ordinary email from your inbox.
Confirmation of receipt
Your client hears straight away that the request has arrived.
Agents in the helpdesk
An agent with its own account takes on tickets, assigns them, solves routine questions with your documentation and books its time.
Home page with your logo
Your client sees your logo, your colour and your welcome message, as text or an image.
For you to do
Approvals, forms and details your team is waiting for, each with a due date.
Shared projects and pages
Your client sees the projects you share and exactly the documentation pages you choose.
Create and comment on tasks
Your client logs requests directly, adds comments and sees the time booked.
Accept express quotes
Your client accepts or declines a fixed-price quote right in the portal.
Guest access at no extra cost
Guests cost nothing extra. They only see what you share, and internal stays internal.
Tickets are tasks
A ticket works like any other task, with status, owner, comments and mentions, as a list or on a Kanban board.
In the same plan
Tickets sit in the weekly plan next to project tasks, so you can see why a week is full.
Forms for requests
A form asks for what you need to solve it, such as the device, the error message and the urgency.
Time tracking on the ticket
Time runs on the ticket and comes straight off the contingent.
AI summaries
Leadtime summarises long threads, so nobody has to read them from the start.
Support contingents
Hours, price and period for each contract. You can always see what's used and what's left.
Several contingents per project
For example one for maintenance and one for training, in the same project.
Carry-over
Unused hours can carry over into the next period if you want.
Hours not covered
Anything beyond the contingent is shown separately, so you invoice it instead of giving it away.
Objects
Servers, printers, firewalls or licences, linked to the client, project and ticket. Each device lists every ticket it has ever had.
Photo: A support specialist leans back at his desk, hands behind his head, glancing sideways with a weary smile.
Support at an IT service provider
“And who answers the twentieth VPN question this week?”
The answer: the agentThe agent
New emails are already sorted when your team opens them.
The agent works in the team with its own account and its own role. It assigns requests to a client and project, sets the priority and passes them on to the right person. It solves routine questions with your documentation and writes the solution into the ticket. It books its time on the contingent.
Your team takes care of whatever needs expertise. Press ⌘K (Ctrl+K on Windows) to ask Leadtime things like which client keeps needing more than the contract covers. The answer draws on your tickets, times and contingents and shows only what you are already allowed to see.
In the inbox
The agent
New emails in the support inbox.
- Read5 emails, one of them advertising
- Sortby client, project, priority and owner
- Solvethe VPN question, using your guide
- Commentthe solution is in the ticket
- Handed overthe wrong prices to Jonas, with a summary
- Timebooked on the contingent
- Your teamtakes on what needs expertise
In Leadtime
What the agent may do is set by its role, like for everyone on the team. What it has done is on the ticket and in its time entries.
More about agentsNext step
Let us show you on one
of your client emails.
30 minutes, one real request from your day-to-day work. Ideally the one nobody has answered for too long.
ClientsOpportunities, quotes, product catalogue
ProjectsPlanning, tasks, sign-off
ServiceHelpdesk, tickets, retainers, assets
TeamPeople, absence, time
MoneyInvoices, e-invoicing, insights
AgentsLeadtime Agent, your own agents, automation



