> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/3.x/examples/contact-form.md).

# Contact Form

Below is an example of a simple contact form with name, email, phone, and message fields. The fields use CBWIRE's built-in [Validation](https://cbwire.ortusbooks.com/3.x/wire-features/validation.md) features.

For the validations to work, you must have *cbValidation* installed. You can install it using CommandBox like so:

```
box install cbvalidation
```

## wires/contactForm.cfm

```html
<cfscript>
    // Constraints
    constraints = {
        "name": {
            "required": true
        },
        "email": {
            "required": true,
            "type": "email"
        },
        "phone": {
            "required": true,
            "type": "telephone"
        },
        "message": {
            "required": true,
            "size": "10..500"
        }
    };

    // Data Properties
    data = {
        "name": "",
        "email": "",
        "phone": "",
        "message": "",
        "success": false
    };

    // Actions
    function submitForm() {
        data.success = true;
    }
</cfscript>

<!--- Template --->
<cfoutput>
    <form wire:submit.prevent="submitForm" id="contactForm">
        <div class="form-floating">
            <input wire:model.lazy="name" class="form-control" id="name" type="text" placeholder="Enter your name..." data-sb-validations="required" />
            <label for="name">Name</label>
            <cfif validation.hasErrors( "name" )>
                <div class="text-danger">
                    #validation.getAllErrors( "name" ).first()#
                </div>
            </cfif>
        </div>
        <div class="form-floating">
            <input wire:model.lazy="email" class="form-control" id="email" type="email" placeholder="Enter your email..." data-sb-validations="required,email" />
            <label for="email">Email address</label>
            <cfif validation.hasErrors( "email" )>
                <div class="text-danger">
                    #validation.getAllErrors( "email" ).first()#
                </div>
            </cfif>
        </div>
        <div class="form-floating">
            <input wire:model.lazy="phone" class="form-control" id="phone" type="tel" placeholder="Enter your phone number..." data-sb-validations="required" />
            <label for="phone">Phone Number</label>
            <cfif validation.hasErrors( "phone" )>
                <div class="text-danger">
                    #validation.getAllErrors( "phone" ).first()#
                </div>
            </cfif>
        </div>
        <div class="form-floating">
            <textarea wire:model.lazy="message" class="form-control" id="message" placeholder="Enter your message here..." style="height: 12rem" data-sb-validations="required"></textarea>
            <label for="message">Message</label>
            <cfif validation.hasErrors( "message" )>
                <div class="text-danger">
                    #validation.getAllErrors( "message" ).first()#
                </div>
            </cfif>
        </div>
        <br />
        <!-- Submit success message-->
        <cfif success>
            <div id="submitSuccessMessage">
                <div class="text-center mb-3">
                    <div class="fw-bolder">Form submission successful!</div>
                </div>
            </div>
        </cfif>
        <!-- Submit Button-->
        <button
            class="btn btn-primary text-uppercase <cfif validation.hasErrors()>disabled</cfif>"
            id="submitButton"
            type="submit">Send</button>
    </form>
</cfoutput>
```


---

# 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://cbwire.ortusbooks.com/3.x/examples/contact-form.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.
