The short answer
A useful enquiry form collects enough information for a real next step and reliably reaches the person responsible for replying. Start with a short service request, one usable contact method and any detail needed to decide whether you can help. Then test the whole chain: visitor submits, the request is stored, staff are notified, and a reply reaches the visitor. Wix Forms can support that workflow, but the business still needs to design and verify it.
Define the decision staff need to make
Write the first action your team will take after reading a request. A local repair business might check the service area and type of fault before arranging a call. A design studio might decide whether a project fits its services before requesting a fuller brief. Those are different forms even if both use a button labelled 'Send enquiry'.
Use this worksheet for every proposed field: what decision does it support, must it be answered now, and who will use it? If nobody can explain the purpose, remove it or ask later. A long form is not automatically a better qualification tool; irrelevant required questions can prevent a suitable customer from making contact.
Keep a visible alternative contact route for people who cannot complete the form. Set expectations beside the button: what happens next and the response window your team can actually meet. An enquiry should not appear to confirm a booking, approve a quote or promise availability.
Build a small field set around the service
For an email-first service request, start with a name, email, service type and a short description. Add a postcode or service area only if it changes eligibility. Make the phone number optional unless a call is necessary. Avoid requesting full addresses, identification documents or payment information just to start a general enquiry.
Wix Forms provides contact fields and rules that can show or hide fields based on answers. Some field types, including file uploads and signatures, require particular upgrades. [1] Check the form version and current plan before designing around a feature you have not confirmed.
For example, a repair enquiry could offer 'Appliance', 'Installation' and 'Other'. Show a model-number question only where it helps identify the appliance; let someone select 'Not sure' instead of inventing an answer. A studio could ask for the project type and desired timeframe while leaving an exact budget optional until a first conversation. These are illustrative designs, not measured conversion results.
- Write clear labels; explain unfamiliar terms next to the relevant field.
- Mark optional details and accept 'Not sure' where the business can follow up.
- Keep newsletter signup separate from the request for a service reply.
Verify storage, notification and reply separately
Wix stores submitted entries in a submissions table, accessible from Forms & Submissions. [2] Use that as a separate checkpoint from email delivery. If a customer reports submitting but the team sees no email, first look for the record instead of immediately blaming the customer's browser.
Wix uses Automations for form notifications and lets you choose recipients. It also documents a dynamic reply-to setting using the submitted contact email. [3] Confirm the right people receive the notice, and test where a reply actually goes. A notification delivered to an unattended owner account is still a broken business workflow.
Assign a primary responder and a backup. Keep a simple operational status such as new, replied or waiting for details in the tool your team uses. That status is a business process recommendation, not a promise that every form version provides the same board or automation. Decide who checks unhandled requests when the normal responder is away.
Run a short acceptance test on the published form
Use your own test addresses and clearly mark messages as tests. Check the published site on a narrow phone screen and with a keyboard. Record the task, expected behaviour, stored submission, received notification and reply result. Do not mark the form passed simply because a success message appeared.
When notification email is missing, Wix recommends checking spam folders and automation recipients. [3] Compare the submitted record with the notification to see whether required details were omitted or mapped incorrectly. Check the reply route with a second address you control, rather than replying to an actual prospect during setup.
Repeat the affected cases after changing fields or notification settings. Keep a dated test record with the person who performed it, but avoid copying real customer details into a general checklist.
- Valid request: one stored submission contains the expected values, the assigned responder is notified and a test reply arrives.
- Missing required answer: the form identifies the problem and preserves other entries so the visitor can correct it.
- Optional fields blank: the request still works, and the notification remains understandable.
- Conditional question: switching the service type shows relevant fields without requiring a hidden answer.
- Mobile and keyboard: fields, validation and the send button remain reachable and readable.
Review spam handling without losing genuine enquiries
New Wix Forms include spam filters with configurable protection levels and invisible reCAPTCHA that can present a challenge when needed. Wix says detected spam remains in the Spam tab for 30 days before permanent deletion. [4] Review the instructions for your actual form version rather than looking for an old CAPTCHA field in a new form.
Give someone responsibility for checking suspected spam for legitimate requests. Do not assume a message is trustworthy merely because a platform sent the notification: unexpected links and attachments still need care. Review whether any new filter setting prevents an ordinary visitor from completing the form.
If your existing form already stores requests, reaches the right team and works on mobile, you may only need better labels or a clearer reply process. Choose Wix or another builder around the complete workflow. More fields and automations are useful only when they help the customer obtain a relevant response.
Before you decide
- Tie every field to the first useful decision your team makes.
- Make the next step clear without implying a confirmed booking or price.
- Test stored submissions, staff notification and customer reply as separate outcomes.
- Assign a responder, backup and regular review of suspected spam.
Sources & limits
This is a documentation-based guide, not a hands-on product test. Provider terms and exact configurations can change. Confirm the details that apply to your purchase.