Define the row structure
Use one row per supported target and action, with the client reference, message URL, service ID and quantity. If a package covers several messages, record its explicit selection rule and attach the message list. Do not hide the targets behind a campaign nickname.
Attach financial and status data
After submission, add the actual order reference, charge and current state. Keep estimated quotes separate from final debits. A shared account balance is useful for funding but does not replace the transaction record needed to explain an individual client's spend.
Close cases individually
Log any adjustment, support outcome or remaining issue against the relevant row. Marking a whole channel complete can conceal one unfinished message. Preserve enough detail for another authorized team member to continue the work without recreating the purchase from screenshots or memory.
Decision checklist
| Decision | What to check |
|---|---|
| Target | Message plus action |
| Transaction | Order ID and charge |
| Closure | Final state or open issue |
Worked example
Imagine an agency handles ten messages across three channels. Two messages remain under review while the others finish. A row-level ledger makes that distinction visible; a single completed-channel checkbox would not explain which purchases still need attention or financial reconciliation.
Example figures explain the decision; they are not current prices or promised results.