Distinguish the objects
A comment on the main post and a reply to another comment are different placements. If the brief requires a reply, confirm that the service explicitly supports that structure. A general comments listing should not be assumed to offer arbitrary placement within a discussion.
Prepare usable identifiers
Follow the listing's target format and include only the identifiers it requests. In a support brief, identify the parent post and intended conversation item clearly. Do not provide account credentials or private access information as a substitute for a compatible public target.
Keep content truthful
Any supplied text should be authorized, relevant and free from invented personal experiences or endorsements. Check whether the requested wording fits the actual discussion. A placement specification cannot justify misrepresenting a customer relationship or impersonating someone who participated in the conversation.
Decision checklist
| Decision | What to check |
|---|---|
| Level | Post comment or nested reply |
| Identifier | Supported target format |
| Text | Authorized and relevant wording |
Worked example
For a hypothetical product announcement, a company may want an explanatory response under its own clarification. If the offer supports only top-level comments, that is a scope mismatch. The buyer should change the brief or select an explicitly compatible service.
Example figures explain the decision; they are not current prices or promised results.