Qué construimos después.
Proponé ideas, votá las que necesitás y seguí su estado. Lo más votado sube en la lista.
Cal: Sell meeting packages that bundle several sessions into one payment
Calendly added Meeting Packages and Payment Links in beta as part of its commerce tools (https://community.calendly.com/featured-tips-tricks-32/change-log-march-13-2026-5463). We charge per event type through Stripe (lib/calendar-payments.ts) and each booking is paid on its own. Coaches and consultants who sell five sessions at a price cannot do it without a manual invoice. First scope: a package with a session count and price, a payment link, and a credit counter that is spent as the invitee books each session. Priority: medium. Effort: M.
Cal: Challenge suspicious public bookings with a captcha
Calendly shows invitees a Captcha when a booking attempt looks suspicious (https://community.calendly.com/featured-tips-tricks-32/change-log-march-13-2026-5463). Our public booking endpoint at app/api/calendar/bookings/route.ts has a rate limit but no bot challenge, so a team that shares its page widely can get junk bookings that hold real slots and trigger emails. First scope: a workspace toggle that adds a lightweight proof-of-work or Turnstile challenge to the booking form after repeated attempts from one IP, and logs the blocked attempts in settings. Priority: medium. Effort: M.
Cal: Add a custom confirmation message with links to the booking confirmation
Calendly lets the host add instructions to the confirmation page and the confirmation email (https://calendly.com/help/how-to-customize-your-confirmation-page). We have welcomeMessage for the booking form and a redirect URL, but nothing that appears in the confirmation screen or the email, so a host cannot say 'bring your ID' or 'here is the prep doc' without a redirect. First scope: a short message per event type with plain links, shown after booking, in the email and in the manage page.
Cal: Duplicate an event type with its schedule, questions and workflow steps
Calendly has Clone on every event type in the list (https://calendly.com/help/event-types-overview), which is how people create the 15, 30 and 60 minute variants. In components/calendar/EventTypesView.tsx an event type can be opened, renamed and deleted, but the only way to get a variant is to fill the editor again, including questions and locations. First scope: a Duplicate action that copies the rules, fields, locations, schedule and workflow steps with a new slug and a Copy suffix in the title, and opens the editor.
Cal: Limit each invitee to one upcoming booking per event type
Calendly and Cal.com can limit how many future bookings the same email can hold for an event type (https://calendly.com/help/how-to-set-meeting-limits). Our meeting limits in lib/calendar-limits.ts count bookings per host and per period but not per invitee, so one person can hold every Tuesday slot. Free consultations and office hours need this to stay fair. First scope: a maxUpcomingPerInvitee rule checked at booking time, with a clear message that links to the existing booking's manage page.
Cal: Add a fixed booking date range to an event type
Calendly offers a rolling window or a fixed from/to range in Availability (https://calendly.com/help/how-to-fine-tune-your-availability-settings). Today lib/calendar.ts only supports maxFutureDays counted from today, so a workshop week or a launch campaign cannot open on a given date and close on another. This matters for recruiting weeks, office hours during an event and seasonal offers. First scope: optional startDate and endDate in the booking rules, applied in the slots engine and shown in the editor.
Cal: Show a cancellation policy on the booking page and in the confirmation email
Calendly lets you write a cancellation policy that invitees see before and after booking (https://calendly.com/help/how-to-add-a-cancellation-policy). We have a welcome message on the event type (components/calendar/PublicBookingPage.tsx) but no field that travels to the confirmation email and the manage page. Invitees at small teams often ask the same question about late changes. First scope: a policy text per event type in the three languages of the host's choice, shown on the booking form, the confirmation and the manage page.
- 0
Cal: Close cancel and reschedule from the invitee link N hours before the start
Calendly only shows a cancellation policy to invitees and does not enforce it (https://calendly.com/help/how-to-add-a-cancellation-policy), and Cal.com added a minimum notice to reschedule. Before this, the manage page in components/calendar/ManageBooking.tsx let a guest cancel or move a booking minutes before it started. A small team that blocks the calendar for a meeting needs a way to say changes close 24 hours before. First scope: a changeCutoffHours rule per event type, enforced in the manage route, with the buttons replaced by a notice. The host can still change the booking from the app.
- 0
Cal: Summarize meetings into the CRM with a notetaker
Calendly launched Notetaker in August 2026: it joins Zoom, Meet and Teams, records, and produces recaps, action items and follow-up email drafts (https://calendly.com/newsroom/press-release/calendly-new-ai-product-suite). Bookings already create a CRM contact and meeting in our suite. Scope: start with notes the host pastes or a transcript upload, summarized by AI into the CRM meeting with action items as CRM tasks; a recording bot can come later. Priority: low. Effort: L. Compared with Calendly.
- 0
Cal: Allow hidden event types that do not show on the public profile
Calendly lets an event type stay bookable by its link without being listed on the profile page. Our profile (lib/calendar.ts) lists every active event type that is not single-use, so a team cannot keep an internal or VIP link off the public page without making it single-use. Scope: a 'Show on profile' toggle per event type, respected by the profile page and the embed picker. Priority: low. Effort: S. Compared with Calendly.
- 0
Cal: Add meeting polls so invitees vote on proposed times
Calendly meeting polls let a host propose several times and invitees vote before one is booked (https://calendly.com/pricing, Standard and up). We have one-off meetings with hand-picked times, but only one person books and there is no voting. Scope: a poll type built on one-off times where several invitees mark the times that work, the host sees the tally and confirms one, and the confirmation goes to all voters with .ics. Priority: medium. Effort: M. Compared with Calendly.
Cal: Add managed event types and a public team booking page
Calendly Teams has managed event types that admins lock and push to members (https://calendly.com/pricing) and Cal.com Teams includes managed event types and team pages (https://cal.com/pricing). We have host pools per event type but every public page is per person (/book/<handle>) and there is no template an admin can enforce. Scope: a team handle page listing team event types, and managed event types whose locked fields (duration, questions, workflows) propagate to each member's copy. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Export bookings and analytics to CSV and filter analytics by host
Calendly analytics filter by user, team or group and export event or user data to CSV, and the Meetings export includes UTM and payment fields (https://calendly.com/help/calendly-analytics, https://calendly.com/help/tracking-and-reporting). Our Cal analytics and Bookings pages have no export and no host filter. Scope: CSV download from Bookings (current filters applied, with answers, UTM, payment and status) and from Analytics, plus a host selector on Analytics for team workspaces. Priority: medium. Effort: S. Compared with Calendly.
- 0
Cal: Let workspaces hide 'Powered by zerosoft' and serve booking pages on their own domain
Calendly lets owners remove the Calendly branding from booking pages (https://calendly.com/help/account-settings-overview) and Cal.com Teams includes branding removal (https://cal.com/pricing). Our ChromeGate always renders the powered-by line on /book pages, and booking pages only live on our domain. Link already verifies custom domains (lib/link-domains.ts). Scope: a workspace setting to hide the footer, and serving /book/<handle> on a verified custom domain reusing the Link domain verification. Priority: medium. Effort: S. Compared with Calendly.
- 0
Cal: Trigger workflows on booked, cancelled and rescheduled, with a webhook step
Calendly and Cal.com workflows fire on new booking, cancellation and reschedule, not only relative to the start time (https://cal.com/docs/enterprise-features/workflows, https://calendly.com/learn/calendly-workflows). Our workflow steps are only 'X minutes before or after the start'. Scope: add a trigger field (booked, cancelled, rescheduled, before start, after end) and a webhook action that posts the booking payload from lib/calendar-lifecycle.ts, keeping the claimed-run pattern in calendar_workflow_runs. Priority: medium. Effort: S. Compared with Calendly and Cal.com.
- 0
Cal: Send SMS and WhatsApp reminders from workflows
Calendly workflows send SMS reminders and follow-ups on paid plans (https://calendly.com/blog/workflows) and Cal.com markets SMS and WhatsApp actions (https://cal.com/docs/enterprise-features/workflows). Our lib/calendar-workflows.ts only has email steps to guest or host. In LatAm services (clinics, salons, classes) WhatsApp is what cuts no-shows. Scope: a channel field per step (email, SMS, WhatsApp), a phone question mapped as the destination, Twilio or WhatsApp Cloud API credentials per workspace (encrypted like the Stripe key), same variables and cron dispatch, and opt-out handling. Priority: high. Effort: M. Compared with Calendly.
- 0
Cal: Import event types, schedules and questions from Calendly
Cal.com offers a one-click Calendly import on its free plan (https://cal.com/pricing). We have no import in Cal, so a team switching from Calendly recreates every event type, availability schedule, custom question and routing form by hand. Scope: paste a Calendly personal access token (API v2), list event types and availability schedules, map duration, locations, questions, buffers and limits to our schema, preview and import; upcoming scheduled events optionally imported as bookings so slots stay blocked. Priority: high. Effort: M. Compared with Calendly and Cal.com.
- 0
Cal: Create a unique Zoom or Teams meeting for every booking
Calendly connects Zoom and Microsoft Teams so each booking gets its own meeting link generated by the provider (https://calendly.com/pricing, conferencing on all plans). Our lib/calendar-locations.ts treats zoom and teams as a fixed URL per host or per option, so every guest reuses the same room and recordings and waiting rooms mix meetings. Scope: OAuth connections for Zoom and Microsoft (Graph onlineMeetings) in Cal settings, create the meeting on confirm, update it on reschedule and delete it on cancel, with the same best-effort pattern as the Google Meet path; keep the fixed link as fallback. Priority: high. Effort: M. Compared with Calendly.
- 0
Cal: Distribute round-robin bookings fairly and expose a no-show webhook event
Calendly round robin can optimize for availability or for equal distribution, and its API emits invitee_no_show.created webhooks (https://calendly.com/help/how-to-use-buffers mentions distribution effects; https://learn.microsoft.com/en-us/connectors/calendlyv2). In lib/calendar.ts createBooking increments rr_cursor by one whatever host pickFreeHost chose, so when the cursor host is busy the next host gets two bookings in a row and the skipped one loses its turn. Separately, the v1 no-show endpoint (app/api/v1/calendar/bookings/[id]/no-show/route.ts) never calls emitEvent, so webhooks and Flow cannot react to no-shows. First scope: set the cursor to the index after the host actually picked (or pick the least recently booked free host), and emit booking.no_show from both the admin and v1 paths. Priority: low. Effort: S. Compared with Calendly.
- 0
Cal: Support group events with seats so several invitees can book one slot
Calendly Group event types let one host meet multiple invitees per slot (webinars, classes, tours), and Cal.com offers seats with capacity (https://calendly.com/help/event-types-overview, https://cal.com/blog/discover-cal-com-s-advanced-settings). Our booking INSERT in lib/calendar.ts rejects any overlap for the host and there is a unique index on host and start, so a slot holds exactly one booking. Trainers, onboarding sessions and office hours need this weekly. First scope: seats per event type, count bookings per slot instead of rejecting overlap, show remaining seats on the booking page, and one shared Google event with attendees added. Priority: low. Effort: L. Compared with Calendly.
- 0
Cal: Add an optional host approval step (requires confirmation) for bookings
Cal.com event types can require the host to accept each booking, always or only when booked within a notice window (https://cal.com/help/event-types/how-to-requires). Our bookings are confirmed instantly; the only pending state is the Stripe hold in lib/calendar.ts createBooking. Consultants, agencies and clinics want to screen requests before committing the slot. First scope: a requiresConfirmation flag that creates a pending booking holding the slot, host emails with Accept/Decline links and an admin action in BookingsList, guest notified either way, and a booking.requested webhook. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Let routing forms end in a URL or message, log submissions and pass answers on
Calendly routing forms can send respondents to an event type, a custom message or an external URL, and emit routing_form_submission.created webhooks (https://community.calendly.com/featured-tips-tricks-32/12-days-of-calendly-day-10-routing-for-teams-527, https://learn.microsoft.com/en-us/connectors/calendlyv2). Our evaluateRouting in lib/calendar-routing.ts can only return an event type slug, rules have a single condition, submissions are not stored, and only name and email reach the booking (components/calendar/PublicRoutingForm.tsx). Disqualified leads hit a dead end and the host never sees the qualification answers. First scope: destination types (event, url, message), a submissions table visible in the form editor, carry all answers into booking answers, and a routing.submitted event for webhooks and Flow. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Ship a booking analytics view with created, cancelled, no-show and popular times
Calendly Analytics shows created, completed, rescheduled and canceled events, popular event types and popular times for up to a year, filterable by user and event type, on Standard and up (https://calendly.com/help/calendly-analytics). Our Cal overview (app/[locale]/app/calendar/page.tsx) only shows an upcoming-7-days count and the next five bookings. Without trends a small team cannot see no-show rate, which rep gets demos, or which hours to open. First scope: a stats tab over calendar_bookings for a date range with counts by status, by event type and host, cancellation and no-show rates, and a weekday by hour heatmap. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Add one-off meetings that offer hand-picked times outside normal availability
Calendly one-off meetings let the host pick specific slots on a calendar, including over non-Calendly events or outside working hours, then share a link or paste the times into an email; Meeting Polls extend this with voting (https://help.calendly.com/hc/en-us/articles/4406031977623, https://help.calendly.com/hc/en-us/articles/4411543910551). We have single-use links (singleUse in lib/calendar.ts) but they still use the event's regular schedule, so a host cannot offer 'Tuesday 18:00 or Thursday 8:00' to one VIP. This is one of the most common daily actions for sellers and founders. First scope: a 'Share specific times' dialog that creates a hidden single-use event type with explicit slot overrides and a copy-as-text option; polls can follow later. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Redirect invitees after booking and capture UTM parameters on the booking
Calendly can redirect to an external URL after booking and optionally append event name, invitee name, email and UTM tags, available from Standard (https://calendly.com/help/how-to-redirect-invitees-to-another-site-after-booking). Our booking page only redirects to Stripe Checkout (components/calendar/PublicBookingPage.tsx) and the page route reads just name and email from the query (app/[locale]/book/[handle]/[slug]/page.tsx); bookings store no source or UTM. Marketers cannot fire a thank-you page conversion pixel or attribute demos to campaigns, which also weakens the CRM sync. First scope: per-event redirectUrl with a 'pass details' toggle, persist utm_* and referrer on calendar_bookings, and include them in webhooks and the CRM activity. Priority: medium. Effort: S. Compared with Calendly.
- 0
Cal: Create collective event types where every selected host must be free
Calendly Collective events let several teammates meet one invitee and only show times when all hosts are available, and shared collective events are on Standard (https://calendly.com/help/how-to-set-up-a-shared-collective-event-type). We only have round-robin: candidateHosts and busyForHosts in lib/calendar.ts accept a slot if at least one host is free. Small teams constantly need 'founder plus engineer' demos or 'two partners' consults. First scope: add a hostMode (round_robin | collective) on the event type, intersect free time across hosts in slotsForDay, book all hosts in one transaction, and add every host as an attendee on the Google event. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Add daily, weekly and monthly meeting limits per event type and per host
Calendly lets an event type cap bookings per day, week or month, and also caps total meetings across all event types; whichever limit hits first removes availability (https://calendly.com/help/how-to-set-meeting-limits). Our bookingRules in lib/calendar-schema.ts only have buffers, notice and horizon, and loadSlotContext in lib/calendar.ts has no count check. Founders and solo sellers use limits to protect focus time, for example at most 3 demos a day. First scope: add maxPerDay and maxPerWeek to bookingRules, count confirmed and pending bookings per host in the slot engine, and enforce it again inside the booking INSERT. Priority: medium. Effort: M. Compared with Calendly.
- 0
Cal: Add dropdown, radio, checkbox, multi-line and phone questions, plus invitee guests
Calendly invitee questions support one line, multiple lines, radio buttons, checkboxes, dropdown and phone number, and invitees can add guests to the meeting (https://help.calendly.com/hc/en-us/articles/226893168, https://help.calendly.com/hc/en-us/articles/226766767). Our customField in lib/calendar-schema.ts only allows text, number and boolean, and bookingRules.allowGuests exists in the schema but nothing in the editor, booking page or emails uses it. Qualification questions like company size or budget become free text that cannot be filtered or routed, and the guest's colleague never gets the invite. First scope: add select/radio/checkbox/textarea/phone types with options, add a guests field (up to 10 emails) gated by allowGuests, and send them the .ics and Google attendee entry. Priority: high. Effort: M. Compared with Calendly.
- 0
Cal: Offer structured locations (Zoom, Teams, phone, in person) with invitee choice
Calendly has native Zoom and Microsoft Teams location types that generate a unique link per booking, plus phone call and in-person locations, and an event can offer several for the invitee to choose (https://help.calendly.com/hc/en-us/articles/223195508). Our location is a single free-text field (components/calendar/EventTypeEditor.tsx) and the only automation is wantsGoogleMeet() sniffing that text in lib/google-calendar.ts. Teams that sell on Zoom or Teams paste a static room link, and phone-call meetings cannot ask the guest for their number. First scope: replace location with a typed list (google_meet, zoom, teams, phone_host, phone_guest, in_person, custom link), let the guest pick when there are several, and add Zoom OAuth meeting creation first. Priority: high. Effort: M. Compared with Calendly.
- 0
Cal: Check conflicts across several calendars and add Microsoft 365 / Outlook
Calendly paid plans connect up to six calendars (Google, Office 365, Outlook, Exchange), let the user toggle which ones to check for conflicts and pick one destination calendar (https://blog.calendly.com/connect-multiple-calendars/). Our lib/google-calendar.ts queries freeBusy only for items [{id: 'primary'}], and there is no Microsoft provider at all. Small teams commonly keep a personal or shared team calendar next to the work one, and many SMB customers live in Microsoft 365, so today they get double booked or cannot use Cal. First scope: list the user's Google calendars and let them select which to check (freeBusy accepts many ids), then add a Microsoft Graph provider through registerBusyProvider plus event creation with the same best-effort pattern. Priority: high. Effort: M. Compared with Calendly.
- 0
Cal: Add start time increments independent of meeting duration
Calendly lets each event type set how often slots start, for example every 15 or 30 minutes regardless of length (https://calendly.com/help/how-to-fine-tune-your-availability-settings). Our engine in computeDaySlots (lib/calendar.ts) steps by durationMin, so a 45 minute event only offers 9:00, 9:45, 10:30 and a 60 minute event cannot start at 9:30. This produces odd times guests do not expect and wastes availability around existing meetings. First scope: add slotIntervalMin to bookingRules (default = duration, options 5/10/15/20/30/60), use it as the loop step in computeDaySlots, and expose it in the editor Limits section. Priority: high. Effort: S. Compared with Calendly.
- 0
Cal: Apply buffers of existing bookings too, so buffer protection is not order dependent
Calendly blocks the buffer around every Calendly meeting, so a 30 minute meeting with 15 minute buffers reserves 60 minutes (https://calendly.com/help/how-to-use-buffers). In lib/calendar.ts the buffer is only added to the candidate slot (applyBuffer in slotsForDay, pickFreeHost and HOST_FREE_SQL), while existing bookings are compared with their raw starts_at/ends_at. With bufferAfter=15, booking 8:30 to 9:00 first and then 9:00 to 9:30 is allowed with zero gap, but the reverse order is blocked. Hosts who rely on buffers for travel or prep get back-to-back meetings depending on who booked first. First scope: store the buffered range (or the buffer minutes) on each booking and expand existing bookings by their own buffers in listBusyRanges and HOST_FREE_SQL, plus a unit test for both orders. Priority: high. Effort: S. Compared with Calendly.
- 0
Cal: Run reminder and workflow cron often enough that 'X minutes before' steps arrive
Calendly Workflows send emails and texts at exact offsets such as 30 minutes before the meeting (https://calendly.com/blog/workflows). Our workflow editor lets hosts pick offsets in minutes (components/calendar/EventTypeEditor.tsx), but the only scheduler is /api/cron/tick at '17 * * * *' in vercel.json, and processDueWorkflowRuns in lib/calendar-workflows.ts silently marks a 'before' step as sent and skips it when the hourly tick lands after the meeting start. In practice a '15 minutes before' reminder is dropped roughly three times out of four, which defeats the main no-show reducer. First scope: move calendar reminders and workflow runs to the existing 5 minute cron (or schedule each email at booking time with the provider's scheduled send), and block offsets shorter than the cron interval in the UI with a clear hint. Priority: high. Effort: S. Compared with Calendly.