Follow one person through the process
A fictional customer might enter one request sequence, receive several messages, submit one video and have no public story yet because review is pending. That is not four testimonials or several new customers. Label each count according to the event it actually represents. A useful report should reveal the stage of work rather than turn all activity into a success metric.
Read the product’s counting unit
Boast defines enrollment as adding someone to a sequence; multiple messages within that sequence are not separate enrollments. Its plans have distinct enrollment allowances. Response allowances are a different constraint. Confirm current limits and the treatment of repeated enrollment before importing a large contact list. Do not infer that a generous email allowance means unlimited new video submissions.
Keep assumptions out of the result
If you enter expected invitations and an assumed response percentage in your own plan, label the result as a scenario—not observed demand. Our worksheet avoids supplying a default conversion rate for that reason. Use actual submissions where available, and keep tests or duplicate records separate so they do not make a small program appear more successful than it is.
Choose the next action from the stage
Many invitations but no replies could reflect timing, relevance, delivery or collection friction; it does not immediately prove a tool is bad. Many submissions but few published items may indicate review capacity or permission gaps. Inspect the actual bottleneck before buying more allowance. A subscription upgrade cannot by itself resolve an unclear request or an unowned review queue.
An original decision example
Illustrative count: twelve people are enrolled in a three-message sequence, four submit responses and two stories are published after review. Report twelve enrollments, the actual messages sent, four submissions and two publications separately. Do not report thirty-six testimonials or assume the remaining two submissions were unsuitable without checking their status.
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 sequence enrollment definition and limits — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast request sequences — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast plans, billing and response allowances — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24