WEXCY FORMS

Ask for the details your team needs.

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

A useful request starts with the right questions.

Choose the information you need before the conversation starts. A defined structure helps the team read requests on the same terms.

QuestionOccasion
Example answer

Team lunch

Why it helps

Understand the occasion

QuestionGuest count
Example answer

20

Why it helps

Understand the group size

QuestionAdditional notes
Example answer

Vegetarian options

Why it helps

Read preferences before following up

Define required information and allowed choices according to the form's validation settings.

AFTER SUBMISSION

Give the submission a clear next step.

Keep the request as a structured record, then let the process you configured determine what the team does next.

  1. 01

    Check the submission

    Apply the action’s configured validation rules, including required information and allowed choices when enabled.

  2. 02

    Keep the record

    Keep the request data in a record linked to the form definition and its state.

  3. 03

    Continue through the configured workflow

    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

Questions about Wexcy Forms.

Clear answers about what a form collects, where a submission is kept, and how configured follow-up works.

A BETTER START

Start with a clearer request.

Collect the details your team needs, then follow the process you have defined.

Start for free