Tree surgeon quote requests: the enquiry page and form spec
Short answer: Build one "Get a quote" page whose form asks for what you'd otherwise phone back to find out: what work, how many trees, rough height, how close to buildings or cables, access width, whether you take the waste away, and three or four photos. Add a map pin for rural or hard-to-find sites, let customers who need a visit book one of your survey slots, and route storm-damage emergencies straight to a phone number instead of the form. Then send a short, honest follow-up message so nobody wonders whether you got it.
Tree work is hard to price from a sentence. "Can you take down a big tree in my garden?" could mean a two-hour job with a chipper on the drive or a full day of rigging over a conservatory. The enquiry page's job is to close that gap before you pick up the phone, so you can quote some jobs from the desk, book visits for the rest, and stop driving out to look at hedges that turn out to be leylandii you can't reach.
Here's the blueprint: page layout, form spec, and the messages that go out afterwards.
Part 1: The enquiry page
Top of the page
- Headline that says what happens: "Send a few details and photos, get a quote or a survey visit."
- Your area covered, in plain words (towns and roughly how far you travel).
- A visible "Emergency? Call now" bar with a tappable phone number. Fallen trees on cars or roofs need a voice, not a form.
Below that
- The form (spec below).
- A small "What happens next" strip: we review photos, we either quote by email or offer a visit, we confirm a date.
- Three or four before-and-after pairs from your own jobs, each captioned with the work done ("crown reduction on mature oak", "stump ground below lawn level"). Real photos of your crew and kit do more than any stock image.
- Credentials and insurance details you can genuinely show, and a link to reviews.
A single neutral line belongs here too: some trees are protected or in conservation areas, so you check with the council before work where needed. That's all the page needs to say on it.
Part 2: The form spec
Each field earns its place by removing a question you'd otherwise have to ask.
| Field | Type | Why it's there |
|---|---|---|
| Name, phone, email | Text, tel, email |
Phone first; many customers prefer a call back |
| Site postcode | Text | Travel time and whether you cover it |
| Type of work | Checkboxes: felling, reduction, crown lift, pruning, hedge, stump grinding, other | Sorts jobs at a glance |
| Number of trees | Number | Quick sense of scale |
| Approx. height | Choice: under 5 m, 5–10 m, 10–20 m, over 20 m | People can't measure; ranges they can guess |
| Near buildings, roads, cables? | Checkboxes | Signals rigging, traffic or utility work |
| Access | Choice: open drive, side gate (with width), through house only, no vehicle access | Decides kit and labour |
| Waste | Choice: take everything away, leave logs, leave chip | Changes the price and the vehicle |
| Photos | File upload, multiple | The single most useful field |
| Notes | Text area | Anything else, including parking or dogs |
| Preferred timing | Choice: urgent, within a month, flexible | Helps you schedule and prioritise |
Photo upload, done properly
The HTML file input supports a multiple attribute so customers can pick several photos at once, and an accept attribute (for example image/*) to steer the picker towards images. MDN also documents a capture attribute that hints the browser to open a camera directly, but if you use it, phones may skip the gallery, which is where the customer's photos usually are. For most quote forms, leave capture off.
Under the upload, tell people which photos help: the whole tree from a distance with the house in shot, the base of the trunk, the access route from the road, and anything it overhangs. That guidance alone improves what you receive more than any extra field.
Keep upload limits generous, and resize on the server rather than rejecting large phone photos.
Map pin for rural jobs
Farms, field boundaries and long lanes don't map well to a postcode. Add an optional "drop a pin on the tree" map. Google's Maps JavaScript API has an official sample for a draggable marker that reports its position when the user finishes dragging (a gmp-dragend event), which your form can store as coordinates alongside the postcode. Keep it optional; plenty of urban customers won't need it, and the map needs an API key and setup on your side.
Part 3: Site-visit booking
Not every job can be quoted from photos. For those, offer the customer a survey slot rather than a back-and-forth about when you're free.
A scheduling tool is enough. Using Calendly as an example, as of November 2026 its help pages describe:
- Buffers before or after a meeting, with the availability check counting the meeting plus buffer. For survey visits, a travel buffer stops two visits being booked back-to-back on opposite sides of the county.
- Meeting limits per day, week or month for an event type, so you can cap surveys at, say, three a day and keep the rest of the day for climbing.
Show survey slots only after the form is sent, or for jobs flagged as large or complex, so you're not visiting every hedge trim in person.
Part 4: Emergency routing
Storm callouts don't belong in a queue. Three layers work well:
- The "Emergency? Call now" bar on every page during storm season.
- An "Urgent: dangerous or fallen tree" choice in the timing field that triggers an immediate text or email alert to whoever's on call.
- An out-of-hours voicemail or message that says when you'll call back and what to do if anyone is in danger.
Never promise a response time you can't keep on a bad night.
Part 5: The follow-up messages
Instant auto-reply (email or SMS): "Thanks, we've received your details and photos. We'll review them and get back to you by [day]. If the tree is dangerous, call us on [number]."
If you can quote from photos: Send the quote with a short description of the work, what's included (waste, stump, clean-up), and a link to book a date.
If a visit is needed: "From the photos, we'd like to see this one in person. Pick a time that suits you here: [link]."
If you need better photos: Ask for the one specific shot you're missing. Customers respond to "a photo of the side gate with something for scale" much faster than to "more photos please".
FAQ
Won't a long form put people off?
Long forms with pointless fields do. Fields that clearly relate to the job, with choices rather than typing, tend to feel like progress. Keep only name, phone, postcode, work type and one photo required, and make the rest optional.
Should I show prices on the site?
Tree work varies too much for fixed prices. Explaining what affects the price (height, access, proximity to buildings, waste) is more useful, and the form fields already teach that.
What about customers who just want to ring?
Keep the phone number visible everywhere. The form exists for people who prefer to send details, and for evenings and weekends when you can't answer.
Can I quote from photos alone?
Often, for straightforward pruning, hedges and small fellings. Anything near buildings, over roads or with tricky access usually still needs a look in person.
If you want your quote page to send you photos you can actually price from, show us how enquiries reach you now.