The unit is a story with a record
A testimonial workflow is not merely a form or a wall of quotations. It includes the request, the response, the source context, the permission decision, the approved version and the places where that version appears. A spreadsheet and a folder can support a small workflow; dedicated software can organize repeated work. Neither removes the responsibility to understand what is being published.
Move through distinct decisions
Collection answers whether something arrived. Review asks whether it is understandable and faithful to the experience. Permission concerns the intended use. Publication makes a chosen version available on a defined surface. Maintenance handles changes afterward. These stages can happen quickly for a simple quotation, but collapsing them into one submitted status makes errors harder to identify.
Give the handoff an owner
A fictional service team might have an account manager request a story, an editor review it and a website owner publish it. One person may do all three jobs, provided the decisions remain clear. Record the item identifier and next action rather than relying on a message thread whose participants may change. Keep private contact details out of public presentation.
Measure the task honestly
Sent invitations, received responses and published stories are different outcomes. None alone proves increased sales. Start with a process your team can explain and maintain, then inspect the actual bottleneck before adding automation. Our guides and tools help organize those decisions; they are not legal-compliance certification, a merchant trial or a forecast of customer behavior.
An original decision example
Illustrative lifecycle: a response arrives Monday, its public wording is checked Tuesday, and the approved excerpt appears Thursday. The customer asks for an attribution correction a month later. A complete workflow can locate that version and its destinations; a collection-only process may merely know that a submission once occurred.
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 documented setup workflow — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast consent states and agreed terms — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast response visibility states — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24