# Ask website visitors for the next useful builder conversation

A builder website call to action asks for the next real step in your intake, not a generic “contact us.” A plan reader gets “discuss this plan and your lot.” A project reader gets “ask about a similar build.” A homeowner gets “submit a warranty item.” Each form lands in your CRM with its source page and an owner.

## Why should every page not use the same button?

A person studying a floor plan is in a different conversation from a past buyer reporting a warranty item. A lot owner on a community page needs a site-fit review. A Parade visitor on a project page needs a way to name the house they toured. One generic contact form throws that context away and hands the office a sorting job.

A call to action is more than button copy. It is the prompt, the form fields, the source page, the confirmation message, the CRM record and the person assigned to act. Miss one part and the site collects an inquiry without creating a [handoff](/process/handoff/).

Each page job in the [builder websites articles](/articles/builder-websites/) needs its own action.

### Start with the next real step

Look at what the team does after a good inquiry. If the first step is a process call, ask for what you need to prepare for it. If the first step is a lot review, ask for the location and whether the lot is under contract. Do not offer an instant estimate when estimating needs plans, a site visit, specs and a review.

## Which action fits each builder page?

Match the action to the question the page answers. The wording should tell the visitor what will happen, not just command a click.

| Page | Useful action | Context to preserve |
| --- | --- | --- |
| Plan page | Discuss this plan and lot | Plan name, lot status and requested changes |
| Project page | Ask about a similar project fit | Project reference and feature of interest |
| Community or lot page | Request a site-fit conversation | Location, parcel status and plan status |
| Process page | Book a process conversation | Stage or question that prompted the inquiry |
| Available home page | Ask about this home's current status | Home identifier and referring page |
| Warranty page | Submit a service item | Home record, issue details and attachments |

Keep warranty and sales paths separate. A service request needs different fields, routing and records from a new-project inquiry. Route a question from a buyer's agent to your listing agent, and keep it out of the inbox that holds homeowner punch list items. The [listing agent guide](/guides/listing-agent-for-custom-builders/) shows what that handoff needs.

## What should an inquiry form ask?

Ask only for what changes routing or prepares the next step. Mark each field with its purpose and the role that reads it. Check that a visitor with no lot and no plan can still send the question the page invited.

1. **Identify the person.** Collect the contact details the team uses and a preferred contact method.

2. **Capture project type.** Distinguish a custom build, available home, lot review, agent inquiry or service request.

3. **Ask about location.** Let the visitor provide a community, general area or lot status without requiring a complete parcel record.

4. **Record plan status.** Ask if the visitor has a plan, is considering a named plan or needs design guidance.

5. **Preserve the source.** Store the page, campaign or event context that produced the submission.

6. **Invite the useful question.** Provide space for the issue the visitor wants addressed first.

The confirmation says what you received and what happens next. Do not promise a reply within the hour or a site visit unless the office keeps that promise every week.

## How should calls to action connect with site ownership?

Forms submit into systems in your name. The original inquiry, its source page and the consent record stay with you when a web or marketing vendor changes. Give one role the job of watching for delivery failures and testing the full path on a schedule.

The [Lead attribution stage](/process/lead-attribution/) joins form, call and campaign records so you can see where each inquiry began. The [builder lead tracking guide](/guides/builder-lead-tracking/) covers the rest of the measurement system.

### Keep the action visible and specific on phones

Buyers open plan and project pages from a text, a social post, a yard sign or a conversation at an event. The action has to be readable, tappable and clear without scrolling back up to recall the page subject. Carry the plan or project name into the form yourself instead of asking the visitor to type it again.

The article on [builder websites on phones](/articles/builder-websites/builder-website-on-phones/) covers the full mobile test, forms and confirmation states included.

## How do you test whether the action works?

Submit each form as a visitor would. Confirm the message on screen, the CRM record, the notification, the source value and the owner. Test required fields, bad input, attachments and a duplicate submission. Then repeat on a phone.

Keep a short action register: page, action, form destination, notification owner, last test date. Review it when plans, communities, events, staff or CRM fields change. If a test submission has no record, no notification or no next action, assign someone to fix it that week.

The article on [what a custom builder homepage must answer](/articles/builder-websites/what-a-custom-builder-homepage-must-answer/) shows where homepage actions fit once [positioning](/articles/positioning/) and routing are settled.

## Questions about builder website calls to action

### Should the phone number appear on every page?

A builder website can show a phone number across pages when calls have a defined owner. Pair the number with a page-specific inquiry action that preserves project context.

### How many fields should a project inquiry form have?

A builder project inquiry form needs fields used to determine fit, preserve the source and prepare the next step. Remove fields that the intake team does not use.

### Should warranty requests use the sales form?

Builder warranty requests need a distinct intake path, record and responsible role. Keep service items separate from new-project inquiries so each reaches the appropriate reviewer.

### How often should forms be tested?

Test builder website forms after site or system changes and on the recurring schedule in your maintenance plan. Confirm the destination record, notification and responsible role.