> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/form-guard.md).

# FORM GUARD

- [Form Guard Overview](https://docs.clearout.io/form-guard/overview.md): Real-time form validation with advanced lead analytics, threat forensics, and lost lead recovery
- [Email Field Validation](https://docs.clearout.io/form-guard/email-field-validation.md): Validate email fields on web forms live
- [Phone Field Validation](https://docs.clearout.io/form-guard/phone-field-validation.md): Real-time phone number validation & formatting
- [Name Field Validation](https://docs.clearout.io/form-guard/name-field-validation.md): Validate name fields to prevent spam leads
- [Advanced Settings](https://docs.clearout.io/form-guard/advanced-settings.md): Configure form guard validation rules.
- [Form Guard Analytics ](https://docs.clearout.io/form-guard/analytics.md): Monitor Form Guard performance, investigate blocked leads, and recover lost opportunities.
- [Developer](https://docs.clearout.io/form-guard/developer.md): Form guard API & developer implementation
- [Form Guard FAQs ](https://docs.clearout.io/form-guard/faqs.md): Find answers to common questions about the Form Guard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.clearout.io/form-guard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.