I Used the Portal. Show Me What Happened to the Complaints.
18 November 2026 · Services Australia portal audit and follow-up
I am talking about the complaints, feedback and written enquiries I put through the Centrelink portal. The submission history is there. What I want to see beside it is the handling history: who received each item, what they called it, where they sent it, and what answer actually went back to me.
A date, a filename and a receipt do not answer those questions. Neither does a general statement that I have contacted the agency repeatedly. If the agency counts my contacts, the record should also let us follow what happened to the matters raised in them.
This continues the 128-entry portal audit and its companion, The Portal Remembers Everything Except the Answers. It concerns Services Australia portal submissions. The separate NDIA telephone-records matter does not supply the count for this story.
What the compilation actually contains
The schedule sent with my new FOI application on 16 November contained 128 provisional entries. The subsequent audit recorded eight transcription corrections and seven additional entries, bringing the provisional inventory to 135. The original sent attachment remains part of the record; correcting the published audit does not rewrite what was attached to that email.
Within the corrected 128-row schedule are 33 enquiry-letter entries, three customer-feedback entries and ten FOI access/change-form entries, alongside accommodation, rent-certificate and other supporting documents. Those are inventory categories, not findings that every item was a separate complaint or that all 128 required individual written replies.
The distinction matters. A document-upload history can show that I submitted something. It cannot, by itself, show whether the agency registered it as a complaint, treated it as supporting evidence, joined it to another case, marked it as a duplicate, or closed it. The FYI, feedback and complaints pathways need to be searched as well.
The photo-picker overview screenshots help locate the underlying images. They do not create additional submissions, and repeated screenshots must not inflate the count. The audit also carries a distinction between rows checked against images and earlier entries carried forward for verification. The backend records are needed to settle the inventory.
The follow-up has now been sent
At 9:19 am Melbourne time on 18 November, supplementary particulars were sent to the Services Australia FOI mailbox in the thread of the 16 November application. They expressly identify the issue as an FYI/feedback portal complaints and non-response audit. They ask for the complaint component to be associated with a separate Complaints Team registration.
The supplement asks the agency to trace each relevant enquiry, FYI item, feedback submission, customer-feedback document, enquiry letter and written complaint through the systems that actually handled it. It extends the requested audit trail through 18 November. It expressly preserves the earlier application rather than withdrawing or replacing it, and it does not consent to an extension of time.
For each item, the requested chain is straightforward:
- The original submission, timestamp, receipt and backend identifier.
- Its classification, any later changes, routing, and links to other matters.
- Acknowledgement, queue, allocation, viewing, assessment and escalation records.
- The actual response, including whether it was only drafted or was dispatched, by which channel, and with what delivery result.
- Any closure, duplicate, withdrawal, no-action or resolved status, with the recorded reason and authority.
A broader request for a consolidated complaint and reference register was also sent earlier that morning. It asks for reconciliation with the portal application. That is a related request, not evidence that all the references have already been joined correctly or that the portal scope has been surrendered.
An acknowledgement is one step in the chain
An agency email dated 17 November bears the acknowledgement reference LEX 96034. That is part of the correspondence record. Its general wording does not, on its own, establish exactly which application and scope it acknowledges. The supplementary request therefore asks the agency to identify the operative reference for the 16 November application and the separate complaint reference.
That acknowledgement is also different from an answer to the underlying portal complaints. A request can be acknowledged today while the handling of an earlier submission remains unexplained. Each step needs its own date and record.
I recall a callback. I am not turning that into a claim that nobody ever contacted me. The question is which submissions that call dealt with, what was decided, what remained open, and whether the agency recorded several unrelated written matters as resolved by one oral contact.
My reported experience is that substantive written answers are missing for matters I raised. The records checked for this update do not provide the item-by-item reconciliation needed to establish the full extent of that gap. The request is designed to test it: received, acknowledged, answered, closed without a written response, or still pending.
If the answer was sent, identify it and show the dispatch record. If the matter was merged, show the link. If it was closed, show the reason. If it is waiting, say where.
I have already done the work of bringing the portal entries together. The next step is to put the agency's handling and response records beside them. That is the follow-up now before Services Australia.
Source record: the 16 November 2026 portal inventory and sent FOI application; the corrected published portal audit; the agency acknowledgement dated 17 November; and the two sent requests dated 18 November. All times in this update are Melbourne time. Counts remain provisional pending reconciliation with source documents and agency records. Related context: Two Systems, One Citizen.