Customer enquiries are a useful source of article ideas because they reveal what people need to understand before deciding. The useful material is usually the question, not the customer’s identity or private circumstances. Extract that information need before sending a brief to an AI writing tool.
This guide proposes a privacy-conscious content workflow. Its examples are invented and contain no customer records. UK ICO guidance helps explain why replacing names is insufficient; the operational checklist is not a determination that any particular dataset is anonymous or lawful to reuse.
- 01Remove context that identifies people.Dates, locations and unusual circumstances can identify someone even after names are deleted.
- 02Brief the information need.A general customer question often provides enough detail to create a useful article.
- 03Review the output again.A careful input process does not remove the need to inspect what will be published.
- 04Record the tool arrangement you actually used.A statement about one subscription or deployment does not transfer to another; the record names the retention, training and access settings in force.
01 — Practical guidanceDistinguish a topic from a customer record
An enquiry might contain a useful question surrounded by contact details, an order history and personal circumstances. Start by writing the question in general terms. For example, “What should a buyer check before choosing a delivery window?” can be useful without preserving the specific customer’s address, travel date or reason for moving.
That example is synthetic. In a real workflow, the person preparing the brief should have an authorised reason to access the source and use it for the proposed purpose. Access for customer service does not itself settle whether a record can be reused in an external content tool.
The ICO’s pseudonymisation guidance explains that replacing identifiers does not necessarily change personal-data status. In particular, data remains personal in the hands of somebody who can reconnect it using additional information. Treat name replacement as one limited step, not an anonymity certificate.
02 — MethodReduce identifying detail before creating the brief
Use the table to review what the proposed article actually needs. Its purpose is to reduce unnecessary detail while preserving the problem a reader wants solved. It is not a formula that guarantees anonymity once every row is checked.
Combinations matter. A broad job title may become identifying when paired with a small town, an unusual incident and an exact date. Review the brief as a whole and consider what an informed reader could connect to other available information.
| Source detail | Useful content substitute | Question for the reviewer |
|---|---|---|
| Name, email or account number | Omit entirely | Does the article need any person-level identifier? |
| Exact date or address | General timing or location only if relevant | Could the remaining combination identify the event? |
| Rare personal circumstance | General problem or clearly synthetic scenario | Does the detail add necessary instructional value? |
| Verbatim customer wording | Paraphrased information need | Could the phrase be traced to a public complaint or post? |
| Private attachment or transcript | Minimal approved facts for the topic | Is uploading the original necessary and authorised? |
03 — The evidenceUse a brief that preserves the useful question
A practical brief can contain the audience, the question, the facts needed to answer it and the permitted source material. State that examples must be invented and labelled, and that the writer should not infer personal stories from sparse details. Keep the source enquiry outside the prompt when it adds nothing necessary.
For example, an illustrative brief might ask for an explanation of delivery-window trade-offs, with sections on access, availability and communication. It can specify a general household scenario without reproducing anybody’s booking record. The article can still answer a genuine recurring question.
When an agent can retrieve more information, limit the connected sources to the task. A narrow initial prompt does not prevent an overbroad retrieval step. Our agent-versus-workflow decision guide helps decide which source selection and publication steps need fixed controls.
04 — The decisionCheck the tool and the intended disclosure
Review the actual product configuration for retention, training use, access and connected services. A statement about one subscription or deployment should not be assumed to apply to another. Record the arrangement used for the workflow rather than relying on a generic claim that the provider is private.
Local execution can change where inference occurs, but it does not establish that every connected feature stays on the device. If that distinction matters, use a scoped offline network test with synthetic input. Do not test privacy by sending a real customer’s sensitive information and watching what happens.
The ICO opened a consultation on draft anonymisation, pseudonymisation and research guidance in August 2026. As of this review, it is a draft consultation, not a final rule this article can apply to your records. Check the relevant jurisdiction and current requirements for consequential decisions.
05 — ExampleReview the final article as a new disclosure
Read the output for details that came from the source and details the model invented. Both can create problems: the former may expose a person, while the latter may falsely imply a real case study. Replace unnecessary specifics and label teaching examples accurately.
A final review should also ask whether the article preserves the customer’s real information need. Excessive generalisation can produce a vague page that helps nobody. Keep concrete product facts, decision criteria and practical explanations while removing person-specific context.
For AI transformation work, assign responsibility for the brief and the final publication decision. Keep a minimal internal record of the approved topic and review, without copying the original sensitive material into every content system.
If several questions become a research report, use the survey citation checklist to describe the sample and limits without publishing identifiable responses.
As-of date. September 14, 2026. Sources reviewed for this article; the article is dated September 14, 2026.
Method. Reviewed ICO pseudonymisation guidance and the current draft consultation. Built a five-row minimisation aid using synthetic examples; no customer records were accessed or processed.
Sources. ICO pseudonymisation; ICO draft consultation.
Limits. Removing names does not establish anonymity or lawful reuse. Jurisdiction, context, recipient access and current guidance require case-specific assessment.
06 — The failuresFour briefs that carried the customer with them
The workflow separates the information need from the record because the record travels unless something stops it. The illustrative briefs below each let it through. They use the same invented delivery-window example as the rest of the guide and describe no real customer.
Names removed, story kept
The brief deletes the name and keeps the job title, the small town, the unusual incident and the exact date. The ICO’s guidance is that replacing identifiers does not necessarily change personal-data status, and the combination can identify the person to anyone who knows them.
The pasted enquiry
The full enquiry is pasted into the prompt so the writer has context. The information need was one sentence; the address, the travel date and the reason for moving added nothing to the article and are now in a tool whose arrangement nobody checked.
The borrowed privacy claim
A colleague’s subscription has a retention setting the team relies on. The tool used for this brief is a different deployment with different settings, and the generic claim that the provider is private was taken for the configuration in force.
The invented case study
The model fills sparse details with a plausible household and the article reads as a real customer’s story. No person is exposed, and a reader is told something that never happened, which the review for sourced versus invented detail is meant to catch.
Each brief kept something the article did not need or claimed something the workflow had not checked. The record in the next section is the place where both are written down before the tool is opened.
07 — The recordA brief record for a customer-sourced article
The guide’s five sections reduce to a record kept with each brief. The information need, written in general terms as the first section asks, with the audience and the question. The access and purpose: who prepared the brief, their authorised reason to read the source, and whether that reason covers reuse in an external content tool, which customer-service access does not settle on its own. The minimisation: each source detail that was removed or substituted, checked as a combination rather than row by row. The tool arrangement actually used: the product, deployment, retention, training-use and access settings, and the connected sources permitted for retrieval. The output review: which specifics came from the source, which the model invented, and what was replaced or labelled. And the publication decision, with its owner, and the minimal internal note of the approved topic without the original sensitive material.
An illustrative record for the delivery-window article reads: need, what a buyer should check before choosing a delivery window, for first-time buyers; access, prepared by a content lead with an authorised purpose confirmed for reuse of the general question only; minimisation, name, address, travel date and reason for moving omitted, with a general household scenario substituted; tool, the team’s named deployment with its retention and training settings recorded, retrieval limited to the product documentation; review, two invented specifics labelled as examples, no source detail present; decision, approved by the named owner, with the topic logged and the enquiry not copied anywhere.
The record is what the final-review section means by treating the article as a new disclosure. It shows what was disclosed to the tool and what is about to be disclosed to readers, and it keeps the two lists short.
The brief is reviewed before the tool sees it, for what the article needs. The output is reviewed before readers see it, for what the model kept and what it invented. A careful first review does not remove the need for the second, and the record holds both.
08 — Next stepThe information need is reusable; the customer is not
Fill in the record for the next article that starts from an enquiry, beginning with the information need in one general sentence. If the sentence answers the reader’s question, nothing else from the enquiry belongs in the brief.
Keep the question and minimise the record
Create the article brief from the information need, use only necessary approved facts and review the output before publication. The result should help the next reader without making the previous customer part of the story.