Make the queue answer a question
The purpose of a review queue is to identify the next decision, not to accumulate favorable material. A reviewer should be able to see what is missing: context, attribution, permission, a factual clarification or a suitable destination. Assign a responsible person and a next action. An item can remain unpublished without being deleted or treated as a failed customer interaction.
Use states consistently
Boast documents Needs Review, Private, Unlisted and Published states. Map your own responsibilities to the actual behavior of those states before relying on them. A state that permits a direct link is different from one intended to remain inside the account. A reviewer should understand that difference even when the item is absent from the main website widget.
Review claims, not sentiment alone
Check whether the proposed excerpt preserves the customer’s meaning, whether a named person or company is correctly attributed and whether time-sensitive statements still apply. Do not equate a positive tone with accuracy. Mixed or critical feedback may be useful operationally without becoming a promotional quote; handle it honestly rather than rewriting it into praise.
Close the decision loop
For an approved item, record where it will appear and which version is allowed. For a hold, state the unresolved question. For a rejection, preserve the reason under your appropriate retention policy. These records help another team member understand the decision later. Do not use an automated approval rule until you have identified the cases that require human judgment and a supported way to stop publication.
An original decision example
Illustrative queue entry: item17 awaits confirmation of a named result; its owner is the account manager and its next action is a clarification, not publication. Item18 has no unresolved question and a specified destination. Keeping these decisions separate lets useful work continue without treating every hold as a failed collection campaign.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Boast response visibility states — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast documented setup workflow — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24