A customer information system can begin with a modest idea: staff should be able to find the last agreed action without searching several inboxes. Turning that idea into a small pilot is more useful than importing every contact into a new platform immediately. An Albany business can learn whether the arrangement helps a real task while keeping the experiment limited and reversible.

The questions below deal with an internal customer record pilot, such as tracking service enquiries. They do not assume that more information is always better, or that a successful demonstration proves a system is ready for every department and customer.

What problem should the pilot answer?

Write the problem as something staff can observe. A useful question is whether an authorised colleague can find an unresolved enquiry and identify its next action. Increasing engagement is too broad to tell the team what to test.

Choose one type of work and specify its beginning and end. For example, the pilot might start when a service enquiry is received and end when a staff member provides an answer or records why another response is needed. Keep marketing campaigns and payment processing outside that scope unless they are essential to the selected task.

Which information belongs in the trial?

Start with invented records that cover ordinary and awkward cases. Include two customers with similar names, a changed phone number and a request that has been reopened. These examples reveal weaknesses in matching and status labels without circulating genuine personal details.

For each field, explain what decision it supports. A preferred contact method can help staff respond appropriately; an unrestricted notes box can encourage unnecessary commentary. Avoid collecting sensitive details simply because the software offers a place to store them.

State Records NSW’s system-design guidance considers information needs, accuracy and future access. It is a useful design reference, not a statement that NSW government recordkeeping rules apply to a private WA business.

Who should be able to see or change a record?

Define roles before inviting the team. Someone answering an enquiry may need to read the relevant history and update its next action, while a system administrator may manage accounts. Those are different jobs and should not automatically have identical permissions.

Test access with an ordinary staff account as well as an administrator account. Check whether search results, exports, notifications and mobile views reveal information beyond the intended role. Restrictions on the main record screen may not cover every route to the data.

Decide who approves new users and removes access when the pilot finishes. If an external supplier helps, specify the records it may inspect and use safe examples whenever possible.

Can a small business assume privacy law is irrelevant?

No. The OAIC’s small business guidance explains that coverage has exceptions and provides a checklist. Determine the business’s actual obligations rather than relying on size alone. Seek suitable advice if the pilot involves sensitive information or an unfamiliar disclosure.

Regardless of the final legal assessment, staff need clear instructions about collection, access and sharing. Before introducing genuine customer information, understand the provider’s use of it, the location and arrangement of storage, and the procedure for correcting a mistake. A free trial is still an information-handling arrangement.

How should staff test the daily task?

Give participants a task and let them try it without being guided through every click. Ask one person to create the enquiry and another to continue it later. Observe whether the second person can identify what has already been promised.

• Find the correct customer among similar names.
• Record an agreed follow-up without overwriting history.
• Hand the enquiry to another authorised person.
• Correct a mistaken entry and understand what changed.
• Retrieve an unfinished item after signing in on another approved device.

For an Albany team covering enquiries from the Great Southern, include a service-area question and a customer who needs a phone response. The system should preserve those practical distinctions rather than reduce every request to the same generic sales stage.

What makes the pilot reversible?

Agree where the authoritative record lives during the trial. Running two uncontrolled copies can produce conflicting promises. If a limited live test is justified, define which records enter it and how other staff will know where to look.

Test a usable export and inspect what it contains. Check attachments, dates, ownership and outstanding actions, not just names and email addresses. Record the steps needed to end access and handle trial information appropriately when the exercise concludes.

When is there enough evidence to expand?

Compare the original problem with observed results. Record time spent finding information, corrections required and unresolved access or privacy questions. A positive staff impression is useful feedback, but it does not replace evidence that the task can be completed accurately.

Expand only after assigning owners to remaining issues and confirming the ongoing workload. A small pilot has done its job when it produces a clear decision, including a decision to change the design or stop.