Home Event Types

Event Types

Learn how to create and customize Event Types in Schedly. Set durations, availability, reminders, and more to make scheduling fit your exact workflow.
Erik Wetzel
By Erik Wetzel
36 articles

Managed Events

Team admins now have the ability to manage event-types for their members, to facilitate creating common event-types for all members and managing them from one place. A managed event-type comes with certain fields locked by the team admin, and certain fields open to be modified by the team members receiving the managed event. Please take into account that Managed Events v2 do not support Webhooks and Apps. Subsequent releases of this feature will tackle them. Creation Be sure to be a team admin, and in case you are self-hosting, have the `managed-event-types“ operational feature flag turned on. When creating a team event-type, you will be getting the option to create a Managed Event like so: Management Once the managed event-type is created, you will be able to set all the fields you want to manage as a team admin. You can distinguish fields that will be locked by team members by the “lock” icon next to the field label, like so: Assignment A crucial part of a managed event-type is the assignment of team members, so managed event-types can be created on your behalf. Think of the managed-event you created as a team admin as an event template, that team members will get regular event types from it once they are assigned to it. Whenever you make changes to locked fields, every team member will also get the same change on their regular event type created upon this managed event-type. Note that unlocked fields will not have any effect on already created event types for assigned members, only for new assigned members. Take into consideration that whenever you try to assign a managed event-type to a team member that already has an event-type with the same slug, you will get a pop-up message to confirm you want to proceed to delete the existing conflicting event-type from the team member and notify them about this, so the managedm event type can be created in its place. Like so: For which, team members will be notified by email.

Last updated on Aug 27, 2025

Round Robin Scheduling

Round robin event types allow you to distribute meetings amongst team members. At the moment, the distribution is based on availability, optimizing all options regardless of individual load. The booking will be assigned to an available host based on weights, priorities or the person least recently booked. Underlying Mechanism The round robin events when not using a common schedule offer slots which are formed using the union of all slots available for each round robin host. Once an available slot is chosen by the scheduler, the underlying mechanism of host assignment kicks in. The mechanism has a couple of options: Priority Ranking Every round-robin host has a priority, by default ‘medium’. The priority level assigned to a host directly influences their likelihood of being selected for bookings. A higher priority signals a stronger preference, positioning them as a more desirable option for hosting duties. This system ensures that hosts with higher designated priorities are given precedence in the booking process, optimizing the allocation of resources and streamlining event organization.For instance, if John Doe & Jane Doe are both available in the same slot, but John has a priority High compared to Jane’s priority of Medium, John will be booked. If several users have the same priority it will choose the least recently booked user.You have the option to select priority for each host and based on their priority (and availability in the selected slot), the hosts will be booked. Weights Weights are optional and must be enabled to use. They allow you to determine how meetings should be distributed among hosts. When enabled, every host has a default weight of 100%. This means each host should end up with the same number of bookings by default. However, hosts with fewer availabilities can still end up with fewer bookings. Only confirmed bookings count towards past bookings.For instance, Jane Doe has a weight of 100% and already has 8 bookings while John Doe has a weight of 200% and already has 12 bookings. Assuming both of them are available, the next bookings would go to John Doe until a total of 16 bookings is reached. Weight Adjustment: If new hosts are added to a round-robin event type that has weights enabled, their weights will be adjusted accordingly. New hosts will have their bookings adjusted proportionally to their weight, taking into account the bookings that existing hosts already have. This ensures a fair distribution of bookings when new hosts are added. Example: Existing host 1: 100% weight, 5 bookings Existing host 2: 200% weight, 9 bookings New host: 50% weight Weight Adjustment = (Bookings of existing hosts / Sum of weights of existing hosts) * New host weight Weight Adjustment = 14 / 300 * 50 = 2.33 The new host will have a weight adjustment of 2 bookings. Least Recently Booked This is the fallback method where the available round robin host who was booked least recently is chosen. If more than one host meets this criteria, one of them is chosen at random. Round-Robin Groups With Round-Robin Groups, you can utilize round-robin scheduling even further by organizing hosts into separate groups and having one host from each group join the booking. This is useful for scenarios where you need multiple participants from different roles or departments to be part of the same event — for example, a sales representative and a solutions engineer, or a recruiter and a hiring manager. How It Works: Without Round-Robin Groups: Only one host from the Round-Robin pool will be selected for the booking. - With Round-Robin Groups: - You can create multiple Round-Robin groups, each with its own assigned hosts. - For each booking, one host from every group will be selected. - Within each group, our regular Round-Robin algorithm determines which host is booked next. - This ensures fair distribution of bookings for all hosts within their group. You can set it up by clicking on Add Group button next to the Round-Robin hosts setup shown in the screenshot below. Make sure you save your changes once done. BrandBird 2025-08-14 07.47.56.png Fixed Hosts If you wish to bring in Collective behavior into round-robin events, it is possible with Schedly. You can now select which hosts you wish to always attend the meeting, whilst the other selected team members who are booked on a round-robin basis. Fixed Hosts are individuals who are consistently present at every meeting. Round-Robin Hosts are members of a group who take turns attending meetings. Rather than everyone in this group attending every meeting, only one person from the group will attend each time.For tasks like scheduling sales calls or product demos, where you have a pool of people among whom you’d like to distribute meetings, round robin is the perfect choice.

Last updated on Aug 27, 2025

Event Type Slot Display Issues

When encountering discrepancies in slot availability on the Schedly event type/booking page, follow these steps to troubleshoot and resolve the problem: If Booking Slots Are Available When You Are Unavailable: Check Connected Calendar - Review your connected calendar for events marked as “free” instead of “busy,” particularly all-day events such as vacations or out-of-office days. Some calendar providers, like Google Calendar, default to marking such events as free. - Navigate to your Schedly settings under “Settings” > “Calendars” and ensure that the calendar containing busy events is toggled to be checked by Schedly for conflicts. Verify Date Overrides - If you’ve set up date overrides in the availability settings, ensure they are configured correctly. Date overrides may override your availability for specific time periods. If Booking Slots Are Unavailable When You Are Available: Review Connected Calendar - Check your connected calendar to confirm that events marked as free are indeed marked as busy during your desired booking times. Adjust Time Intervals - Verify the time intervals set for your event type. If your availability starts or ends at non-standard intervals (e.g., 8:15 - 11:30), adjust the time intervals accordingly. By default, Schedly displays slots starting on the hour only. Increasing intervals to 30 or 15-minute increments will display additional slots. Check Buffer Times - Review buffer times applied before or after meetings. Buffers subtract time before or after a meeting, potentially affecting slot availability. Verify Booking Frequency Limit - Ensure that the booking frequency limit is set appropriately. Adjust settings accordingly if there are restrictions on how frequently bookings can be made. - Review the “Limit Future Bookings” setting to ensure it aligns with your availability preferences. Adjust this setting if necessary to allow for future bookings. By following these steps and checking each aspect meticulously, you should be able to effectively identify and resolve issues with slot availability on the Schedly event type/booking page. If the problem persists, don’t hesitate to contact Schedly support for further assistance.

Last updated on Aug 28, 2025

Event Buffer

Event buffers are time spaces that can be appended before and/or after an event. This is helpful in scheduling your availability such that you have time to prepare for a meeting, take a breather between two meetings/events, or to accommodate travel time in case of events on a physical location. You can customize buffer time for each event so that you can accommodate the needs of that specific event type to further optimize your event type setup. The before event buffer time allows the space of time of chosen length before the events being booked on Schedly based on your availability. The after event buffer time allows the space of time of chosen length after the events being booked on Schedly based on your availability. Hidden events are flexible; they can be whatever you need them to be. Whether you want to use hidden events to facilitate sponsorship meetings, organize a fundraising drive, or offer one-on-one mentoring sessions, this feature can help you make the most of your meetings while keeping them out of the public eye. Event buffers are a great way to maintain a breathing space between multiple events in a day. Buffers are taken into consideration while booking a Schedly event, if that Schedly event has a buffer time selected. This simply means that buffers cannot overlap Schedly events and thus a Schedly event with buffer time can only be booked respecting the buffer time (before event, after event or both). An Example Given the availability from 9am to 5pm (09:00-17:00) and a 60-minute event with a 30-minute buffer before and a 30-minute buffer after, the total calendar time required for an event is indeed 120 minutes. But the buffer is applied around busy times and not to the start or end of the working day. So, in this scenario (considering you didn’t modify the Custom time slot intervals in this example): 1. The first available time slot starts at 9am. The buffer before doesn’t push this since there’s no preceding busy time. 2. The event itself is for 60 minutes. 3. There’s a 30-minute buffer before & 30-minute buffer after the event. But again, if there’s no following busy time immediately after, this buffer doesn’t push the next available slot. Thus, the sequence is: - 9:00-10:00am: First available slot - 10:00-11:00am: If Slot 1 is booked, this slot will be blocked as buffer (after) to allow the buffer period relative to the 9-10am slot. - 10:00-11:00am: If Slot 1 is free, this slot will be free. - 10:00-11:00am: If Slot 2 (10:00-11:00) is booked, since booking slot 1 (9:00-10:00) would imply that there will not be an after buffer (as 10-11 is already booked). Hence, slot 1 will not remain bookable anymore.

Last updated on Aug 28, 2025

Private Links

Private Links let you control access to your event types in a secure and flexible way. They are ideal for invite-only sessions, VIP access, pilot programs, or scenarios where you want to limit visibility and usage. Unlike standard public links, Private Links are not discoverable on your public booking page — and can be configured with advanced expiration rules. Key Features - Multiple Private Links per Event Type You can create several private links for the same event type — each with its own unique usage rules. - Usage-Based Expiry Set a private link to automatically expire after it has been used a specific number of times. Example: expires after 2 successful bookings. - Date-Based Expiry Set a specific expiry date after which the link will no longer be usable. Example: valid until August 31, 2025. - Non-Guessable, Secure URLs Each private link is generated as a secure, hash-based URL that cannot be guessed or found publicly. - Granular Control via Event Type Settings All private links are managed per event type under the Advanced tab of the event type settings. How to Use Private Links 1. Open an Event Type Go to the Event Types section in your dashboard and select the one you want to configure. 2. Go to the Advanced Tab Inside the event type settings, switch to the Advanced tab. 3. Create a Private Link - Toggle Private Link if it isn’t already - Click Add Private Link to add more links - Click on the settings (gear) icon in front of the private link and define: - Number of allowed uses, or - Expiry date - Save the private link configuration - Save the event Type settings to be able to use the link 4. Share the Link Securely Copy and share the generated link only with the intended invitees. ​What to Expect - If a private link has usage limit, it will expire after the set number of bookings are made using the link. - If a private link has date limit, it will expire after the set date. - Once expired, the link will: - No longer be accessible - Show 404 error page if opened - Private links do not appear on your main booking page or directory - You can delete any private link at any time from the same event type settings - You can configure any active private links from the same event type settings

Last updated on Aug 28, 2025

Booking Success Redirect Parameters

Complete reference guide for query parameters forwarded to custom success pages after successful bookings When a booking is successfully created in Schedly, users can be redirected to a custom success page by enabling ‘Redirect to a custom URL after a successful booking’ option in the Event Type’s Advanced settings page. This guide documents all the query parameters that are forwarded to your custom success URL when ‘Forward parameters’ option is enabled (which is the default). Overview Schedly automatically appends booking information as query parameters to your custom success redirect URL. These parameters allow you to display booking details, or integrate with your own systems. Example redirect URL: https://yoursite.com/booking-success?uid=abc123&title=30min%20Meeting&startTime=2024-01-15T14%3A00%3A00.000Z&attendeeName=John%20Doe&email=john%40example.com Quick Reference Core Booking Parametersuid - Unique identifier for the booking - Always included - Example: 9ybDCbazSYpJHthpxG5EDM - Usage: Use this to fetch additional booking details via API or store in your database title - The event type title - Always included - Example: 30 Minute Meeting description - Event type description - Included when event has description - Example: Quick sync meeting to discuss project updates startTime - ISO 8601 formatted start time in UTC - Always included - Example: 2024-01-15T14:00:00.000Z endTime - ISO 8601 formatted end time in UTC - Always included - Example: 2024-01-15T14:30:00.000Z location - Meeting location or video conference URL - Included when location is set - Example: integrations:daily (Cal Video), integrations:zoom (Zoom). Host/Organizer ParametershostName - Host name(s), comma-separated for multiple hosts - Included when host information available - Example: Jane Smith,Mike Johnson hostStartTime - Start time formatted in host’s timezone - Included when host timezone available - Example: 2024-01-15T09:00:00-05:00 Attendee ParametersattendeeName - Name of the person who booked - Included when primary attendee name available - Example: John Doe attendeeStartTime - Start time in attendee’s timezone - Included when attendee timezone available - Example: 2024-01-15T06:00:00-08:00 attendeeFirstName - First name from booking form - Included when first name provided in booking form - Example: John attendeeLastName - Last name from booking form - Included when last name provided in booking form - Example: Doe guestEmails - Comma-separated list of guest emails - Included when additional guests added - Example: guest1@example.com, guest2@example.com Booking Context Parametersemail - Primary attendee’s email address - Always included - Example: john@example.com phone - Phone number from booking form - Included when phone number provided - Example: +1234567890 System Context ParametersisEmbed - Boolean flag indicating if booking was made via embed - Always included - Example: false Troubleshooting Common Issues Missing Parameters - Some parameters are only included when data is available URL Encoding Issues - Always use decodeURIComponent() in JavaScript or equivalent in other languages - Special characters like @, +, spaces are URL encoded Date/Time Handling - startTime and endTime are always in UTC (ISO 8601 format) - hostStartTime and attendeeStartTime include timezone information - Convert to local time as needed for display Security Considerations - Always validate and sanitize parameters before using in database queries - Don’t trust parameter values - validate against your expected data types

Last updated on Aug 28, 2025