Managing online enquiries in WA can start with a small pilot aimed at one identifiable problem. The business might want to learn whether clearer service-area questions reduce the time spent clarifying requests that arrive without enough location information.
Western Australia is not one uniform service market. A business’s capacity to assist someone can depend on the actual location, task and delivery arrangement. A useful pilot tests those distinctions without promising statewide coverage or collecting more personal information than the enquiry needs.
Problem: the idea is too broad to test
“Improve online enquiries” could mean increasing volume, reducing missing details, answering faster or attracting different work. These aims require different evidence and can pull the design in different directions.
Solution: choose a narrow question. For example, test whether a proposed form helps an authorised staff member identify the service requested and the area relevant to deciding the next step.
The business.gov.au market research guide recommends deciding what to learn, researching customer needs and recording findings and actions. A pilot can contribute to that learning without proving demand across the whole state.
Problem: a location field creates a misleading promise
A form may accept a town or postcode even when the business has not decided whether it can provide the requested service there. Customers can interpret an accepted submission as evidence of coverage.
Solution: explain what the enquiry process does. State that the business will assess the request against its actual service arrangements, where that is the process, rather than suggesting that every accepted location is automatically supported.
Ask for a suitable level of location detail at the initial stage. An exact residential address may be unnecessary if a broader locality is enough to decide whether further discussion is appropriate.
Problem: participants cannot understand what information is required
Internal terms such as zone, category or service tier may be familiar to staff but confusing to customers. Guesswork then produces records that look complete while conveying the wrong meaning.
Solution: give plain instructions and distinguish required from optional information. The W3C WAI forms tutorial explains the importance of instructions about inputs, formats and requirements.
Test whether participants understand those instructions without coaching. Good labels support use, but the business still needs broader accessibility assessment and suitable alternatives for people who cannot complete the proposed channel.
Problem: the sample contains only easy enquiries
A trial using complete, straightforward requests can miss the situations that consume the most staff time. It may show that the form works without showing that the workflow is useful.
Solution: include appropriate sample cases with uncertain service type, an unsupported location and missing information. Use fictional or suitably protected data and an authorised test arrangement.
Check what the receiving staff member does with each case. A vague request needs a clear clarification task; an out-of-scope enquiry needs an accurate explanation, not an invented referral or assurance that someone else will provide the service.
Problem: routing and responding are treated as the same result
An enquiry can reach the correct inbox but remain unattended. Alternatively, several people may answer it because nobody knows who owns the response.
Solution: assign one clear next responsibility and show whether the enquiry is received, being clarified or resolved. Any stated response expectation needs to match actual staffing and support arrangements.
Review the handover as well as the form. If a record loses its locality or service description when assigned, the pilot has exposed a downstream problem that another mandatory field may not solve.
Also check what happens when submission fails or its result is unclear. Provide an appropriate way to ask for help, and investigate the original enquiry before encouraging repeated submissions that could leave several staff members working on the same request.
Problem: the pilot expands before the team understands the evidence
A few encouraging cases can create pressure to add more service types, locations or channels. Each addition can change the questions the original pilot was designed to answer.
Solution: review the bounded findings first:
- The enquiry types and locations represented.
- The instructions participants understood or misread.
- The information staff needed to clarify.
- The cases routed and actually responded to.
- The effort and unresolved limitations observed.
- The specific next change or test proposed.
Keep the number of cases and their selection visible. A limited sample can reveal a useful problem without establishing a reliable conversion rate, statewide demand or a guaranteed reduction in workload.
Problem: the findings never change the process
A pilot report can become another file while staff continue using the same ambiguous instructions. The value of the test then disappears between observation and action.
Solution: choose a responsible person and a defined next step. That might be revising one location instruction, clarifying ownership or repeating the exercise with a previously untested request type.
A manageable WA enquiry pilot produces a better decision about the service people actually need. Wider use should follow demonstrated clarity and operational capacity, rather than the mere ability to publish another form.