Feed-in remuneration felt hard to reconcile.
One reviewer said the app’s calculation was “a mystery,” comparing the displayed amount with exported kWh. Paraphrased from German.
Signal: earnings need traceable inputsIndependent concept · Solar customer support · 2026
When earnings look wrong, help support agents explain what’s known.
A concept workspace for investigating a homeowner’s question: “Why were my earnings lower than expected for September?” It helps an agent trace the amount, check data quality, and respond without guessing at the cause.
Design premiseDon’t turn an unexplained number into a confident explanation.
Give the agent a clear path to verify the earnings definition, meter data, remuneration terms, and settlement—then communicate what is and isn’t known.
01Discovery · Public signals
Two customer questions point to an explainability gap—not a proven support workflow.
Enpal publicly describes its app as showing production, consumption, savings, and earnings. Recent public app reviews raise two related questions: can customers reconcile displayed remuneration with exported energy, and can they trust production data when different views appear inconsistent?
Production and consumption figures did not sync.
A reviewer reported that the app’s yield and consumption data were not synchronising correctly on several days.
Signal: data freshness and consistency matterWhat this does—and doesn’t—tell us. These are two self-selected public reviews, not representative research. They motivate a problem hypothesis; they do not establish prevalence, root cause, customer-operations procedures, or how Enpal staff currently resolve cases.
Observed publiclyQuestions about earning calculations and data consistency
Design hypothesisSupport agents need to trace displayed amounts to their underlying records
02Concept · Support workflow
A case workspace that separates customer expectation, energy data, and remuneration.
The example is a fictional case dated October 2026, about September 2026. All customer details, values, statuses, and account information below are invented for the design exercise. The interface is a workflow proposal—not an Enpal internal tool or a description of its systems.
September earnings lower than expected
Customer asks why the September amount shown in the app is below their expectation.
Displayed for September
€62.40Concept: current app figureCustomer expected
~€90Based on customer recollectionExport data coverage
89%27 of 30 days in this scenarioCASE CONTEXT · SYNTHETIC DATA
Not reconciledSeptember earnings need a source check
HighLow
17–19 Sep · no readings in sample
01 Sep15 Sep30 Sep
Synthetic exported-energy trendIllustrative only · not an Enpal data export
INVESTIGATION CHECKLIST
0 / 4 checkedWhat the agent needs to verify
- 1What does the €62.40 represent?Estimate, earned remuneration, or settled payment?Unverified
- 2Are meter and export records complete?Check the three-day gap against the source meter feed.Unverified
- 3Which remuneration model applies?Confirm contract, activation, and period rules.Unverified
- 4Does the settlement reconcile?Compare the app figure with the billing or market record.Unverified
No root cause established. Missing readings are a lead to investigate—not proof that they caused the lower amount.
Concept UI · not an Enpal product screenTry the tabs: Overview · Earnings data · Activity
01 · UNDERSTANDWhat does “earnings” mean here?Estimate, remuneration, or settled payment?
02 · VERIFYAre the source records complete?Meter export, data freshness, contract terms.
03 · RESPONDExplain what’s known—or hand off.Agent-approved reply with no unsupported diagnosis.
03Design decisions · Trade-offs
The interface is designed to prevent premature certainty.
Separate production, export, earnings, and payment.
Why: They describe different parts of the energy and remuneration journey. A homeowner’s “earnings” may not mean a settled payment.
Trade-off: More distinctions add cognitive load. Group the values, but label the relationship and source rather than collapsing them into one number.
Show data coverage and freshness beside the figures.
Why: A monthly total is hard to interpret when days are missing or feeds are delayed.
Trade-off: Completeness is a signal to investigate, not proof of causation. The UI must show gaps without asserting they explain the amount.
Keep the agent in control of explanation and escalation.
Why: Public information doesn’t expose the account’s actual tariff, activation state, meter, or settlement records.
Trade-off: A human review is slower than an automated answer, but avoids making a false promise or diagnosing from incomplete evidence.
04What I’d validate next
Test whether agents can reach a safe, useful next step—not just find a number.
I could not interview Enpal or solar customer-support staff for this concept. The current workflow is therefore a hypothesis. Before claiming it improves support, I would test it with agents from a solar provider or a comparable energy-service team, using realistic cases and synthetic customer data.
Can the agent distinguish the amount types?
Ask the agent to explain the difference between displayed estimate, remuneration, and settled payment—and identify which source record is missing.
Can they avoid a false diagnosis?
Introduce incomplete meter data and ask what can be stated, what remains uncertain, and when to route the case to a specialist.
Does the next team receive useful context?
Check whether the handoff includes the customer’s question, evidence already reviewed, unresolved checks, and the promised follow-up.
Candidate measures · only after testing
Correct evidence identifiedUnsupported causes statedAppropriate escalationRepeat customer contact
05Boundaries · Sources
A grounded concept, with its unknowns kept visible.
Known from public sources
- Enpal publicly describes app features for viewing production, consumption, savings, and earnings.
- Enpal explains that its remuneration and state feed-in remuneration are different models; the applicable details matter.
- Two public reviews raised concerns about earnings calculation clarity and production-data consistency.
Unknown in this concept
- Enpal’s internal support tools, case categories, team structure, service levels, and handoff rules.
- The fictional customer’s actual account, contract, meter readings, and remuneration calculation.
- Whether a data gap caused any difference in earnings—or whether the designed workflow would improve outcomes.
01
Enpal app · Google Play listing and public reviewsReview excerpts accessed October 2026 · self-selected, anecdotal signals
02Enpal · The appPublic product description of monitoring, savings, and earnings
03Enpal · Remuneration and feed-in remuneration explainedPublic explanation of Enpal remuneration, direct marketing, and factors affecting amount
04Verbraucherzentrale · Who does what in the energy market?Consumer guidance on supplier, grid operator, and metering roles
Independent portfolio concept · not commissioned, endorsed, or validated by Enpal. All account and case data in the workspace are synthetic. No customer, company, or operational system data is represented.