Skip to content

Event calendar

Enterprise feature (new in 1.20.6, helpdesk). See the Helpdesk overview.

Some requests are for a moment in time: set up the boardroom for Thursday’s meeting, have a laptop ready for a new starter’s first day, meet a visitor at reception. Such a ticket can carry an event: when it starts and ends, where, and how long before the start everything must be ready.

A ticket with an event:

  • shows on the desk’s Calendar;
  • can’t be solved until its setup is marked complete;
  • reminds its owner, or the team, before the setup is due.

Until a ticket has an event, nothing about the desk changes.

Every ticket has an Event block in its side panel. Add an event asks for:

  • Starts and Ends, or All day with a first and a last day.
  • Place (optional): a room, a site or an address. Places used before are suggested as you type. Requesters see the place on their request.
  • Setup ready: how long before the start everything must be in place, from “At the start” to a day before. The block then says “Ready by 13:30 · 30 minutes before”.

Any agent who can work the ticket can add, change or remove its event, until the ticket is closed. A ticket has one event. Each change writes an agents-only line on the timeline (“Ana added an event: Fri 20 Nov 2026, 14:00 to 15:30 (London time) at Boardroom A.”). Requesters never see the block or those lines.

Times. You type times in your own time zone, and everyone sees them in theirs. An all-day event keeps its dates wherever it is read. When the clocks change, a time that happens twice is read as the first of the two, and a time that is skipped is moved on by the hour that was skipped.

When two events name the same place and their times overlap, both tickets show a Double-booked warning with a link to the other ticket. Setup time counts as part of the event. Places are compared without regard to capitals or extra spaces, so “Boardroom A” and “boardroom a” are the same room.

It is a warning only. Nothing is blocked, because the desk can’t know whether a room can hold two things at once. An agent sees the other ticket’s number and subject only if they could open that ticket; otherwise the warning names its team and time.

A request type can put its requests on the calendar by itself. In Desk settings → Forms and fields → Request types, the card Goes on the calendar has:

  • Put its requests on the calendar: the switch.
  • Start: the question that holds when the event starts. It must be a Date and time question (a new kind of answer in 1.20.6) or a Date question, which makes an all-day event.
  • End (optional): left out, a timed event is one hour long.
  • Place (optional): a short-answer or pick-one question.
  • Setup ready: the lead time its tickets start with. Agents can change it on the ticket.

A request sent with that type opens a ticket with the event already filled in. Times the requester picks are read in their own time zone.

When someone forwards or sends a meeting invite to a help address, the ticket it opens gets the invite’s time and place as its event. This works for invites from Outlook, Google Calendar and Apple Calendar.

  • An update to the same meeting (a later revision of the same invite) changes the event on the same ticket instead of opening a new one. From 1.20.34 it may come from the ticket’s requester or from the meeting’s organizer, and it is matched on the help address it was sent to. The desk records the organizer only when the invite names its own sender as organizer and that sender passed the sender check, so an attendee or someone forwarding the invite can’t become the organizer. An organizer’s update finds its ticket only when exactly one open ticket has that meeting and organizer; with more, it opens a ticket of its own. When the organizer isn’t the requester, their email goes on the ticket as an internal note (agents only) and the update is applied. Anyone else’s invite with the same meeting id opens a ticket of its own and never moves or cancels this one. Someone copied on the ticket never adds or changes its event: their invite is added as a note. An update that only changes the guest list or the description is added to the ticket and changes nothing else.
  • A cancellation marks the event Canceled and adds an internal note. The ticket is not closed: someone may still need to take the room down or tell people. A canceled event no longer holds the ticket open and is no longer reminded about. A parked ticket wakes (see below).
  • A meeting that repeats puts only its first date on the calendar, and a note on the ticket says so.
  • An invite whose time zone the desk doesn’t know is read in the desk’s zone, with a note asking an agent to check it.

Only the event is read from an invite. Its guest list and anything else in it are ignored.

A ticket with an event stays open until someone confirms the work is done.

  • Mark setup complete in the Event block records who did it and when. Not complete after all undoes it.
  • Pressing Solve before that opens the Before you solve dialog with a Setup complete tick box. Tick it and the ticket is solved and the setup marked in one step.
  • Every other way of solving or closing is refused until it is done: the status menu, Send and set Solved, bulk edit, macros, automations, the API and the Claude connector. They all get the same sentence: “Before you solve, this ticket needs: the event setup marked complete.”
  • The desk never closes such a ticket by itself. The step that closes solved tickets after a few days, and the retention clean-up, both leave it alone.

An event that has passed still holds its ticket open, so a missed setup isn’t lost. Desk settings → Event calendar lists those tickets under Setup never marked. Mark the setup complete, or remove the event, and the ticket can be solved as usual.

A canceled event holds nothing open.

Desk settings → Event calendar → Reminders. It needs the desk capability Helpdesk settings (Admins, out of the box).

  • Remind this long before setup is due: up to five lead times, from 15 minutes to 7 days. Out of the box: 1 day and 1 hour. They count from the “ready by” time, not from the start of the event.
  • Remind again when an event starts before its setup is marked complete: on, out of the box. It goes to the ticket’s owner and the team’s leads, once.
  • Who gets them: The owner, or the team when nobody owns it (out of the box), or The owner and the team.
  • Also message agents in Microsoft Teams or Slack: a direct message as well, once a chat app is connected.
  • Setup time for an event added by hand: what the Event block offers first.

Each agent chooses how they hear about them (bell, email, push) under Event reminders in their notification settings. Quiet hours apply.

Each reminder is sent once. Moving an event sets its reminders up again for the new time. No reminder is sent for a ticket that is solved, an event that is canceled, or a setup already marked complete. If the desk was switched off when several were due, only the nearest one is sent.

New in 1.20.34. A ticket for an event months away doesn’t need to sit in the queue, grow old and miss its targets. Park it: it goes On hold, leaves the queue, its reply and resolution targets pause, and it comes back by itself when it’s time to prepare.

A parked ticket wakes a number of working days before the event’s setup must be ready: the prep window. Working days are those of the ticket’s team calendar (Teams and hours), so weekends and holidays don’t count, and it wakes when that day opens. An all-day event counts from the start of its first day in the desk’s time zone.

Out of the box the prep window is 10 working days. Change it in Desk settings → Event calendar → Holding tickets until the event (0 to 60), or for one ticket when you park it.

In the ticket’s Event block, choose Hold until the event. The dialog shows the prep window and when the ticket would wake. Choose Hold until the event to park it. You need the same permission as for changing the ticket’s status.

If the wake date has already passed, or is less than an hour away, the desk says so in one sentence, such as “This event is too close to park: it would wake today.”, and the ticket stays as it is.

A parked ticket shows Parked until Tue 3 Mar · for the event on Sun 15 Mar under its subject, with two buttons:

  • Wake now brings it back to the queue straight away.
  • Change prep window moves the wake date.
  • It isn’t in My open, Unassigned, All open, Waiting or its team’s list, and isn’t counted in them. The Parked view lists every parked ticket, soonest to wake first, with when it wakes and when its event is.
  • Its targets are paused, as for any ticket on hold. Event reminders, auto-assignment and auto-close leave it alone: it isn’t counted in anyone’s load and is never assigned.
  • Its status still reads On hold in its header, with the Parked chip beside it. In the queue its row reads Parked.
  • A saved view on Not solved (parked left out) leaves parked tickets out. Tick Include parked tickets to see them there too; views saved before 1.20.34 keep leaving them out.
  • An agent’s reply, internal note or field change leaves it parked.
  • Reports: Open now and the backlog leave parked tickets out (the backlog for each day a ticket was parked, so past days keep their counts when it wakes), and Open now shows Parked: N beside it. Parked now is a measure of its own.

The ticket goes back to Open, whatever its status was when it was parked (a New ticket wakes as Open), with its targets running again, and its owner (or, with no owner, its team) is told, as for an event reminder. With no owner it goes back to auto-assignment. The timeline says “Woke for the event on Sun 15 Mar”. It also wakes at once when:

  • the requester, or someone copied on the ticket, writes (an updated invite counts only when they wrote something in it, not just the calendar app’s own text);
  • the event is canceled: the timeline says “The event was canceled. Close this ticket if nothing else is needed.”;
  • the event is removed from the ticket;
  • the event moves so close that its wake date has passed;
  • an agent changes the ticket’s status (this ends the parking).

When the event moves further out, or its setup time changes, the wake date moves with it and the timeline says so. The wake date is also worked out again when the ticket moves to another team, when the desk’s prep window changes, and when a team’s working hours or holidays change; one that is now past wakes the ticket within a minute.

If the desk can’t wake a ticket, it tries again after 2, 4, 8 and 16 minutes. After 5 failed attempts it puts the ticket back to Open anyway and the timeline says “Woke without its usual steps after 5 failed attempts (…). Check its targets and its owner.”

Two settings under Holding tickets until the event, both on out of the box:

  • Park tickets from meeting invites until they’re due
  • Park tickets from calendar request types until they’re due

The requester’s acknowledgment goes out first, exactly as before, and any automations for new tickets run. That acknowledgment is the ticket’s first reply before it parks. It is the automatic email, so it doesn’t meet the first reply target: that target pauses while the ticket is parked and runs again when it wakes. Then the ticket parks itself if its wake date is still ahead. If it’s too close, it stays in the queue.

A meeting invite parks its ticket only when its sender passed the sender check or has an account in the workspace, and only for an event within 400 days. A ticket for an event further out stays in the queue, and the timeline says “Not parked: the event is more than 400 days away, so the ticket stays in the queue. Park it by hand if that date is right.” Parking by hand has no such limit. An updated invite keeps it parked and moves the wake date. A canceled one wakes it.

In Get help and the customer portal a parked request shows Scheduled · Sun 15 Mar, 10:00 · Room 4 instead of On hold. Parking and waking send the requester nothing.

Remind the requester before the event (off out of the box) sends them one short email a set number of days before (2 out of the box), with the date, time and place and a link to the request. It goes once per event date, and again if the event moves.

Example: a conference room booking in March

Section titled “Example: a conference room booking in March”

In November, Pat emails a meeting invite for the annual conference to the facilities help address: Sunday 14 March, 10:00, Room 4, with an hour’s setup. Facilities works Monday to Friday and keeps the prep window at 10 working days.

  1. The desk opens ticket #1047, sends Pat the usual “request received” email, and fills in the event. Pat has an account in the workspace, so the invite can park its ticket.
  2. The ticket parks itself until Monday 1 March, ten working days before setup is due at 09:00 on the 14th. Facilities doesn’t see it in All open all winter, and its targets don’t run.
  3. In January Pat moves the conference a week, to Sunday 21 March. The update lands on #1047, the event moves, and the ticket now wakes on Monday 8 March. It stays parked, because Pat’s update carried no message of its own; had Pat written “We need a projector too”, the ticket would have woken so someone could read it.
  4. On 8 March, when the working day starts, #1047 is back in the queue and its owner gets a notice. All along, Pat’s Get help page showed Scheduled · Sun 21 Mar, 10:00 · Room 4.

Calendar in the desk’s side rail shows the events on the tickets you can see.

  • Day, Week and Month, with Today and the arrows to move.
  • Team: all your teams, or one.
  • Color by: Team or Status. Every item also carries its team’s short name or its status in words, so color is never the only clue.
  • Setup time is drawn as a hatched block before the event.
  • Also show: Due dates (reply and resolve targets of open tickets) and Recurring tickets (when each schedule next opens a ticket). They are drawn with a dashed outline.
  • A click, or Enter, opens the ticket.

Your view, team, colors and layers are remembered. On a phone the same days are shown as a list.

Print opens a page made for paper, for the view you are on:

  • Day: a day sheet, one row an event, with a tick box, the time, the place, the owner and when setup must be ready. Made to carry around the building.
  • Week: one column a day.
  • Month: one cell a day.

Nothing of the desk’s menus is printed, and the sheets read well on a black-and-white printer. Use Print or save as PDF.

From 1.20.24 the desk shows what’s coming up without opening the Calendar:

  • The pill in the top bar, next to Claude, shows the next timed event that hasn’t ended in the next 14 days: Now while it’s running, then “2:00 PM”, “Tomorrow 9:00 AM”, “Thu 9:00 AM” or a date. All-day events never show in the pill, and it’s hidden when nothing timed is coming up. On a narrow window it shrinks to the time, then to the icon.
  • Click it for every upcoming event, grouped by day. Each day lists its all-day events first (“Day 2 of 5” on one that spans several days), then timed events in order. “Today: 2 all-day events” shows at the top when there are any. Click an event to open that day in the Calendar (all teams), or Open calendar.
  • The count on the Calendar icon in the left rail is today’s timed events that haven’t ended yet, in your time zone. An event in progress counts; all-day and past events don’t. It drops as each event ends, with no reload, and is hidden at 0.

Both show only events on tickets you can see on the Calendar page: your teams’ tickets and tickets assigned to you. They update with the desk’s live updates and when you come back to the tab.

A feed link lets Outlook, Google Calendar or Apple Calendar show the desk’s events beside your own. Make one from Subscribe on the Calendar page, or in Desk settings → Event calendar.

  • A link is yours. It shows one team’s events, or All my teams.
  • The link is shown once. Copy it then. Only a fingerprint of it is kept; if it is lost, Replace it, which stops the old one.
  • Treat it like a password. Anyone who has the link can read those events without signing in. That is how calendar apps work: they can’t sign in, or answer a two-step sign-in prompt, so the link itself is the key. Revoke it if it may have been shared.
  • A feed lists each event with its ticket number and subject, its place, its setup time and whether setup is complete, and a link to the ticket. It never carries the requester’s name or address, messages or internal notes.
  • It always shows what you could see in the desk right now. Leave a team, or the desk, and its events are gone from the feed.
  • It covers the last 30 days and the year ahead. Calendar apps read a feed every few hours, so a change can take a while to show.
  • Admins see Everyone’s links in the settings page and can revoke any of them. Making, replacing and revoking a link are in the audit log.

The feed is read-only. The desk doesn’t write into anyone’s Outlook or Google calendar.

A ticket’s event is in the REST API and in every webhook delivery as event, and a webhook can listen for event.setup_completed. See API tokens and webhooks.

In the Claude connector, hd_read_ticket returns the event and hd_update_ticket takes event in the same shape, so Claude can add an event, move it or mark its setup complete, within your desk role.

From 1.20.34 a ticket in the REST API also carries parked_until, park_reason (agent, invite or request_type), park_prep_days (the prep window that applies) and park_prep_days_own. event in a PATCH (and in hd_update_ticket) takes park: "park" or park: "wake", and prep_days (0 to 60, or null for the desk’s). Parking needs the permission to change the ticket’s status. If the parking part of a request would be refused (too close, already parked, a prep window out of range), the whole request is refused and nothing in it is saved. hd_read_ticket shows parking, and the desk’s views accept view=parked. Everything here is additive: existing calls and receivers keep working unchanged.

Action What it records
helpdesk.calendar.settings_updated Changed the event calendar settings (which ones)
helpdesk.calendar_feed.created Created a calendar feed link (whose, and for which team; never the link)
helpdesk.calendar_feed.regenerated Replaced a calendar feed link
helpdesk.calendar_feed.revoked Revoked a calendar feed link
helpdesk.ticket.parked Parked a ticket until its event (when it wakes, the prep window, by whom or by itself)
helpdesk.ticket.woke Woke a parked ticket (and why)
helpdesk.ticket.park_changed Changed a ticket’s prep window

Changes to a ticket’s event are on the ticket’s own timeline. Printing the calendar is not recorded.

Nothing to do. The update adds what it needs by itself, and no existing ticket, request type or setting changes. Reminders only start once a ticket has an event.

1.20.34 adds parking. Tickets from new meeting invites and calendar request types park themselves from then on (both settings are on out of the box; turn them off under Holding tickets until the event). Tickets that already have an event in the future are not parked automatically: an agent can park each one from its Event block, and the Parked view then lists them. The requester’s reminder is off until you turn it on.

  • “Before you solve, this ticket needs: the event setup marked complete.” The ticket has an event whose setup isn’t marked. Mark it in the Event block, or remove the event if it no longer applies.
  • An old ticket won’t close. Look under Setup never marked in Desk settings → Event calendar.
  • An invite didn’t fill in the event. The message must carry the invite itself (the part calendars read), not only its text. Forward the invite from the calendar app rather than copying its words.
  • The feed shows nothing in my calendar app. Check that the link was copied whole and hasn’t been replaced or revoked, then wait for the app’s next refresh.
  • “This event is too close to park.” Its wake date is past or less than an hour away. Park it with a shorter prep window (0 waits until setup is due), or leave it in the queue.
  • A parked ticket came back early. The requester or someone copied wrote, the event was canceled, removed or moved closer, the ticket moved to a team with other working days, or someone changed its status. The timeline says which.
  • An invite’s ticket didn’t park itself. The sender didn’t pass the sender check and has no account, the event is more than 400 days away, or it is too close. Park it by hand from its Event block.
  • I didn’t get a reminder. Check Event reminders in your notification settings and your quiet hours, and whether you own the ticket or are in its team.