adsoraAsk which work the homeowner wants
Separate replacement windows from glass repair, screen replacement, hardware fixes and new-construction requests where those are different programs. Ask how the capture form handles someone who is unsure. A general interest in better windows does not establish a specific replacement scope.
Use the same project labels in the source form, acceptance rules and CRM mapping. If one system sends replacement and another expects window_replacement, document the translation. Review the value your contact team sees so a technically accepted inquiry does not arrive under a confusing generic category.
Define the role of window count
If the buyer has a minimum project size, specify the threshold and how the count is collected. Make clear whether the number is the homeowner’s estimate or a later confirmed measurement. A form answer can help qualify interest, but it should not be represented as a final installation quote.
Agree what happens when the count is unknown. Some programs may accept the inquiry for qualification; others may require the field before purchase. Do not replace a missing answer with the minimum accepted number. That produces a record that satisfies the software while misrepresenting what the homeowner supplied.
Give the source a window-program specification
| Buying field | Definition to agree |
|---|---|
| Project type | Replacement and any other included work |
| Project size | Required count, units and unknown handling |
| Property type | Eligible residential or other building categories |
| Inquirer relationship | Accepted owner or authorized-party values |
| Service area | ZIP coverage by branch and product |
| Requested timing | The homeowner’s stated window for starting the project |
Keep optional preferences separate from acceptance requirements. A homeowner’s preferred material or style may be useful to the sales team without being a reason to reject the lead. Only make it a hard filter when the program has a clear, maintainable rule for it.
Check product coverage inside the territory
A company’s footprint may include branches with different product lines or project-size rules. Route using the service ZIP and the approved program, then identify the receiving branch. Test an overlap and an excluded market before opening traffic.
Review the source offer for any claims about energy savings, rebates, financing or installation timing. The receiving team should know what the homeowner saw and who approved the offer. A buying filter cannot fix a promise that the branch cannot support.
Review project fit alongside contact outcomes
During the pilot, record whether the team reached the homeowner, confirmed a replacement project, booked a visit and held it. Keep repair-only requests and below-threshold project sizes as separate reasons. Preserve the original form answer when the scope changes during the conversation.
Compare those outcomes by source, branch and requested project size. A branch receiving too many repair inquiries needs a different correction from one with an unworked call queue. Send Adsora your accepted window projects, minimum-size rule if applicable, ZIP coverage and receiving setup to scope the program.