Smart Home Consultation Request Form: What to Ask Before the First Project Call

Overview

A smart-home enquiry form has one job: give the integrator enough context to make the first conversation useful.

It should not make the homeowner specify a complete system, count every keypad, choose cable types, or calculate a budget for equipment they do not yet understand. It also should not imply that a form submission produces an instant design or final quote.

Use the field list below as an intake blueprint. The exact field types, branching, uploads and validation available on a live site depend on the form implementation; this Guide does not claim that every suggested control is a native OneStudio form feature.

For most integrators, a useful first-step form answers:

1. Who is the project for?
2. Where is it?
3. What stage is the property in?
4. Which systems matter?
5. What happens next?

Decide what the CTA means

Common CTAs include:

Those are not identical.

If the company reviews every enquiry before offering a meeting, use Request a consultation rather than Book installation.

If a real discovery-call calendar is connected to published availability, the visitor can choose a time through a true booking flow. OneStudio publicly supports services, working hours, available times and website booking on relevant plans. See OneStudio features and pricing.

• Request a consultation
• Discuss your project
• Book a discovery call
• Start a smart-home project
• Request a site survey
• Talk to an integrator

Field 1: name

Ask for the person who should be contacted.

Recommended: Full name

Keep it simple.

Field 2: email

Email is useful for:

Ask for:

Email address

• consultation confirmation;
• non-urgent follow-up;
• requesting additional project information;
• sharing the next step through the business's normal process.

Field 3: phone

High-ticket projects often benefit from a direct call.

Ask for:

Phone number

If the company uses SMS, obtain the permissions required by its actual messaging setup. Do not turn a project enquiry into automatic marketing consent.

Field 4: project location

Location determines service coverage and can influence project logistics.

A first-step form may ask for:

For a first consultation, postal code is often enough to verify territory.

Avoid collecting a luxury homeowner's exact address unnecessarily before the company needs it.

• city;
• state/region;
• ZIP/postal code;
• full address only when genuinely needed at this stage.

Field 5: project type

A short selector can immediately improve qualification:

Different project types have different timing and design constraints.

• New build
• Renovation
• Existing home upgrade
• Inherited / existing smart-home system
• Commercial project
• Builder / developer project
• Other

Field 6: property type

Depending on the integrator, useful options can include:

Use only categories the firm serves.

• single-family home;
• apartment / condo;
• multi-residential;
• vacation / second home;
• office;
• hospitality;
• retail;
• other commercial property.

Field 7: project stage

Project timing matters enormously for technology integration.

Useful options include:

This often tells the integrator more than asking for an arbitrary desired start date.

• Early planning
• Architect / designer stage
• Plans in progress
• Pre-construction
• Framing / rough-in approaching
• Renovation underway
• Property complete / retrofit
• Existing system needs upgrade or support

Field 8: systems of interest

Use multi-select choices that match real capability:

"Not sure yet" is important. A homeowner should not need to know the solution before the consultation.

• Whole-home automation
• Lighting control
• Motorized shades
• Home theater
• Multi-room audio/video
• Wi-Fi / networking
• Surveillance
• Security integration
• Access control / intercom
• Climate integration
• Structured cabling
• Existing-system upgrade
• Not sure yet

Field 9: existing platform, if relevant

For retrofit or support requests, ask:

Do you already have a control or AV system?

Options can include:

Only include brands the firm is willing to discuss or support.

Do not imply the business is authorized for every brand in the list.

• No, this is a new system
• Control4
• Crestron
• Lutron
• Savant
• KNX
• Other
• Not sure

Field 10: project goals

A plain-language open field can be more valuable than a technical checklist.

Prompt:

What would you like the home or space to do better?

A buyer may say:

These goals give the integrator context without forcing premature design decisions.

• simplify lighting;
• improve Wi-Fi;
• hide AV equipment;
• automate shades;
• create a theater;
• integrate an existing alarm;
• control the whole home from one interface;
• replace an unreliable system;
• coordinate technology before construction.

Field 11: timeline

Ask for the desired timing in broad ranges:

A form should not promise completion by that date.

• Just researching
• Within 1–3 months
• Within 3–6 months
• Within 6–12 months
• More than a year away
• Construction date is already set
• Need support for an existing system

Field 12: professional team involvement

For construction projects, ask whether other professionals are already involved:

This helps the integrator understand coordination needs.

Do not request contact details for those professionals until necessary.

• Architect
• Interior designer
• Builder / general contractor
• Electrician
• Lighting designer
• Developer
• None yet

Field 13: plans available

A simple yes/no field can help:

Are architectural or electrical plans available?

Do not automatically invite plan upload through a public form unless the implementation has been specifically reviewed for secure document handling.

The team can provide the approved submission method later.

• Yes
• No
• In progress
• Not applicable

Field 14: budget range, only if the business truly uses it

Budget can prevent mismatched expectations, but it can also feel abrupt when used badly.

Include it only when the integrator has a clear qualification reason and useful ranges based on real projects.

Possible wording:

Do you have an expected technology investment range?

Include:

as a legitimate option.

Do not use a budget field to imply that the website can price the design automatically.

• I need guidance

Field 15: consultation preference

If the business offers several first-step options, ask:

Do not list a meeting type the company does not actually offer.

• Phone call
• Video call
• Showroom visit
• Site consultation
• Please recommend the best next step

Field 16: preferred consultation time

If the company is not using live booking, label dates as preferences.

Use:

Preferred days / times for a call

If the company does use live booking for discovery calls, present actual available slots and make it clear what is being booked: a consultation, not the installation project.

Keep support requests separate from new-project enquiries

An owner with an existing broken Control4 or network system has different needs from a new-build prospect.

A support branch can ask:

Do not promise remote troubleshooting or support for third-party systems unless the integrator genuinely provides it.

• existing customer or new customer;
• current platform;
• broad issue;
• property location;
• whether the system was installed by the company;
• best contact information.

Keep builder and architect enquiries concise

Professional partners may need a different branch.

Useful fields:

The goal is to start coordination, not reproduce a consultant's project brief in the browser.

• company;
• role;
• project location;
• project type;
• current stage;
• estimated construction timing;
• technology scope;
• whether plans are available;
• short notes.

Do not collect security-sensitive project details publicly

Smart-home projects can include surveillance, access, networking and alarm integration.

Avoid asking for public-form submission of:

Those belong in controlled project workflows, not marketing intake.

• alarm codes;
• gate codes;
• IP addresses;
• Wi-Fi passwords;
• camera positions in sensitive areas;
• detailed security drawings;
• remote-access credentials;
• device passwords;
• network credentials.

Do not let the form make engineering decisions

Avoid questions that pretend the visitor can determine:

Collect project context. Let qualified professionals design the system.

• cable categories and topology;
• circuit and lighting loads;
• panel architecture;
• wireless access-point placement;
• acoustic treatment design;
• camera coverage;
• rack thermal requirements;
• automation processor sizing;
• system compatibility;
• compliance requirements.

Explain what happens after submission

A useful confirmation can say:

Thanks for telling us about your project. Our team will review the location, project stage, systems of interest and timeline, then contact you to confirm the best next step. Submitting this form does not create a final system design, project price or installation date.

Adjust the language to the company's actual process.

Keep CRM expectations accurate

OneStudio publicly supports client records, contact details, interaction history, related bookings, notes and labels. For an integrator, that can support ordinary contact continuity around consultation enquiries.

Do not describe OneStudio as:

Specialist tools can remain in place behind the website.

• a sales-pipeline CRM;
• proposal or estimating software;
• CAD or design software;
• project management;
• device inventory;
• ticketing;
• remote monitoring;
• commissioning software;
• field dispatch;
• lead scoring.

Example first-step smart-home consultation form

Final consultation-form checklist

Before publishing, verify that:

The best consultation form does not design the smart home. It gives the integrator enough context to begin designing the relationship.

• service geography is clear;
• system choices match real capability;
• brand lists do not imply unauthorized dealer status;
• "not sure" options exist for non-technical buyers;
• project stage is captured;
• sensitive security/network information is excluded;
• plan upload is not claimed without a reviewed implementation;
• preferred times are not presented as confirmed installation dates;
• budget is used only when the company truly needs it;
• submission does not imply instant design or pricing;
• the confirmation explains the actual next step.

Make the first consultation more useful

OneStudio can support the public website, enquiry path, scheduled consultations where appropriate, and ordinary client context while system design and project delivery remain in the integrator's specialist workflow.

Explore OneStudio features, OneStudio solutions, and pricing.