Templates for file requests
Configure reusable file requests: recurring document asks (meter photo, heating-system label, ID copy, proof of ownership) that customers upload directly into their project through the customer portal or the Energy House lead funnel.
File requests are how you ask a customer for a document and have them upload it straight into their project. There are two surfaces: the Energy House funnel, where image requests appear automatically after a homeowner submits the public form, and the customer portal, where you create ad-hoc requests on an individual project for walk-ins, referrals, and mid-project asks. Both result in files in the project's file list.
Who this is for
Company admins setting up the image-request library on the Energy House funnel. Account managers create per-project file requests on individual customer projects.
Before you start
- You need the Admin role for the company-wide Energy House configuration. The per-project customer-portal file-request flow works for the Editor role too.
- Decide which document categories you ask for repeatedly. Three to five requests is the typical working set.
- Have example images ready where possible. Homeowners follow visual examples more reliably than text descriptions.
Configure the funnel-bound image requests (Energy House)
For requests that appear automatically after a homeowner submits the public Energy House form. You need the Editor or Admin role; the controls are read-only for the Viewer role.
- Open the Energy House configuration under Settings > Lead generation > Energy house.
- Click Add (the + button, top right). A new draft request opens for editing.
- Fill Name (max 50 characters), for example "Meter cabinet photo". This is the label the homeowner sees.
- Add a Description (max 150 characters, optional) clarifying what to photograph.
- Drop an Example image into the upload area. The homeowner sees this as a visual guide.
- Set Display for: the component package(s) this request applies to (Solar, Storage, Wallbox, and Heatpump where available). The request only appears to homeowners who selected one of these.
- Set Required for: the subset of those packages where the upload is mandatory rather than optional. You can only mark a target required once it is selected under Display for.
- Click Save. Saving an active request asks you to confirm.
- Back in the list, flip the request active with the on/off switch to make it live, and confirm "make public".
To reorder how homeowners see requests, drag the rows. To remove one, use the row's Delete action. Use the Preview (eye) button to see exactly which requests a homeowner gets per package.
The request appears on the homeowner's post-submission confirmation page, and uploads land in the project's file area. See the Energy House article for the surrounding funnel flow.
Configure the per-project file-request flow (customer portal)
For requests that don't come through the Energy House funnel (walk-in leads, referrals, mid-project asks, post-deal handover photos):
- Open the customer's project in the Portal.
- Navigate to Files / File Requests.
- Click New file request.
- Fill Title (what the customer should upload) and Description (optional clarifying text).
- Set Allowed file types: Image, PDF, or a combination.
- Toggle Allow many if the request accepts multiple files.
- Click Create. The request is added to the project's File Requests list.
- From the File Requests list, use the request's send / publish action to make it visible to the customer. Confirm the customer portal is activated for the project, then share the customer-portal link.
The customer logs into the portal, sees the request under File Requests, uploads from phone or computer, and marks the request complete. The upload appears in the project's file area, tagged as customer-uploaded.
Pro tip: Build per-project requests by copying from a previous project, or keep a short "quick start" list of the Titles you reuse most so each new project's set goes up fast.
Things to know
- Two surfaces, one outcome. Energy House image requests appear automatically after the homeowner submits; customer-portal file requests are per-project ad-hoc. Both result in files in the project file list.
- Energy House requests are tailored to the homeowner's selection. A request set to Display for: Solar only shows to homeowners who picked a solar package. Toggling a request off stops it appearing on new submissions; requests already in flight are unaffected.
- Add visual guidance to portal requests in the Description. Example images attach to Energy House funnel requests; for a customer-portal request, describe what to capture in the Description field or link a tutorial.
- Follow up after publishing. Once a request is published, check the project file area and nudge the customer if they haven't uploaded within your expected window.
Need help?
- Step-by-step questions about file requests → contact your Reonic account manager.
- Feature requests (a company-wide reusable template library, auto-reminders, example images in the portal flow) → drop a note to your account manager.
- Bug reports → include a screenshot and the project URL where the issue happened in your support email.
Last updated on

