If Customers Aren't Leaving Their Information, Your Website Forms Are Failing Them

When we first published this in 2019, the advice was simple: clear headings, real offers and a specific call to action. That still holds. A shopper trades contact details for something worth having, and if the trade looks bad, they keep scrolling.

What has changed is everything around the form. Shoppers fill them in on phones, and they have learned that one form can mean a week of calls. Text consent has rules with real penalties. And a lead sitting in a shared inbox is not really a lead.

This guide is for the dealer principal, sales manager or BDC lead who owns the website's results. It covers which forms to offer, how many fields each deserves, consent, accessibility, and the part most guides skip: where every submission goes after the shopper presses the button.

Why powersports shoppers skip your forms

Most shoppers who leave without filling in a form looked at the trade and said no. The usual reasons:

• The button is vague. "Submit" or "Contact us" does not say what the shopper gets. "Check availability" does. Our guide to call to action examples for powersports dealer websites covers the wording.
• The price is hidden behind the form. If "Get my price" leads to a call instead of a price, word gets around.
• The form asks too much, too early. A home address and a birth date to ask whether a side-by-side is in stock feels like a trap.
• Nothing says what happens next. Will a person reply? By text or by phone? Today or Monday?
• It breaks on a phone. Tiny fields, a keyboard that covers the button, or an error message nobody can find.

The six forms every powersports dealer site needs

A dealership website needs a small set of forms, each matched to a question the shopper actually has, not one "contact us" form copied onto every page. Our certified powersports dealer websites are built on the same idea: "Match each form and call to action to the page, vehicle, and stage of the shopper journey."

Two notes on the table:

1. The unit should travel with the form, not be typed by the shopper. A "Check availability" form on a VDP already knows the stock number, year, model and price shown. Pass it in automatically. Our certified website page puts it this way: "The vehicle, source, behavior, and requested action can move with the lead instead of becoming another disconnected form submission."
2. Powersports is not automotive. Trade forms need an engine-hours option, because many ATVs, side-by-sides and personal watercraft are valued by hours rather than miles. Test-ride forms may need to ask about a motorcycle endorsement, so nobody drives an hour to be turned away.

How many fields each form should ask for

There is no magic number, and we will not quote a conversion statistic we cannot source. The working rule: ask only for what the first useful reply needs. Everything else can come in the conversation.

• Name: first name is enough for the first reply. Last name can wait.
• Contact: ask for phone or email and let the shopper pick which one you use. A "preferred contact method" choice (text, call or email) tells your team how to reply and is often the most useful field on the form.
• Address and birth date: not on any form except the credit application.
• "How did you hear about us?": drop it. Your website and CRM should record the source without asking.

The credit application is the exception: lenders need the information, so the goal is an easier path, not fewer fields. The W3C's forms tutorial recommends dividing long forms "into multiple smaller forms that constitute a series of logical steps or stages," with progress shown to the user. Break the application into steps (you, your address, your income, review), show "Step 2 of 4," and keep what the shopper entered if they go back.

Before adding any required field, ask: who reads this, and what do they do differently because of it? If the answer is "nobody," cut it.

Consent checkboxes for text and email, done properly

Many dealer forms get this wrong in one of two ways: a consent sentence buried under the submit button, or a pre-ticked box the shopper must accept to ask a simple question.

Start with the distinction that matters. A shopper who asks "Is this unit in stock?" expects an answer about that unit. Marketing texts (sale announcements, event invitations, new arrivals) are a different thing under the FCC's rules for the Telephone Consumer Protection Act (TCPA).

For marketing calls and texts sent with an autodialer, the FCC's rule at 47 CFR 64.1200 requires prior express written consent. The regulation defines it as a written agreement, bearing the customer's signature, that clearly authorizes the seller to send advertisements or telemarketing messages to a specific phone number. Three details matter for a web form:

1. The disclosure must be clear and conspicuous. It must tell the person they are authorizing those messages.
2. Agreeing cannot be a condition of purchase. The disclosure must say the person is not required to agree "as a condition of purchasing any property, goods, or services."
3. An electronic signature can count. The rule says a signature includes "an electronic or digital form of signature" recognized under federal law or state contract law.

What that looks like on a dealership form:

• Two separate, unticked checkboxes: one for marketing texts, one for marketing emails. Neither is required to submit the form.
• Plain wording that names your dealership and the number the consent covers. For example: "Yes, [Dealership] may send me marketing texts, including by automated technology, at the number above. Consent is not required to buy. Message and data rates may apply. Reply STOP to opt out." Have your counsel approve your exact wording.
• A link to your privacy policy next to the boxes, not hidden in the footer.
• A record of what the shopper saw. Store the date and time, the form, the page, and the version of the consent wording with the customer record in your CRM. If you change the wording, keep the old version.

Carrier registration, opt-out handling and quiet hours are covered in our guide to texting customers the right way, so they are not repeated here.

This is general information, not legal advice. Rules change, states add their own, and Canada works differently, so have counsel review your forms.

Accessible form design: labels, errors and autofill

A form that a screen reader or keyboard user cannot finish loses that lead. Our call to action guide covers buttons and contrast; this section covers the form itself, using the W3C Web Accessibility Initiative (WAI) forms tutorial and WCAG 2.2:

• Every field has a visible label. The tutorial's first rule is to give each control a label, mainly with the HTML <label> element. Placeholder text inside the box disappears when the shopper starts typing, so it is not a label.
• Related choices are grouped. "Text / Call / Email" as preferred contact should be radio buttons inside a <fieldset> with a <legend>, so a screen reader announces the question with the options.
• Instructions come first. Say which fields are required before the shopper starts, not after they fail.
• Errors are specific and in text. WCAG 2.2 success criterion 3.3.1 requires that when an input error is detected automatically, "the item that is in error is identified and the error is described to the user in text." A red border alone fails. "Enter a 10-digit phone number" passes, and criterion 3.3.3 asks for that kind of suggestion when you know the fix.
• Autofill works. Criterion 1.3.5 (Identify Input Purpose) asks that the purpose of fields collecting information about the user "can be programmatically determined." In practice that means correct autocomplete values for name, email, phone and postal code, which also lets phone users fill a form from saved details.
• The credit application has a review step. For pages that cause financial transactions or legal commitments, criterion 3.3.4 requires that submissions are reversible, checked for errors, or confirmed through a review before they are final.

For what the law asks of a dealer site overall, see what the ADA asks of a powersports dealer website.

Where every submission must go

The top results for this topic stop at the form, then say "send it to your CRM" in one line. But the shopper's experience is decided in the minutes after the button. A great form feeding a shared inbox nobody checks on Saturday is a bad form.

Every submission should follow this path:

1. Into the CRM, as a record, with context. Form type, unit and stock number, page, source, preferred contact method and consent record arrive together, not as an email someone retypes.
2. Matched to an existing customer. If the phone or email already belongs to a past buyer or a service customer, the owner should see that history before replying.
3. Assigned to one named owner. Use the owner column in the table above, with a backup for days off. Our guide to who should handle internet leads covers how to decide.
4. Answered by a person, quickly, in the shopper's chosen channel. The reply answers the form's question: "Yes, the Rincon is on the floor. Want to see it at 4 today?" not "Thanks for your interest." Answering the question they asked is informational; it is not a marketing message. See what slow lead response costs a powersports store.
5. Confirmed on screen. The thank-you page says who will reply, how and roughly when. It is also the cleanest event to count; see tracking website conversions.
6. Escalated if nobody connects. Set your own target, such as a two-way conversation within 15 minutes during open hours, and alert a manager when it is missed.
7. Prioritized by intent. A credit application on an in-stock unit is not the same as a newsletter sign-up. Use simple lead scoring for powersports dealerships to decide who gets called first, without delaying the first reply.

Credit applications need a stricter path

A credit application holds Social Security numbers, income and addresses. It should never travel as a plain email. If your store arranges financing, ask your counsel whether the FTC's Safeguards Rule (16 CFR Part 314) covers you; the rule's own examples of a customer relationship include an agreement to "arrange or broker a home mortgage loan, or credit to purchase a vehicle." Where it applies, the rule requires, with limited exceptions, encrypting customer information in transit over external networks and at rest, multi-factor authentication for anyone accessing your information systems, and notice to the FTC no later than 30 days after discovering a security event involving the unencrypted information of at least 500 consumers. This is general information, not legal advice.

How PSX Ascend handles the path

On PSX Ascend's AI-powered powersports CRM, website leads arrive with their context and an owner, and the team works them from one record across phone, text and email. One dealer reports this result from the connected website and CRM:

"The PSXAscend website, combined with their CRM, has allowed us to connect in a two-way conversation via phone, text, or email 99% of the time in less than 1 minute from the time a lead is submitted."

Chuck Scott, GM, Edge Performance Sports (dealer-reported)

When a shopper goes quiet after the associates have worked the lead, ALMA, the Automated Lead Management Assistant, takes over the repetitive re-engagement, aiming to bring the customer back to a live conversation with a person. ALMA does not make AI voice calls.

You can also see the same certified dealership websites on our sister site, PSXDigital's certified dealership websites page.

Run a 30-minute form audit

Open your website on a phone, submit every form, and score each one.

Fix routing first (an unanswered lead is lost whatever the form looks like), then consent, then fields, then design. Repeat the audit every quarter and after any website change, because forms break quietly.

Sources

• eCFR, 47 CFR 64.1200, delivery restrictions (TCPA rules, including prior express written consent)
• eCFR, 16 CFR Part 314, Standards for Safeguarding Customer Information (FTC Safeguards Rule)
• W3C Web Accessibility Initiative, Forms Tutorial
• W3C, Web Content Accessibility Guidelines (WCAG) 2.2