Clear product answers.
Grounded in MyCal.

It can explain documented MyCal features, current beta availability, privacy behavior, calendar connections, relationship rules, Company Intelligence, notifications, and where hosts find settings.

No. The public beta is grounded only in approved MyCal website and product-source material. It refuses questions that the current sources do not support.

No. The public guide cannot access or change account data, calendars, contacts, bookings, API keys, or billing. Account actions remain inside the authenticated host workspace.

Open your email-bound beta invitation and choose the unique name after mycal.live/. MyCal checks availability as you type and blocks product routes, names already in use, and names held by another pending invitation. The address remains permanent during beta so shared links keep working.

MyCal asks the event’s normal conditional booking questions first, then shows one neutral no-times result. By default, the host receives a private email with the verified visitor, requested event, answers, time zone, and whether booking rules or the relationship-specific booking window prevented registration. Hosts can turn that email off under Notifications → No-time booking alerts.

Yes. Under Scheduling, open an event type and its dropdown or Yes / No booking question, then expand Registrant follow-up emails. Each answer can send a separate customized email after registration with a subject, message placeholders, and up to 3 private attachments. Each file may be 10 MB and all attachments together may be 15 MB.

Yes, when the host enables it for that event type. Under Scheduling, edit the event and set Invitee-added guests to a limit from 1 through 10. The booking form then accepts one guest email per line. Added guests receive the same Google or Microsoft calendar invitation after the meeting is confirmed—or after host approval when approval is required—but they do not receive the primary invitee’s private booking answers. Set the option to Off to keep the meeting limited to the person booking.

Signed-in hosts can open Analytics from the left navigation to review their own created, completed, upcoming, pending, rescheduled, cancelled, and no-show meetings. Reports support 7, 30, 90, or 365 days, compare the prior period, show event-type, duration, weekday, and daily trends, and export a private CSV. Super Admin has a separate aggregate Analytics view with cross-workspace totals and host activity but no guest identity or booking answers.

Open Launch from the signed-in host navigation. The Host Launch Assistant checks your profile, booking calendar, conflict calendars, availability, active event types, guest-facing details, and automations. Its built-in test booking sends a fictional guest through the same live availability engine used by visitors, but it does not create a calendar event, send messages, consume AI or SMS, or add a booking to analytics.

Open Preview from the signed-in host navigation. Choose Public, Known, MyCal VIP, blocked, or Specific email. The specific-email option evaluates your real contact tags, email and domain exceptions, prior meetings, company rules, disposable-email protection, booking cadence, schedules, horizons, and connected-calendar conflicts. It is read-only: times cannot be booked, no hold or appointment is created, no message is sent, and analytics do not change.

Yes, when Sign in with Apple is activated for the environment. Apple verifies the invitee before MyCal reveals meeting options. If the invitee chooses Hide My Email, MyCal links repeat sign-ins through Apple’s stable identity and uses the relay address as the verified booking email.

Open Contacts. Readable recent bookers, manual contacts, and encrypted Calendly imports show their effective Public, Known, MyCal VIP, or Do Not Schedule label, any rolling booking cadence, and whether an email, domain, Google Contact, company, import, or booking-history rule supplied it. Google- or Microsoft-only contacts remain non-browsable, so MyCal reports those classifications as private totals until the person becomes a readable booking or imported contact.

Common contact details and secret-shaped values are removed before processing, stored conversation text is encrypted, and public guide history is retained only for a short operating period.