Collecting and publishing testimonials

Availability

Testimonials is in beta. The page is visible to everyone under Audience → Testimonials, but until your organization is enabled you'll see a sample preview behind a lock overlay rather than your own data.

The idea

Your customers have almost certainly already said something nice about you — in a survey comment, in a support thread, or by voting for a feature that later shipped. Testimonials finds those moments and turns them into a wall of social proof, rather than asking you to go begging for quotes.

Where candidates come from

Click Scan for candidates and the scanner reuses signal you're already collecting across AppGram. Candidates are tagged by source:

• Survey — NPS and survey responses that came with a written comment.
• Support — support replies an AI classifies as positive.
• Shipped wish — customers who voted on a feature request that later shipped.
• Public form — testimonials submitted directly through a form.
• Manual — anything you add yourself with Add manually.

The header shows when the last scan ran. Filter the list by source to work through one type at a time.

The three tabs

• Queue — candidates waiting on your review, with a count when anything is pending.
• Wall — the testimonials you've approved. Filter by all, published, draft, or featured.
• Archive — everything that left the queue: invited, approved, rejected, or expired.

Consent

A quote is someone else's words, so nothing reaches your public wall without permission. From a candidate you can send a consent invite — a magic link emailed to the author. They approve or decline, and the testimonial draft only lands on your wall after they say yes.

A testimonial can carry one of two consent states, and the difference matters:

• Author confirmed — the author clicked through the invite and agreed. This is the strongest position and the one to aim for.
• Self-attested — you ticked I have consent when approving, but the author hasn't confirmed in AppGram. Fine when permission was given elsewhere, as long as you can actually point to it.

If an author declines, their reason is recorded on the archived candidate.

Reviewing a candidate

For each candidate you can:

• Send a consent invite — the normal path for anything you want to publish.
• Approve — you edit the quote at this point, so you can trim it without changing its meaning.
• Reject — with a reason, so the next person reviewing the archive understands the call. Something like "Generic thank-you, not specific enough to feature" is more useful than no note at all.

Adding a testimonial manually

Add manually is for quotes that came from outside AppGram — a conference conversation, an email, a post. You provide the quote plus the author's name, job title, company, email, avatar URL, and a social profile link.

Manually added quotes still need consent. Send the invite, or record that you have permission when you approve.

Publishing

Approved testimonials sit on the Wall as drafts or published entries, and any of them can be featured. Published testimonials are what appear on your public testimonials page and in the testimonials widget — including the testimonials block you can drop onto a link page.

Best practices

• Prefer specific quotes to enthusiastic ones. "Cut our onboarding from two weeks to two days" outperforms "Great product!" every time.
• Always chase author-confirmed consent for anything you'll use in marketing. Self-attested is a fallback, not a default.
• Include the author's role and company. An unattributed quote reads as invented.
• Scan periodically rather than once. New candidates appear as surveys come in and features ship.
• Trim quotes for length, never for meaning. Editing a lukewarm quote into a glowing one is the fastest way to lose a customer's trust.