Currently with a From to Book a meeting flow, users would need to fill 2 forms. One at the beginning (the “form”), and another one at the end since the “book a meeting” requires a form. This is not ideal from a user experience pov, and not using the form at the beginning means we don’t get the data availbale as part of the form tool.
Status: Idea Submitted
Hi @NSamimi
Could you elaborate a bit more what data you would miss by not using a “normal” form?
What is your user journey? You can customise the form for the meeting and capture additional information.
Depending on what you ask on the normal form you can also set the meeting form to populate with known values and auto-submit if all information is known.
Would that help your use case?
Thanks
Frank
So the flow I want to use is Form, then using the “Redirect to another page” functionality take the use to my book a meeting link (which shows our team’s calendar). However I do not want to have the mandatory form fill at the end of the book a meeting flow. Because the user has already filled a form at the beginning. I’ve tried the pre-populate fields function in the meeting tool, and it doesn’t work to pull the data from the form (did not work for me or an agent from your support team)