Managing social media accounts in Albany seemed straightforward to Elise until she drafted the customer information flow for a proposed adult pottery workshop. The planned promotion had one public post, but enquiries could arrive as comments or private messages with quite different questions.

Elise and the workshop in this story are fictional. The account review, sample messages and proposed arrangements are planning illustrations. No real customer information was collected, no event was advertised and no successful implementation is claimed.

A comment was not a booking record

Elise began by imagining a public comment asking whether a place remained. It was tempting to count the comment as interest and immediately move the person’s name onto an attendance list.

That would skip several decisions. The person might be asking for someone else, comparing dates or simply seeking information. An enquiry was not a confirmed registration, and a friendly response did not establish that the workshop had space.

Elise’s draft response process would keep the question at the enquiry stage. The separate booking process, once established, would need its own clear confirmation rather than relying on a comment beneath an advertisement.

The public page needed less detail than the organiser

A second invented message included a telephone number in a public reply. Elise did not want the planning method to depend on customers placing contact details where other visitors could see them.

The proposed public information would explain how to make an enquiry without requesting personal details in comments. Questions requiring individual information would need an appropriate private channel and an explanation of what was needed.

Elise read the OAIC’s information collection guidance, which explains collection purposes and notification responsibilities under Australian privacy law. She would need to check the obligations applying to the actual organisation rather than assume every small activity had identical legal coverage.

A useful list did not need the whole conversation

Elise sketched a proposed enquiry list beside the sample messages. Copying every sentence into a shared planning document would make it lengthy and could expose details that other helpers did not need.

The draft list instead identified the enquiry reference, the question requiring a response, its current status and the person handling it. Contact details would be held only where needed for the relevant work, with access considered separately.

A brief note could say that a person wanted clarification about the activity format. It did not need to preserve unrelated personal context simply because that context appeared in the original message.

Account access was different from responsibility to reply

A friend might help prepare promotional wording without needing access to every private enquiry. Elise could review a draft separately from allowing the friend to operate the account.

The Australian Signals Directorate’s account and identity guidance recommends MFA, unique passwords and access limited to what people need for their work. Elise would investigate the platform’s available roles before assigning access.

The proposed plan would not circulate a shared password in a group message. It would also identify who could confirm details to a customer, because technical access to an inbox would not automatically make every answer accurate or authorised.

A changed date could leave several versions behind

In the next fictional planning scene, Elise considered a possible change to the proposed workshop date. An old post, a draft message and a copied list could all retain the earlier version.

Rather than relying on memory, she would keep one current event details record and note which public or private communications might need attention if a change occurred. The record would distinguish a proposed change from a confirmed one.

This did not mean silently replacing every historical message. The practical question was which people needed an accurate update and which channels had already communicated the detail. No change or notification was actually carried out in the story.

A sample enquiry exposed the handover questions

Before a live event, Elise planned to walk through an invented enquiry with a helper. The exercise would ask whether someone could identify the next action without opening unrelated customer conversations.

  • What information has the person requested?
  • Has the relevant detail been verified?
  • Who is responsible for answering?
  • Does the reply contain only information appropriate to that channel?
  • Is the enquiry still open or genuinely resolved?

A completed response would not automatically mean a booking, attendance or satisfaction. Elise would keep those meanings separate instead of using one vague completed label for every stage.

The plan ended before any customer outcome

Elise’s draft now described a smaller, clearer flow from public information to individual enquiry and, where relevant, a separate registration process. Questions about the actual platform, privacy obligations and event arrangements remained to be resolved.

The fictional story ends with that proposed structure. It offers no claim that a workshop sold out, information was fully protected or account settings were changed. The next task would be to check the real arrangements before using them with customers.