Skip to content
A Dutch company, based in AmsterdamDutch company · Amsterdam
Questions? Call us+31 6 15 42 58 11
EN
Guide

Site photos and measuring visits in the request

Why terrace photos change the first pergola or veranda quote, how booking a measuring visit in the form reduces phone tag, and how customer uploads are kept private.

4 min readUpdated By the Next Configurator team

On this page · 6 sections
Key takeaways
  • A few terrace photos often let you quote without a visit, or shorten the visit.
  • Keep photos optional and cap them at about five images.
  • Let customers book the measuring visit in the form, against your real calendar.
  • Re-encode uploaded photos on the server so EXIF and GPS data are removed.

Two optional additions to the quote request form change the first quote more than any other: a few photos of the terrace, and a measuring visit booked straight from your calendar. Photos give the quoter the site context a phone call can’t, and in-form booking removes days of phone tag. This guide covers why photos matter, why both should stay optional, how slot booking works, and how customer photos are kept private.

Why photos change the first quote

A customer’s own description of their terrace (“it’s about 4 by 3, there’s a step down to the garden”) is rarely enough to quote confidently. A handful of phone photos (the terrace itself, the house wall the pergola or veranda would attach to, any existing structure, the approach for delivery) tell a quoter things a text field can’t: whether the wall can take a fixing, whether there’s a step or slope that affects installation, whether access for materials is tight. For many requests, photos are enough to firm up a quote without a visit at all; for others, they at least tell you what to look for when you do visit, which shortens the visit itself.

Keeping it optional

Photos should never be required to submit a request. Some customers won’t have good photos ready, some are on mobile with limited data, and a required upload step is exactly the kind of friction that causes partial-form abandonment right before a submit. The right default is: offer it, cap it at a handful of images (five is a sensible limit), and let the customer skip it. Most customers who have their phone in hand while configuring a 3D pergola will happily add two or three photos if it’s one tap, not a form validation blocker.

Measuring visits: booking in the form, not after

The traditional sequence (customer requests a quote, staff member calls to find a time, back-and-forth over email or voicemail to settle on a slot) can burn days before a visit is even scheduled, independent of how busy your calendar actually is. Putting a visit-slot picker directly in the request form, showing real availability from your own calendar, collapses that to one step: the customer picks a date, sees actual open slots (filtered to showrooms or technicians that do home visits), and the visit is booked the moment they submit the request. This matters most during the spring peak, when both demand and calendar contention are highest. A customer picking their own slot removes an entire round of scheduling emails from your team’s load exactly when they have least spare time for it.

Keep the visit step optional and conditional: not every quote needs one, and forcing it onto customers whose job can be quoted from photos and measurements alone just adds a delay they didn’t need.

Privacy: strip EXIF and location data

Photos uploaded from a phone commonly carry EXIF metadata, including GPS coordinates of where the photo was taken. Information a customer submitting a quote request did not consciously choose to share and shouldn’t have to worry about. Any photo upload in a quote request should be decoded, validated as an actual image (not a disguised file), resized to a sane maximum, and re-encoded before storage, which strips metadata as a side effect, not as an afterthought. This matters both for customer trust and for straightforward data-protection hygiene; it’s worth checking any tool you use for this actually does it, rather than storing the raw upload as submitted.

Summary

Addition Problem it solves Keep it
Terrace photos (optional, capped) Quoter lacks site context without a visit Optional, max ~5 images, stripped of metadata on upload
Measuring-visit slot booking Scheduling a visit takes days of back-and-forth Optional, shown only when your process needs a visit, booked against real calendar availability

Where this fits

This is one piece of the request-form design that determines how good your first quote can be. See how to sell pergolas, verandas and carports online for the funnel it sits in, and photos and visits for the mechanics. It also feeds directly into hitting the 24-hour rule: a booked visit slot sent within hours is a strong substitute for a firm quote when one genuinely isn’t possible yet. See pricing or apply for a walkthrough.

Questions, answered

Still deciding? We'll walk you through it with your own product.

Book a walkthrough
How many photos should I ask for?

A handful is enough. Five is a sensible cap. More than that adds upload friction without adding much quoting value; the goal is site context, not a full survey.

What if a customer doesn't want to share photos?

Let them skip it. The form should work identically without photos; they’re an enhancement to quote accuracy, not a requirement to submit a request.

Does booking a visit in the form replace the visit itself?

No. It only removes the scheduling friction. The visit itself still happens, and for jobs that need one, the firm quote still follows the visit rather than the initial request.

Is it safe to store customer-uploaded photos?

Yes, provided uploads are validated as genuine images, resized, and re-encoded on the server before storage. This process removes EXIF and location metadata as part of normal handling, not as a separate step that can be skipped.

Live in three minutes. Yours for €499 a month.

14 days free, then one plan with everything in it. Live in about three minutes. Cancel any month.