Forms

Forms

Definition

Every Hibu One Smart Site includes at least one form by default, and additional types of forms may be added depending on the client’s needs. The four standard form types (Contact,  Request,  Hero,  Custom) are designed to capture leads efficiently and securely. All forms share a common foundation — structure, behavior, and compliance requirements — but differ in purpose and placement.

Common to All Hibu One Smart Forms

All forms on Hibu websites share the following core elements:

• Form Submission Notifications: Configured in the Performance Dashboard. Any number of contacts may receive notifications via email, text, and web push.
• Email Subject Line: Submitted emails display as “New Form Fill Submission.”
• Error Message: By default reads “Oops, there was an error sending your message. Please try again.” (editable on request).
• Confirmation Message: By default reads “Thank you for contacting us. We will get back to you as soon as possible.” (editable on request).
• Thank You Page: Forms may redirect to a thank-you page on request.
• A free thank-you page may be added when requested or when determined necessary by an Elite Analyst.
• This page is already included as a hidden page with indexing turned off.
• Title tag should be updated to: “Thank You | NOB.”
• A meta description is not required.
• reCAPTCHA:
• Added by default to all forms to protect against spam and speed up the submission process.
• The reCAPTCHA icon appears in the bottom-left corner only when a visitor interacts with the form (clicks into a field).
• The icon disappears after submission or page refresh.
• Position and display (icon or text) can be adjusted in form settings.
• reCAPTCHA cannot be disabled.
• Tracking & Integrations
• Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form.  (view details)
• Hibu will not set up accounts, generate, or retrieve third-party code.
• Sensitive Data Restrictions: No form may request medical, financial, or other sensitive information. (view list)
• Field Type Alignment & Validation
• All template and section forms include built-in validation for standard field types (e.g., phone, email, zip, date, time).
• When adding a custom form, Hibu team members are expected to select the correct field type so the validation applies properly. For example:
• Phone → Phone field
• Email → Email field
• Zip/Number → Number field
• Date/Time → Date or Time field
• Message/Question → Long text field
  

Contact Us Form

• One (1) contact form is included by default on the Contact Us page or non-Multi Location pages, unless a client requests removal.
• By default, the template displays the form title and button label as “Send Us a Message.”
• Clients may request alternate wording such as “Contact Us,” “Request Information,” or “Get in Touch.”
• It is expected that the Hibu Build Team updates both the form title and the button label so they match.
• May include additional fields upon request (dropdowns, checkboxes, etc.), except where HIPAA restrictions apply (see below).
• Sensitive Data Restrictions: No form may request medical, financial, or other sensitive information. (view list)
• Healthcare Businesses:
• Message/long-text fields must be excluded.

Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental.

• Tracking & Integrations: Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form.  (view details)
  

Request Form

• A Request Form is a detailed, multi-field form placed on a dedicated page to support the site’s primary call to action (e.g., Request a Free Estimate, Request a Quote, Request an Inspection, Request a Callback).
• Request Forms do not count toward the total page count.
• The type of Request Form should align with the client’s call to action (CTA).
• The DSC is responsible for determining the correct form to match the CTA and relaying that to the Build Team.
• By default, the form title and button label display as “Request Information.”
• Clients may request alternate wording such as “Request a Quote,” “Schedule Appointment,” or “Get a Free Estimate.”
• It is expected that the Hibu Build Team updates both the form title and the button label so they match.
• The URL slug must also be updated to match the CTA (e.g., /request-quote, /request-appointment).
• By default, Request Forms include:
• Full Name
• Email
• Phone
• Preferred contact method
• Product/Service selection
• Message/long-text field (unless restricted by HIPAA).
• May include additional fields upon request (dropdowns, checkboxes, etc.), except where HIPAA restrictions apply (see below).
• Sensitive Data Restrictions: No form may request medical, financial, or other sensitive information. (view list)
• Healthcare Businesses: Message/long-text fields must be excluded. Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental.
• Tracking & Integrations: Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form.  (view details)

Hero Form

A Hero Form may be added by request.

• When requested, the form will be placed on the homepage, category landing pages, and all core service/product pages.
• A client may request removal of the form on specific pages where it is not applicable, and that is permitted.
  
  

Purpose: capture quick leads with as little friction as possible. Short forms mean higher completion rates and more leads.

Default Setup

• Four fields: Full Name, Phone, Email, and a Services/Products dropdown.
• The dropdown is connected data, populated through the form collection.
• By default, the form title and button label display as “Get Started.”
• Clients may request alternate wording such as “Request Info,” “Schedule Now,” or “Free Estimate.”
• It is expected that the Hibu Build Team updates both the form title and the button label so they match.
  
  

Field Limitations

• Hero forms are limited to four fields by default.
• One additional short field may be added if needed (e.g., Zip, City/State, “How did you hear about us?”).
• Long-text boxes or multiple extra fields are not allowed, as they hurt conversion rates and mobile user experience.
• For more detailed lead capture (addresses, project descriptions, multiple checkboxes, etc.), the form should be replaced with a button CTA that links to a dedicated Request Form page.
  
  

Operational Considerations

• Updating the Hero Form requires updating every instance across the site.
• On large sites (30–50+ pages), this becomes time-consuming and inefficient.
• For efficiency, performance, and conversion best practices, Hero Forms should remain simple.
  
  

Tracking & Integrations

• Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form.  (view details)
  
  

Client Requests for Page-Specific Hero Forms

• Clients may request different Hero Form setups on different pages (e.g., alternate fields, removal of fields, or different services).
• Requests to swap one field for another (e.g., replace Services with an additional text field) are permitted.
• Requests to remove fields are also permitted (e.g., one page may have three fields, another may have two, another may have four).
• Requests to change or adjust services in the dropdown are permitted but require a ticket submission, since the connected form collection must be modified and reconnected.
• Field type validation: If replacing specialized fields (e.g., Phone or Email) with a general text field, the Hibu Team must also change the field type to “text.” If not updated, validation errors will occur (e.g., a non-email entry being rejected).
• Long-text fields are not permitted in Hero Forms. Only short text fields may be used to maintain conversion performance and mobile usability.

Custom Form

A custom form is any form added to a Hibu One Smart Site that is not a Contact, Request, or Hero form. Custom forms allow businesses to collect specialized information from visitors while following Hibu’s compliance and usability standards.

Rules

• Hibu will build up to 10 unique custom forms per site.
• Each custom form must serve a unique purpose and contain its own set of fields.
• Forms may be duplicated across multiple pages as needed, but no more than 10 distinct forms will be created.
• Custom forms may not exceed 25 fields.
• Forms with 10 or fewer fields may be placed on any page.
• Forms with more than 10 fields must be placed on their own dedicated page, which counts toward the site’s total page count.
• Custom forms may include any of the available DUDA platform form fields, except where HIPAA restrictions apply (see below).
• Field Validation: Custom forms follow the same validation rules as all Hibu One Smart Forms (see Common to All Forms).
• Tracking & Integrations: Third-party tracking and integrations (e.g., Google Ads, Sheets, Webhooks) may be connected to this form. (view details)
  
  

Restrictions

• Sensitive Data Restrictions: No form may request medical, financial, or other sensitive information. (view list)
• Healthcare Businesses: Message/long-text fields must be excluded. Applies to doctors, dentists, pharmacies, therapists, nursing homes, counselors, and insurance providers handling medical/life/health/dental.

Form Design Rules of Thumb

When building custom forms in Hibu One Smart Sites, the following UX and design guidelines should be followed to ensure forms are easy to use, accessible, and function correctly.

General Options (Most Field Types)

• Required Fields:
• If left blank, a red box will appear around the field.
• No automatic indicator (e.g., asterisk) is added — builders should manually add “*” or text like “(required)” in the Field Label or Placeholder.
• Start New Line:
• Use this option to force a field to display on its own line.
• Field Size:
• Adjust width to improve layout and responsiveness.

Specific Field Considerations

• Radio Buttons & Checkboxes:
• Images can be added to display as option choices.
• Images will not appear in the email submission.
• The selected label will still appear in the email (even if hidden on the site).
• Time Field:
• The “Use 24-hour clock” toggle only affects how submissions display.
• The time picker shown to visitors depends on their browser settings.
• File Attachment Field:
• File name must not include spaces.
• File size limit: 10MB.
• Only one file per attachment field (add multiple File Attachment Fields if needed).
• Supported formats:
• Documents: .pdf, .doc, .docx, .xls, .xlsx, .ppt, .pptx, .txt, .xml, .odt, .ott
• Images: .png, .jpg, .jpeg, .gif, .svg
• Fonts: .ttf, .otf, .woff, .eot
• Code: .js, .css
• Other: .zip, .rar, .psd, .mp3, plus all video formats
• Submissions expire after 90 days.
• Files are not added to the Media Manager.
• Phone Number Field:
• Validation checks for proper formatting.
• Valid characters: numbers, spaces, +, -, and periods.
• At least one number must be present.

reCAPTCHA

• Added by default to all forms to protect against spam and speed up the submission process.
• The reCAPTCHA icon appears in the bottom-left corner only when a visitor interacts with the form (clicks into a field).
• The icon disappears after submission or page refresh.
• reCAPTCHA cannot be disabled.

Best Practices for Form Design

To maximize usability and conversion rates, follow these guidelines when building forms:

• Keep it short: Fewer fields = more submissions. Only ask for information that’s necessary at the first touch.
• Group related fields together: Improves readability and makes forms feel less overwhelming.
• Avoid unnecessary long-text fields: Use sparingly; these fields slow users down and reduce completion rates.
• Label clearly: Use plain, descriptive field labels (e.g., “Phone Number” instead of “Best contact method”).
• Use required fields strategically: Mark only essential fields as required to reduce friction.
• Prioritize mobile experience: Review all forms on mobile devices to ensure spacing, field size, and button placement work well.