Privacy-first local workflow
Collect only what you need to answer a customer enquiry
A short enquiry form can create a large responsibility if it asks for more than the team needs. Start with the action you can complete, ask for the minimum information and make the next step understandable before someone sends a message.

Write the purpose before the fields
For each field, write the immediate purpose: reply to a question, confirm a booking or prepare a quote. If the purpose is only ‘it may be useful later’, leave the field out.
Avoid asking for sensitive details in a general contact form. If a service genuinely requires special information, use an appropriate process, explain why and seek the necessary consent or professional advice.
Explain what happens next
Near the form or contact option, say who receives the message, how it will be used and when a customer can expect a reply. Do not describe a response time your team cannot maintain.
Do not convert an enquiry into continuing marketing by default. Give people a clear, separate choice for promotional updates and a simple way to withdraw it.
Keep access narrow and tidy
Use a shared, approved inbox or system rather than forwarding customer messages through personal accounts. Limit access to people who need it for the enquiry and avoid copying a message into several tools without a reason.
Set a review date for old enquiries. Information that is no longer needed should not remain simply because nobody owns the cleanup routine.
Treat this as a practical baseline
Australian privacy obligations can depend on the business, information and context. This is not legal advice or a statement that a business is exempt from, or compliant with, any law.
OAIC guidance emphasises collection that is reasonably necessary and data minimisation. Check your actual obligations and provider arrangements before changing how you collect or store customer information.