> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/scheduling/create-booking-links.md). # Booking links Create booking links for yourself or a group, take Zendesk meeting requests, brand the booking page and manage bookings. A booking link is a meeting customers can book. It sets the length, the hours, who hosts and the emails guests get. Find them in **Bookings → Booking links**. {% embed url="" %} Members create links they host themselves. Admins can also create links for other members, for groups and for Zendesk requests. ## Create a booking link Click **New booking link**. The form has four sections: * **Basics**: title, URL, description, **Booking flow**, **Host** and **Duration** (15, 20, 30, 45, 60 or 90 minutes). The meeting always takes place in a Screendesk room. * **Availability**: **Hours**, which are the host's own hours (or the group's, for a group link) or a shared [schedule](/scheduling/connect-your-calendar.md), and **Start time intervals** (15, 30 or 60 minutes). Times when the host is busy on their calendar are never offered. * **Booking limits**: **Minimum notice**, **Booking horizon**, and buffer time **Before the event** and **After the event**. * **Notifications**: the confirmation email, **Send a reminder email** and its timing, and the calendar invite. **Send test email** sends you a preview. The **Booking flow** is either **Instant confirmation**, booked straight away with a member or a group, or **Zendesk request** (see below). Emails and the calendar invite can use `{{event_name}}`, `{{guest_name}}`, `{{guest_email}}`, `{{host_name}}`, `{{date}}`, `{{start_time}}`, `{{end_time}}`, `{{time_zone}}`, `{{meeting_link}}`, `{{manage_link}}` and `{{notes}}`. Admins also see **Available to**, which sets who can find and share the link in Screendesk and Zendesk: **Host / booking group members**, **Selected users** or **Everyone in the workspace**. It doesn't change who hosts. {% hint style="info" %} Changes to a link apply to new bookings. Existing bookings keep their time, host and messages: change those from the booking itself. {% endhint %} ## Share a link Click **Copy booking link** in the list and paste it into an email or reply. The Screendesk app in your helpdesk lists the links available to you, so you can insert one into a reply. **Pause** stops new bookings and **Activate** takes them again. **Archive** keeps a link you no longer use. None of these cancel existing bookings. **Delete** stops the link for good. The list flags a link that can't take bookings, for example **Your calendar needs setup** (with **Fix calendar**), **No eligible hosts in this group** or **Zendesk needs to be reconnected**. ## Group links A group lets customers book whichever member of a team is free, from one link. Only admins manage groups. 1. Go to **Bookings → Groups** and click **New group**. 2. Enter a **Group name** and choose a **Routing strategy**. 3. Under **Members**, add who can host and use the arrows to set the queue order. 4. Under **Hours**, set when the group can be booked. 5. Click **Create group**, then create a booking link with the group as its **Host**. | Routing strategy | Times offered | Who hosts | | ------------------------- | ---------------------------- | ------------------------------------ | | **Round robin** | The next member's free times | That member. The queue then rotates. | | **Maximize availability** | Every member's free times | The first free member in queue order | Each member connects their own calendar. Members whose calendar needs setup are skipped, so fewer times show. Group links use the group's hours, not each member's own hours, but a member is never booked while their calendar shows them busy. ## Zendesk meeting requests With the **Zendesk request** booking flow, customers propose a time and Screendesk creates a Zendesk ticket. A member then claims it. Nothing is confirmed, and no host is reserved, until someone claims it. An admin sets it up: 1. Connect Zendesk in **Settings → Integrations**. A request link can't be activated without it. 2. Create a booking link with **Zendesk request** as its **Booking flow**. 3. Under **Availability**, set the time zone, the weekly hours customers can request, and any date overrides. To take a request, open the claim link from the Zendesk ticket, or **Bookings → All bookings → Requests** and click **Review request**. Click **Claim meeting**. Your calendar must be connected (**Configure calendar**) and free at that time, and it's checked again when you claim. Only one person can claim a request. Use **Decline request** if the team can't take it. Until it's claimed, the customer can **Choose a different time** or **Withdraw request**. An unclaimed request expires when its start time passes. If the ticket couldn't be created, fix the Zendesk connection and click **Retry Zendesk delivery**. ## Booking page Admins brand the page customers book on in **Settings → Booking page**:
Settings, Booking page
* **Logo**: shown at the top of the scheduler. PNG or JPEG, up to 5 MB. A wide logo works best. * **Accent color**: used on the picked date and time and on the booking buttons. Both apply to every booking link in the workspace. ## Manage bookings **Bookings → All bookings** lists bookings by **Upcoming**, **Past** and **Cancelled**, and Zendesk **Requests**. Click **Join meeting** to join the meeting, or open a booking to see its time, host, notes and **Delivery activity**. From there you can: * **Copy meeting link** * **Reschedule booking** or **Cancel event**: admins, or the host of a link they own * **Reassign host**: admins or the assigned host. The new host's calendar is checked first. * **Add guests**, up to 30: admins or the assigned host **Delivery activity** shows whether the meeting room, the calendar event and the emails went through. If one failed, fix the cause (often a calendar that needs reconnecting) and click **Retry**. Customers can **Reschedule** or **Cancel event** from the link in their confirmation email. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.screendesk.io/scheduling/create-booking-links.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.