top of page
Search

Sort Wix form leads with one small automation

Writer: apteagency
apteagency
2 days ago
4 min read

Give each inquiry a clear place to go. Use AI only when free text is doing work that a simple choice cannot do.

Suppose a contractor uses one form for repairs and full installations. Installation requests sit in the same inbox as existing-job questions. Before you add anything to the system, list the people who can handle each kind of note and decide what they need to see.

Try sorting a few made-up entries in the current inbox. If your colleagues regularly disagree about which team should get a request, decide who owns that choice before you ask software to make it.

Give the visitor a choice they can answer

Put short choices in the words the customer would use. "Fix something already installed" may be clearer than "service request." Leave a route for someone who is unsure. Test the choices against a handful of made-up inquiries before you change the form.

Keep one owner for the uncertain category. If that person sees the same request often, ask whether it deserves a new choice. If a customer must choose a technical department they have never heard of, change the choices. There is no advantage in getting a clean list of categories that customers guess at.

Repairs. Send to the existing-job team. New installation. Send to estimates. Unsure. Send to the intake owner. Record. Keep the original inquiry in the approved system.
Route a contractor inquiry. Start with an explicit choice on the form.

Route on a field before you classify a message

The Wix guide to automation conditions explains how a Wix Automation can use a condition to choose between branches. The Wix Forms automation guide shows how to start a rule when a customer submits a selected form. Check which fields your configuration supplies. Give the other branch to the person who receives unclear requests.

Make the first version small enough to verify. Try one inquiry for each route and one without a recognizable category. Compare the submissions in Wix with the messages staff received. Ask a recipient to show you which part of the message tells them the next action.

Try AI only on the uncertain part

Take a few invented free-text notes. Give them one label from your list and see which ones a staff member would send somewhere else. If the choice is ambiguous, include a category like "Needs a person." Decide which examples must always land there before you test a classifier.

You can also use the Wix guide to automation conditions documentation to see where Wix offers help building certain conditions. Review any generated rule before using it. Read the exact condition against a normal request and an exception. A rule that sounds plausible in a prompt still needs to handle the values your form actually provides.

Have the colleague who reads inquiries check whether the form labels match the words customers use when they call.

Keep the test close to what staff receive

Use a test configuration or agreed internal recipients. Put a clear label on test notifications. Submit a new installation request with a harmless sentence that mentions a repair as background. See whether the result follows the form choice or the incidental phrase in the note.

Try a blank optional message, a double submission and an urgent request written in plain language. Decide what staff should see for each example. If you use automated acknowledgments, read those separately. Check that the message says the request was received and gives the customer the next step you can actually support.

Use an invented case with overlapping categories and write down who should get it before running the automation.

Mixed note. Check where a repair mentioned in passing goes. Blank message. Verify the form choice still works. Uncertain. Give staff a usable handoff. Retry. Check what happens to a duplicate submission.
Test the unusual cases. Agree on the result before enabling a rule.

Decide what belongs in each destination

Use as little customer information as the recipient needs for the first action. Decide which details must stay in an approved company system. If an email just needs to tell someone to open the lead record, include only what that person needs to find it. Ask your team to approve any extra service that would receive the form text.

Name the person who owns wrong turns. Give them a quick way to reassign a lead without asking the customer to resubmit it. Keep the original note available where staff already handle inquiries. Make the way back from a wrong label part of the test.

Review the first week by looking at actual work

Agree on what the office will record. Useful notes might include a confusing choice, a message that arrived twice or a lead no one knew how to handle. Store the examples without copying personal information into a shared design document. Build your next changes around what the team saw.

If you change a form label or add a category, run the same test again. Compare who received the message and what the customer saw. Give the person who owns the form a short list of the expected routes so they can check a new rule before it goes out.

Check that a staff member can see a wrong assignment and move it without sending the customer back to the form.

Wix features and plans can change. Confirm the tools you need in your own account before committing to a project.

Sources

Bring your form and the staff roles that handle inquiries. TJ can help you pick a first automation to try.

 
 
 

Comments


bottom of page