When a host books a meeting on behalf of a contact (via the "Book for contact" flow), the booking form bypasses required fields that are enforced when an invitee books themselves.

This creates a data integrity issue: records created through host-initiated bookings end up incomplete compared to those created through the standard invitee flow, breaking any downstream automation or CRM sync that relies on those fields being present.

Any field marked as required in the scheduling link should be required regardless of who initiates the booking — invitee or host.

Required fields are only enforced on the invitee-facing booking form. The host booking flow skips them entirely (or makes them optional).

Hosts who book on behalf of contacts should still be prompted to fill in required fields (e.g. phone number, topic, source) to maintain consistent data across all bookings.