Record context at collection
A customer may describe one team, location, service or period. Decide which details matter to a future reader and which should remain private. A broad business name alone may be insufficient when locations operate differently. Avoid collecting precise personal or visit details that are unnecessary for the publishing task. The objective is relevant context, not an exhaustive customer dossier.
Separate routing from endorsement
Boast documents location and staff fields and widget filters. Those are organizational mechanisms, not proof that an individual agreed to every possible use. A story collected for one service should not automatically populate an unrelated sales page. Have the reviewer confirm the relationship between the response, its approved use and each proposed destination.
Plan for organizational changes
Staff move, services change and branches close. A testimonial can remain a truthful historical account while becoming a poor description of the current offering. Retain a date and enough internal context to review it later. Do not silently rewrite the customer’s attribution to imply they used a different location or were served by a current team.
Check a mixed fictional set
Create a paper acceptance case with two locations and an item with no location assigned. Decide where each should appear and what should happen to the unknown item. Then inspect the actual filter behavior before publishing real content. This is our proposed test method, not a merchant test result. Keep a manual review path for exceptions instead of assuming every imported record is correctly classified.
An original decision example
Illustrative filter case: a story about the north branch should not automatically appear under a promise about the south branch’s team. Keep a record with unknown location out of a location-specific collection until clarified. A company-wide destination may be appropriate only when the context and permission support that broader presentation.
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 form-field descriptions — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast widget fields and filters — Merchant documentation · support.boast.io · Merchant-controlled · checked 2026-09-24