Practical guide: Support reply
From source to a checked result: Support reply. A useful result starts with a clearly defined task. This worked example separates the source material, the proposed output and the checks needed before publication.
A useful result starts with a clearly defined task. This worked example separates the source material, the proposed output and the checks needed before publication.
Source material
Hello, I ordered a table lamp ten days ago (order 4711) and it still has not arrived. Can you tell me where it is? I need it by Friday.Example result
Reply: Hello, thank you for your message and sorry for the wait. We are checking order 4711 with the carrier right now and will send you the tracking status today …
Concerns: delivery is late; needed by Friday
Questions: Should we send a replacement if the parcel is lost?What matters in this example
A reply draft should separate the customer's concern from confirmed operational information. An order number and a requested deadline identify the case, but they do not prove where a parcel is. A useful draft acknowledges the issue, identifies missing information and avoids promising a replacement, refund or delivery date without a verified source.
A repeatable workflow
- 1Define the purpose and collect the relevant source material.
- 2Compare the result with the source; check names, numbers, dates and meaning.
- 3Resolve uncertain details, then copy or export the approved version.
Before publication
A fluent result is not evidence of accuracy. Missing facts should remain open rather than being filled with assumptions. A final review in the actual page or document checks context and presentation.