In this guide
Write the preference as an actionDistinguish current-case and ongoing useUse the note in the responseKeep sensitive history out of routine notesUpdate when the customer steersA note saying “prefers text steps” can improve the next response. A note turning that preference into a judgment about capability can mislead the next agent and collect more personal information than the task needs. Record what helps the interaction and let it change when the customer’s instruction changes.
This article concerns practical support records, not a claim that a particular service offers every communication format.
Write the preference as an action
“Send ordered text instructions” tells an agent what to do. “Customer cannot cope” does not identify the barrier or a useful response. Keep the wording neutral and tied to the task. If the customer wants a written summary after a call, record that specific request rather than infer a broader personal profile.
Distinguish current-case and ongoing use
A person may prefer text because they are in a noisy place today, or because text works best for their assistive technology. Ask only what is necessary to use the preference appropriately. The organisation’s actual process determines whether it can retain a future preference. Do not promise account-wide storage if the team only has a current ticket note.
Use the note in the response
Clear headings, one action per step and a concise result summary can support the stated preference. Keep necessary field labels and avoid image-only directions when text was requested. W3C’s instruction guidance offers a reference for this writing. The quality of the response matters more than the existence of a preference field that nobody reads.
Keep sensitive history out of routine notes
A practical format request rarely needs a diagnosis, family history or an agent’s speculation. ICO’s minimum-data principle can help frame purposeful collection, without establishing compliance for a particular organisation. Access should follow the support task. A broad export of preference notes should not become an unnecessary personal dossier.
Update when the customer steers
If the customer now asks for a concise explanation or another supported format, revise the current note. Do not force an old preference onto a new situation. A useful record supports the person’s present interaction and preserves the actual account question. It should make the next step easier, not become a label that follows the customer after its original context has gone.
A preference note can include an example of the useful format, such as a short written result followed by the next step. That is more actionable than a vague label. Review whether the note still fits when the task changes. A customer may want detailed setup help in one case and a concise payment confirmation in another.
Questions about this guide
Can a preference note replace asking whether the explanation helped?
No. A format can be followed and still leave the task unclear. Check the relevant understanding or result, then adjust the explanation if needed. The preference is useful context, not proof that every future response will be accessible or complete.