Choose validation or review after submission

A form can reject a useful inquiry for the wrong reason. It can also accept a message that leaves staff with no practical next step. Those failures look similar in a queue, but they need different fixes.

Sentient Forms 0.12.0 can run Spam Detection and Content Quality Validation during validation for Gravity Forms, Contact Form 7, WPForms, and Elementor Pro Forms. That makes the timing choice more important. WordPress form validation should help a visitor fix something now. Work that depends on staff judgment usually belongs after submission.

Start with the cost of a wrong decision

Validation sits between the visitor and a successful submission. A false positive can block a real lead. After-submission review has a different cost. A weak result may waste staff time, but the original entry still exists for a person to inspect.

Decision	If the system is wrong	Safer first location
The message is obvious spam	A real visitor may be stopped	Validation, after a cautious test
The answer is too vague to use	A useful inquiry may be blocked	Validation only when feedback is specific
The lead looks worth pursuing	Staff may prioritize it badly	After submission
The request belongs to a team	The first owner may be wrong	After submission
The entry needs a short summary	Staff can still read the source	After submission

Block only when the visitor can understand the problem and fix it before trying again.

Use validation for fixable input problems

A validation message should point to a concrete repair. “Add the project deadline” gives the visitor a next step. “Your response is low quality” does not. The second message hides the rule and asks the visitor to guess.

• The problem is visible in the submitted fields.
• The visitor can correct it without staff help.
• The message names the missing or unsafe part in plain language.
• A false positive will not silently erase the original work.
• The same rule has passed tests with short, long, unusual, and borderline answers.

Keep native required fields and conditional logic for deterministic rules. An email address, consent checkbox, or required service area does not need an AI opinion. The existing guide to using form logic before AI shows where those rules belong.

Keep staff judgment after submission

Lead grades, urgency, routing, summaries, and reply drafts help staff decide what to do. They should not become visitor-facing gates simply because they can run earlier in the form lifecycle.

Start those workflows after submission. Preserve the source entry, attach a readable result, and let staff compare the recommendation with the original fields. The human review sampling guide gives a practical way to check whether people agree with the result before you expand the workflow.

Respect the Form Source boundary

The four supported Form Sources do not expose identical records or native effects. Gravity Forms has the deepest native workflow path, including realtime behavior where the Action supports it. Contact Form 7, WPForms, and Elementor Pro Forms use the Sentient Forms Submission Ledger for after-submission results. Elementor support requires Elementor Pro Forms APIs.

Version 0.12.0 adds validation support for Spam Detection and Content Quality Validation across all four. It does not turn every after-submission result into a native entry note, native spam status, notification control, webhook control, or realtime suggestion. Check the current WordPress.org listing before copying a setup from one builder to another.

Test the rule before it can block a visitor

Build a small test set from consented examples or synthetic entries. Include obvious passes, obvious failures, terse answers, long answers, and cases that a reasonable person could read two ways. Record the expected result before running the test.

1. Run the exact form and Action configuration you plan to use.
2. Read the visitor-facing message on desktop and mobile.
3. Confirm the message points to a repair the visitor can make.
4. Submit again after the repair and confirm the form succeeds.
5. Keep a human recovery path for borderline cases.

Do not call the test complete because a direct service request returned the expected label. Use the same form path a visitor will use. The client rollout checklist covers the wider handoff.

Measure blocks and recovery separately

Count how often the rule blocks a submission, how often the visitor succeeds on the next attempt, and how often staff says a blocked example should have passed. A high block count is not a win by itself. The useful signal is fewer unusable entries without a rise in avoidable abandonment or support requests.