Franz
My feedback
4 results found
-
17 votes
An error occurred while saving the comment Franz
supported this idea
·
-
16 votes
An error occurred while saving the comment Franz
commented
+1. I would especially like to see custom fields treated as structured booking data rather than only additional text on the page.
Besides short and long text fields, select fields and checkboxes, it would be useful to make fields required or optional and configure them individually for each booking page.
A very common business use case is that the booking follows another step, for example an assessment, contact form, application or qualification flow. Being able to safely prefill selected fields or pass a reference or context into the booking would avoid duplicate data entry and make the handoff much cleaner.
Longer term, structured access to these responses through an export, webhook or API would also be extremely valuable for creating or enriching CRM contacts and preserving the context of a booking for follow up.
File uploads are useful for some workflows, but structured custom fields and access to their responses would already solve a very broad range of business use cases.
Franz
supported this idea
·
-
30 votes
An error occurred while saving the comment Franz
commented
Strong +1. For professional use, custom questions are more than a convenience. They are often the missing handoff between scheduling and a useful first conversation.
It would be very helpful if each booking page could define its own required or optional questions, using fields such as short text, long text, single choice, multiple choice and checkboxes.
Common examples are company, current role, reason for booking, desired outcome, relevant context, or which service or topic the person is interested in.
Ideally, the answers would stay attached to the booking and be visible to the organizer before the meeting.
This would make Proton Booking significantly more useful for consulting, coaching, recruiting, sales conversations and other professional services without forcing users to place a separate form in front of the booking page and ask for the same information twice.
Franz
supported this idea
·
-
31 votesFranz
supported this idea
·
I agree. The current name and email flow works well for simple scheduling, but it is difficult to replace established booking tools in a professional workflow without a configurable intake step.
For many business appointments, the organizer needs a small amount of context before the meeting, such as company, role, meeting topic, desired outcome and one or two qualification questions. These fields should ideally be configurable per booking page, required or optional, and stored together with the booking.
This also matters beyond meeting preparation. A booking is often the point where an anonymous website visitor becomes a known contact in a CRM. Structured booking data makes it possible to preserve source and context, prepare the conversation, create or enrich the contact and reliably manage follow up afterwards.
Integration options such as structured export, webhooks or an API would make this much more powerful for business users.
I would also support the other points mentioned here, especially control over which organizer email address is displayed and an embeddable booking page.