Team lunch
Understand the occasion
WEXCY FORMS
Collect inquiries through structured forms. Keep each submission organized and connect it to the workflow you have set up for the next step.
STRUCTURE THE REQUEST
Choose the information you need before the conversation starts. A defined structure helps the team read requests on the same terms.
Team lunch
Understand the occasion
20
Understand the group size
Vegetarian options
Read preferences before following up
Define required information and allowed choices according to the form's validation settings.
AFTER SUBMISSION
Keep the request as a structured record, then let the process you configured determine what the team does next.
Apply the action’s configured validation rules, including required information and allowed choices when enabled.
Keep the request data in a record linked to the form definition and its state.
A state change can start workflow-related processing according to its configured rules.
Submitting an inquiry does not confirm a booking. Your team follows the process you have defined.
WEXCY FORMS FAQ
Clear answers about what a form collects, where a submission is kept, and how configured follow-up works.
You can collect inquiries and structured information through the fields defined for the form, such as an occasion, guest count, and additional notes.
Required information and allowed choices are checked according to the validation rules configured for the action; not every check is assumed to apply by default.
The submitted data is kept in a record linked to the form definition. It is not automatically copied into every Wexcy product.
Yes, when the relevant route, action, and workflow rules are configured. Accepting a submission does not mean every later workflow step has already finished.
No. Receiving an inquiry and confirming a booking are separate stages governed by the process your organization defines.
A BETTER START
Collect the details your team needs, then follow the process you have defined.
Start for free