Coordination in chat
One person suggests a day, another checks a calendar, and someone forgets the time zone. An open window needs manual confirmation.
PUBLIC BOOKINGEurope/Moscow
MONTUEWEDTHUFRI
15Wednesday
10:0011:3014:00
Calendly-style booking
The guest chooses a slot. The team gets a booking.
The team sets the meeting type and availability rules; the guest chooses a time in their time zone. After submission, the guest gets a booking status and the team gets a booking record; if the type requires confirmation, the organizer confirms it separately.
IntroductionA short first conversation to understand the task and next step.
Submit details and create a bookingAfter submitting details, the guest sees the booking status and the organizer gets a booking to confirm or run.
After confirmation, the booking becomes an eventThe created booking stores the selected type, time, and participants. If confirmation is required, it becomes a calendar event after confirmation.
Grew from Calendly
Slot booking inside the working context
We took Calendly's simple path—meeting type, availability, and slot selection—and added team rules, time zones, external calendars, formats, and a working booking record with the right status.
Source model
Calendly
SHD version
Meetings
From Calendly to the working context
A person chooses the time; the team keeps the context
Calendly's simple path removes slot negotiation. SHD adds team rules, time zones, external calendars, formats, and confirmation.
The scenario is ready
The guest sees the right meeting type, chooses an available time, and creates a booking. If the type requires confirmation, the team confirms it separately.
Type, availability, and confirmation are one path
Meeting type
Purpose first, time second
A meeting type tells the guest why to come, how long it will take, and what format to expect.
01
Introduction
A short first conversation to understand the task and next step.
02
Project review
Time for inputs, materials, and questions about a specific object.
03
Technical session
A meeting for engineers, integrations, and checking working solutions.
04
Site visit
A slot with a clear format and place, not an abstract call.
05
Follow-up call
A short return to the agreements after a work stage.
Each type defines its own duration, format, and availability rules.
Guest path
Three steps to a meeting booking
The public link opens a specific scenario. The guest sees only the information needed to choose a time and create a booking.
- 01
Open the link
The meeting name explains what to prepare and how much time to allow.
- 02
Choose a day and slot
The guest chooses a day and an available slot with the rules and time zone applied.
- 03
Submit details and create a booking
After submitting details, the guest sees the booking status and the organizer gets a booking to confirm or run.
The public link shows availability but does not expose the team's personal calendar.
Calendars and availability
Availability is not a personal calendar
Guests see only selectable intervals. The team keeps bookings and events separately without exposing personal calendar details.
The team sees occupied intervals
Availability rules remove overlaps and leave the guest only real windows.
After confirmation, the booking becomes an event
The created booking stores the selected type, time, and participants. If confirmation is required, it becomes a calendar event after confirmation.
After confirmation, the event calendar stores the meeting; availability answers what can be chosen.
Formats
Format belongs to the booking
The guest knows the duration, channel, and conditions in advance. Fewer details need clarification after booking.
30, 60, or another predefined length.
Online, offline, or an address that must not get lost in chat.
After the slot
Each side gets its own result
The guest gets a booking status and the organizer gets a booking in the working context. If the type requires confirmation, the status remains pending until the organizer decides.
Guest
Gets the booking details
The date, time, format, and next step remain with the person after selection.
Organizer
Sees the booking in context
The team knows who is coming, for which type, and when to be available.
Booking connects the record to the working context; the work itself stays in the project modules.
Before booking
The boundaries in brief
The module handles meeting type, availability, and booking. Project content stays in its working modules.
Is this a shared calendar of open windows?
No. First create a meeting type with duration and rules, then show its availability.
Does the guest see the team's personal calendar?
No. Only the available slot and the data needed for booking are shown outside.
Can we offer several meeting types?
Yes. Each type has its own duration, format, and availability.
What if a slot has already been taken?
The slot is checked again when the booking is created. If it is no longer available, the booking is not created.
Can people book in different time zones?
Yes. Time is shown according to the selected meeting time zone.
Is this just Calendly?
The booking path is similar to Calendly, but SHD keeps it next to calendars, notifications, and the rest of the working modules. Meeting context stays in project records and discussions.
Meeting context
Turn an open slot into a meeting booking.
We will review meeting types, availability rules, channels, and what the guest should receive after booking.
We will start with the current messages and find meetings that can become a clear booking flow.