Define what you need
Start with a title, payment amount and the information required to fulfill the request. A form can collect a booking reference, a service choice or a customer note. Avoid adding fields simply because they are available; each field should support the task.
Choose the field type
Use short text for references, a date field for dates and a number field for numeric input. Select, radio and checkbox groups fit different choice patterns. A heading can separate longer forms into readable sections without collecting another response.
Review the customer view
Use the layout preview to check labels, required fields and theme. Read the form as a customer would: the purpose, requested information and next action should be visible. Long labels and choices need to remain readable on a narrow screen.
Inspect responses and status
A submitted form provides customer information; it does not prove the attached payment is confirmed. Keep those states visible separately when reviewing submissions. The sample builder saves interactions within its preview session and does not deliver live customer responses.