Let customers add photos to a quote request when those pictures help you decide what to do next. Keep the upload optional for an ordinary first enquiry, explain what to photograph and give people a way to send the request without images. A useful description and a working reply address are often enough to start the conversation.
Before adding the field, decide who will view the pictures, where they will be stored and what happens if an upload fails. For a decorating or repair business, a couple of well-chosen images can help plan a conversation or visit. Asking for a complete photo survey on a phone can make the first contact unnecessarily difficult.
Ask for pictures that change the next step
Write down what you expect to learn from the image. A room overview may show the scale and access; a close-up may show the area the customer wants you to inspect. Neither necessarily establishes measurements, the underlying cause of damage or the full scope of work.
For a hypothetical decorating enquiry, helpful field copy could read:
Photos of the work area — optional. If convenient, add one view of the room and one close-up of the area you want us to look at. You can send the request without photos and discuss them with us later.
Tell customers to leave people, private paperwork and unrelated parts of the property out of the picture. Do not ask them to climb, dismantle anything or enter an unsafe area to obtain a better angle. If a photograph would require that, arrange the appropriate inspection instead.
A photo request should fit the rest of the form. The quote-form guide for Formby tradespeople covers the initial contact details, job description and location. Add uploads after those essentials, with a clear indication that they are optional.
Set limits customers can understand
Choose the accepted file types, maximum size per file and maximum number of files together. Display those limits beside the upload field before the customer selects anything. Avoid a vague “file too large” error that leaves them guessing what would work.
For example, “Up to two JPG or PNG photos, 5 MB each” is clear field copy if those are the limits your developer has configured and tested. Those numbers are an illustration, not a recommendation for every business. Try representative pictures from the phones your customers are likely to use before deciding the final allowance.
Check the actual files offered by the phone’s camera and photo picker. If a format is unsupported, the error should explain the accepted choices and let the person continue without it. Do not tell customers merely to rename a file’s extension: that does not convert its contents into the required format.
WPForms’ upload-field documentation describes controls for allowed extensions, file size and multiple files. The server also places limits on uploads. Ask your developer to check the installed plugin version and licence, then test the complete request against the hosting limits; a setting in the form editor does not establish that every permitted combination will succeed.
Include a remove-or-replace action so someone who picks the wrong image can correct it before sending. An error should stay beside the relevant field and preserve the job description. The customer should not have to type everything again because one photo was rejected.
Decide who can open the files
Choose between receiving pictures with the first enquiry and requesting them later through an agreed channel. Collecting them immediately suits straightforward, low-sensitivity job photos. Asking later can be preferable when you first need to establish scope, when files are large, or when the material needs tighter access controls.
If the website accepts uploads, give the developer a clear brief for private retrieval. A file being absent from the page or having a long URL does not establish that only your team can open it. Ask them to demonstrate what an unauthorised visitor sees when attempting to open a test file.
WPForms documents file-access restrictions and distinguishes its own upload storage from saving files in the WordPress Media Library. Check which mode the form actually uses and who has access. Do not assume that every upload inherits the privacy of the form entry containing its link.
The developer’s technical review should cover accepted file types, server-side validation, size limits, safe storage, access controls and suitable scanning or processing. OWASP’s file-upload guidance explains why checking an extension alone is insufficient. A public upload field requires several protections working together; a list of allowed image formats is only one part of that implementation.
Keep sensitive documents out of a general job-photo form. If your work genuinely requires them, agree a separate collection and access process before inviting customers to send them.
Plan storage and notification together
Decide whether the staff notification should contain an attachment or a link to a protected file. Attachments create additional copies in mailboxes; a protected link requires the recipient to have working access. Test the chosen route with the person who will actually handle enquiries.
For an illustrative workload of 100 enquiries, each containing two 5 MB photos, allow 1,000 MB for the uploaded files before any additional copies. Keeping files indefinitely can turn a small form feature into a growing storage commitment.
Agree when unsuccessful enquiries and completed-job images will be reviewed or removed, taking account of the records your business needs to retain. Record where copies exist: form storage, mailboxes, downloaded job folders and backups can follow different lifecycles. Have the website maintainer confirm what deleting an entry actually removes in your setup.
Use the WordPress storage-planning guide if uploads will become a significant part of the site. Establish the expected workload before paying for extra hosting capacity.
Also test a notification with photos and one without. If the form accepts the enquiry but the message never reaches the recipient, follow the enquiry-delivery diagnostic.
A practical brief before the form goes live
Give your designer the purpose of the photos, the agreed formats and limits, the person responsible for viewing them and the alternative route for customers who cannot upload. Then ask for a demonstration using harmless test images, with no real customer’s property or documents involved.
- No photo: the enquiry can still be sent and the recipient understands that images may follow later.
- Ordinary phone photos: the customer can select, remove and replace files; the received pictures are useful at the intended viewing size.
- Wrong format or oversized file: the message names the problem and gives a usable next action without losing the other answers.
- Interrupted upload: the form does not falsely announce that the whole request succeeded. The customer can retry or use the agreed alternative.
- Staff access: the right person can open the accepted files, while the agreed restrictions prevent unauthorised access.
- Confirmation: the wording reflects what the system accepted and explains the next human step. Photos do not turn a request into a confirmed quote or booking.
Repeat the relevant checks on both a phone and desktop. Keep the agreed limits and test result with the website handover so a later form or hosting change can be checked against the same requirements.
For a Formby, Freshfield or L37 business planning this enquiry journey, tell Formby Web Design what you need to learn before quoting. A description of the work and your current website are enough to start discussing a practical form.
