Choose an observable moment
Delivery, a completed milestone or a customer voluntarily describing a useful result can each be a reasonable starting point. None guarantees that the person wants to endorse the business. Decide what experience the request concerns and why the customer can speak about it. A newly signed contract may provide too little substance for a meaningful account of results.
Separate service recovery from promotion
If a customer is waiting for a problem to be resolved, first address the service issue. Do not turn support into pressure to provide a positive statement. An invitation should allow an honest response or a decline. The testimonial process must not become a condition of receiving the service, a refund or ordinary support.
Define a trigger without assuming it is reliable
Boast documents automated sequences and enrollment. Before connecting any trigger, write down the exact event it represents and cases where it should not send a request. An imported customer, canceled job or duplicate record can look like a new opportunity to a simple automation. These are proposed operational checks, not claims about an observed Boast integration failure.
Prefer a small, explainable rule
A workable first rule might be a human-reviewed list of completed projects with no unresolved service issue. The example is illustrative, not a universal timing recommendation. Record who decides that a request is appropriate and how a refusal is respected. Expand automation only when you can explain why each person received a message and stop inappropriate follow-up promptly.
An original decision example
Illustrative trigger: completion of an agreed project milestone creates a reviewable candidate for outreach, not an automatic endorsement request. The account owner checks whether the customer has experienced the result and whether a service issue remains open. Only then does the team decide whether an invitation is appropriate.
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 request sequences — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast submission instructions guidance — Merchant documentation · support.boast.io · Merchant-controlled · checked 2026-09-24