Important limitations

When a standard testimonial consent field is not enough

Last materially reviewed 2026-09-24

Quick answerTreat custom permission requirements as an early product-selection constraint, not a detail to discover after migration.
Likely to work well when

✓ Small teams with repeated customer-story requests

✓ Readers comparing concrete collection and review requirements

✓ Businesses needing an understandable publication inventory

Important limitations

— Fake reviews or manufactured endorsements

— Regulated advice or legal-compliance certification

— Generic CRM, course delivery or agency project management

What to know

Define the use before the wording

Specify what you intend to publish, where it may appear and whether edits or future reuse are expected. Do not begin by copying a legal-sounding paragraph from another business. Different circumstances can require different permissions. We do not provide a universal release form or certify that a checkbox satisfies the rules applying to your customers.

What to know

Distinguish editable text from the linked agreement

Boast’s documentation distinguishes editing consent-field text from linking a custom agreement, with the latter described for Premium. That matters when a business needs its own approved terms. Confirm the exact current entitlement and behavior before selecting a plan. A text-editing control should not be assumed to replace the agreement a contributor actually sees and accepts.

What to know

Preserve the version that applied

A link to today’s terms may not explain what someone agreed to months earlier. Keep a defensible record of the version and context associated with each response, using the product’s supported records and your own appropriate retention process. Avoid changing historical evidence merely to make old submissions look consistent with a new campaign.

What to know

Escalate substance, not routine formatting

If the unresolved question concerns minors, regulated claims, sensitive information or a disputed permission, involve a qualified adviser or responsible business owner. The tool can help collect and organize a decision but cannot make it valid by itself. For ordinary operational changes, keep the process simple: review the proposed use, verify the supported configuration and test the visible explanation before sending real invitations.

What to know

An original decision example

Illustrative buying constraint: a business has adviser-approved terms that must be shown at collection. Ask whether the exact agreement can be linked on the chosen plan and whether the accepted version remains identifiable afterward. A field that merely changes the checkbox label is not evidence that both requirements are met.

Source boundary

Where the safety evidence stops

This guide draws on Boast consent states and agreed terms, Boast plans, billing and response allowances. Merchant-controlled records describe the provider’s own capabilities, terms or standards; they do not independently validate those claims. These records do not establish independent confirmation of the product claims.

Verify any current price, plan limit, label direction, compatibility rule, or commercial term that would materially change the decision. The dated source ledger shows the underlying records so this conclusion can be checked and updated.

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.

  1. Boast consent states and agreed terms — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
  2. Boast plans, billing and response allowances — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24