As a practical drafting approach, a request should be split before it is sent for support when one message bundles separate problems, or when its desired outcome, supporting documents, or prior actions apply to different parts of the issue. Each resulting request should make the problem, outcome sought, relevant evidence, and action already taken clear for that part. This is an organising approach, not a mandatory rule established by the cited guidance.
What signals that a request should be split?
Guidance for written service complaints says that the complaint should explain the problem and desired outcome, identify any action already taken, and can include relevant supporting documents. Those elements provide a practical way to identify requests that should be separated.
| Element to check | Reason to split | How to organise it |
|---|---|---|
| Problem | Separate issues are bundled together | Give each request a specific problem |
| Desired outcome | The result sought differs between parts | State the relevant outcome with its issue |
| Supporting documents | A document supports only one part | Place it with the relevant request |
| Action already taken | Different steps have been tried for different issues | Record those steps under the corresponding issue |
Shortening a message is not, by itself, a sufficient reason to split it. Separation is most useful when the problem, desired result, evidence, or prior-action history would otherwise become unclear.
What should each split request contain?
Each request should follow the same basic structure:
- Explain the specific problem.
- State the outcome sought.
- Identify what has already been done to address the problem.
- Attach relevant supporting documentation.
Documents that relate to separate issues should accompany the request they support. This keeps the material connected to the problem and intended outcome without claiming that splitting guarantees separate handling.
What still needs confirmation?
The cited guidance does not establish a required split threshold, a particular support channel, or a guaranteed response or outcome. Before sending, the requester should check current official support instructions and any applicable contract or policy for:
- The correct support channel and required format.
- Any mandatory rules for separating issues.
- Which supporting documents are required or accepted.
- Any applicable fees, deadlines, refund rights, or other terms.
- Whether related requests will be linked or handled independently.
No particular result should be assumed merely because a request has been split or supporting documents have been attached.