Personalized Booking Pages

Each host gets a page showing availability for the meeting types offered, so invitees pick a slot without an email exchange. A Beam agent watches for new bookings on that page, reads the invitee's chosen time, meeting type and any notes left, then applies the account's rule for what happens next, such as adding a matching entry in a calendar or CRM. Cancellations and reschedule requests get the same treatment: the agent updates the record and notifies the host. Anything ambiguous, like two bookings in the same slot or a meeting type the rule doesn't cover, gets routed to a person to sort out.

Meeting Type Configuration

Hosts set up separate meeting types, a fifteen minute call, a demo, an onboarding session, each with its own length, questions and availability window. When someone books a specific type, a Beam agent reads which type was chosen along with the answers to any intake questions, then applies the rule tied to that type, for example routing a demo request to the right rep or matching an onboarding booking to a customer record. Straightforward matches update on their own. Bookings that don't fit an existing type, or intake answers needing a judgment call, are flagged for a human to check before the meeting is confirmed.

Booking Notifications and Reminders

DaySchedule can notify hosts and invitees when a meeting is booked, changed or approaching. A Beam agent reads each notification event, matches it against the account's rule for that meeting type or host, and forwards the relevant update, for instance posting a summary to a team channel or updating a shared calendar entry. No-shows and late cancellations get recorded against the booking so hosts have a history. When a notification concerns a repeat cancellation, a VIP invitee or a meeting type marked for manual handling, the agent leaves it for a person to decide what happens next.