Identify required inputs
Use the selected service's documented fields to determine what the order needs. Public content identifiers and campaign references often serve different purposes from account access credentials. Do not collect extra information just because an intake form has room for it.
Separate access from reporting
If another authorized task requires sensitive access, keep that process separate from ordinary purchase reporting. Avoid placing passwords, API keys, or private messages in shared order exports. A support request should contain relevant evidence without exposing unrelated account data.
Review retained records
Keep the information needed for reconciliation and unresolved order questions under your own retention process. Limit shared reports to the intended audience. When staff hand off a campaign, transfer the required references rather than an unrestricted copy of every client file.
Decision checklist
| Decision | What to check |
|---|---|
| Input | Documented service requirement |
| Access | Separate sensitive credentials |
| Report | Relevant purchase references |
Worked example
A hypothetical client sends a password alongside a public post link for a post-level service. The operator should use the required link and avoid copying the password into the campaign sheet or support ticket; the extra credential does not improve the order specification.
Example figures explain the decision; they are not current prices or promised results.