Asking every customer on the same calendar day.
Trigger the request from the milestone, not the month. The same question lands very differently a week after a win than it does ninety days later.
SaaS
SaaS buyers discount vague praise. The useful testimonial names the job the customer was doing, the thing that used to be painful, and what changed. That level of detail decays fast, which is why the request belongs next to the milestone rather than in a quarterly push.
Share a campaign after onboarding, an implementation milestone, or a support win. Give the customer a clear path to a written story, video, or public review destination.
Best request moment
After a meaningful product milestone
Sample setup
Illustrative, not a customer account
Growth adds webhook, Slack, and Teams connections when the handoff needs more automation.
Broad questions get broad answers. These are written to surface a specific before and after.
Trigger the request from the milestone, not the month. The same question lands very differently a week after a win than it does ninety days later.
A job title and company size tell the next buyer whether the story is about them. Keep the attribution the advocate agreed to and no more.
Approved items belong on the pages where buyers hesitate, which for most SaaS teams is pricing and the comparison page.
Right after a visible win: onboarding completed, an integration going live, a support case resolved well, or a renewal. The request works because the customer has a specific event in mind, not because the calendar says it is time.
Yes. A campaign can point to a public review destination you configure instead of collecting the response inside Amplaud. Free covers 1 review source; paid plans raise that limit.
The 14-day trial covers the full workflow. The free plan runs 1 workspace, 1 campaign, 1 review source, and 1 seat, which is enough to collect and publish your first stories.
Give them the mic. Launch your first campaign free and watch quiet goodwill turn into public proof.