After a service guidance conversation about a service problem, the reader should record the key dates and any action already taken to resolve the issue. If the matter is being raised as a complaint, putting it in writing can give the business a clear account and preserve a record.
What to record
| Record | Details to include |
|---|---|
| Key dates | When the service was bought and when the issue arose. |
| Actions already taken | What the reader has already done to try to fix the problem. |
The written account should distinguish the original problem from the steps taken to address it. This makes the sequence easier to follow without adding assumptions or unverified claims.
How to check the record
Before sending a written complaint, the reader should check that:
- The date the service was bought is included.
- The date the issue arose is included.
- The actions already taken are stated clearly.
- The account describes what happened without presenting an uncertain outcome as guaranteed.
What the reader must still confirm
The cited official guidance does not establish a complete recordkeeping template for every type of service guidance conversation. It does not specify universal additional fields, case-specific deadlines, or retention periods.
The reader should therefore confirm any further requirements with the relevant business or support channel rather than assume that the three items above are the only records that may be needed.