Keep urgent IT problems in the queue and planned work in the diary
A practical way for IT consultants to separate reactive support from booked sessions: remote fixes, user training, after-hours maintenance and consultation calls, each with its own route.
An IT consultant's week usually has two kinds of client contact mixed together. One is reactive: the server is down, a director cannot get into email, a laptop has been stolen. The other is planned: a remote session to set up a new starter, an hour of training on SharePoint, a firewall update that has to happen after close of business. Problems start when both arrive through the same door.
This guide is about drawing that line clearly. Urgent issues go to your ticketing system, PSA or support phone line, where they can be triaged. Planned work goes on a booking page, where the client picks a time that suits them and you. A scheduling tool such as Calenix handles the second half well. It is not a ticketing system and should not pretend to be one. For the wider habits behind this, see our guide on reducing back-and-forth when scheduling meetings.
Reactive support and booked sessions are different jobs
It helps to sort every type of client contact into one of two buckets before touching any software.
What should never go through a booking page
- Outages and security incidents. A client with ransomware on a file server should not be choosing a slot next Tuesday. They need your phone number or your emergency ticket route, and your on-call process.
- Anything with a response-time commitment. If your agreement promises a response within a set number of hours, the clock starts in the ticketing system, not when a meeting is booked.
- Requests that need triage first. 'My computer is slow' might be a two-minute fix or a failing drive. Log it, look at it, then decide whether it needs a session.
What a booking page handles well
- Booked remote-support sessions. Non-urgent fixes that need the user present: printer set-up, mailbox migration, a new phone enrolled in device management.
- User training. 30 or 60-minute sessions on Microsoft 365, password managers or a new line-of-business system, for one person or a small group.
- After-hours maintenance windows. Slots outside office hours where the client confirms the system can be taken down and someone is available to test afterwards.
- Consultation calls. A planned conversation about a problem that is not urgent but needs thought, such as replacing an ageing NAS or tidying up user licences.
The bridge: a booking link inside the ticket reply
The two systems meet in one place. When a ticket turns out to need a session with the user, your reply includes a link to the right event type: 'This needs about 30 minutes with you at your desk. Please pick a time here.' The ticket stays in your PSA as the record; the booking handles the diary. Put the ticket number in a booking question so the two can be matched up later.
For remote sessions, connect Zoom or Microsoft Teams so each booking gets a meeting link, or include your remote-access instructions in the confirmation. Our guide to adding video meeting links to appointments covers the options.
What goes wrong when support and bookings share a door
Consultants who publish one general 'book time with me' link usually find it used for everything. A client books a 15-minute slot on Thursday for a problem that has stopped their accounts team working since Monday, and you only see it when the reminder arrives. Or a minor request lands in your phone queue during a genuine outage, because the client could not tell which channel was which.
The cost shows up in three places. First, response times: urgent issues hidden in a booking calendar are not being triaged. Second, focus: engineers interrupted by unplanned calls lose the half-hour either side. Third, billing: work done on an ad hoc call is easy to forget to log against a prepaid block of hours.
Separating the routes fixes all three. Clients learn that the phone or ticket portal is for 'it is broken now' and the booking link is for 'I need some of your time'. You get a diary of planned sessions you can prepare for, and a queue of urgent issues you can triage in order.
After-hours work benefits most. A booked maintenance window, confirmed by the client in writing through the booking form, is far better than a verbal 'any time this week after six' that leaves you guessing. Our page on avoiding meetings outside business hours explains how to keep these windows deliberate rather than creeping into every evening.
What clear separation gives you and your clients
Urgent issues stay visible: outages reach the ticket queue or phone line instead of a calendar slot days away.
Prepared sessions: booking questions collect the ticket number, device and user before you connect.
Fewer interruptions: planned work sits in blocks, so engineers are not pulled off tasks for every request.
Accurate prepaid block usage: each booked session has a type and length you can log against the client's hours.
Deliberate after-hours work: maintenance windows are booked and confirmed, not agreed vaguely on the phone.
Clients who know where to go: one route for 'broken now', another for 'I need your time'.
How to set up booked support alongside your ticketing system
Write down your urgency rule — Decide in one sentence what counts as urgent, and put it in your service agreement, your email footer and every booking page description.
Create one event type per session kind — Remote-support session, user training, maintenance window and consultation call each get their own duration, buffer and questions.
Ask for the ticket number — Add a required booking question for the ticket or job reference on support sessions, so bookings match up with your PSA records.
Restrict maintenance windows to after hours — Give the maintenance event type availability only in the evenings or at weekends, with a long minimum notice so you can plan the change.
Connect calendars and meeting tools — Connect your Google Calendar or Outlook so on-site visits block slots, and add Teams or Zoom links to remote sessions.
Paste booking links into ticket reply templates — Add the right link to your canned responses so a ticket that needs a session can be booked in the same reply.
Which route should each request take?
| Feature | Route | Typical response | Booking question to ask |
|---|---|---|---|
| Outage or security incident | Phone line or urgent ticket | Per your agreement | Not booked |
| Non-urgent fault needing the user | Ticket, then booking link | Next suitable slot | Ticket number |
| New starter set-up | Booking page | Before the start date | Start date and devices |
| User training session | Booking page | Within a week or two | Topic and number of attendees |
| After-hours maintenance window | Booking page, after hours only | Planned ahead | Who will test afterwards? |
| Consultation about a future change | Booking page | Within a week or two | What decision is coming up? |
Good habits for booked IT support
Print the urgent phone number or portal link at the top of every support-related booking page.
Keep support session links out of your public website and share them through tickets and client emails.
Use a buffer after remote sessions to update the ticket before the next one starts.
Tell clients how booked sessions draw down their prepaid support block, in plain language.
Confirm maintenance windows in writing, including the expected downtime and who is on call.
Review which event types are booked most each quarter and adjust lengths to match reality.
Cancel and rebook rather than running over, so the next client's session starts on time.
Common mistakes when booking support calls
Using the booking page as an informal ticketing system with no triage.
Leaving the booking link visible in places where clients look during an outage.
Not asking for a ticket number, so sessions cannot be matched to the work log.
Opening after-hours slots every evening and never getting a night off.
Running every session as 60 minutes when most fixes take 20.
Assuming email reminders alone will get a busy user to their desk; ask clients to accept the calendar invite as well.
Example: a solo IT consultant in Manchester
Take a fictional solo IT consultant in Manchester who looks after a dozen small offices: two dental practices, an architect, an estate agency and several professional firms. Clients buy prepaid blocks of ten support hours, and she uses a ticketing tool for logging work.
Her problem was not the ticket queue. It was everything around it. Clients phoned her mobile for training requests, emailed about after-hours updates, and occasionally booked her public 'consultation' slot for a broken printer. She separated the routes:
- Urgent: the support phone number and ticket portal, printed at the top of every booking page and in her email signature.
- Remote-support session, 30 minutes, ticket number required, link sent only in ticket replies.
- User training, 60 minutes, up to three attendees, with a question on the topic.
- Maintenance window, two hours, Tuesday and Thursday evenings only, five working days' notice.
- Consultation call, 45 minutes, open to clients for planned changes.
She runs it on Calenix Individual with Microsoft Teams links on remote sessions and her Outlook calendar blocking on-site visits. Confirmations and reminders go by email. Each booked session is logged against the client's prepaid block. The ideas in how to share a meeting booking link helped her decide which links went where, and automatic appointment reminders cut down on users forgetting training.
The illustrative maths: if separating routes saves three 20-minute interruptions a day across a five-day week, that is five hours a week back, or around half a prepaid block, every week.
FAQ
Frequently asked questions
Booked support, done properly
Give planned IT sessions their own booking page
Set up remote-support, training and maintenance event types with Teams or Zoom links, and keep urgent work in your ticket queue. Start free, no card needed.