Collecting honest reviews: a practical guide for SaaS teams

B2B buyers read reviews long before they talk to sales. Five glowing, vague reviews convince nobody. What convinces them is a steady flow of specific reviews from people who clearly use the product, including critical ones, and a team that answers in public.

This guide shows how to build that on SaaS.Vote, step by step. It also lists what your team cannot do, because those limits are exactly why buyers trust the result.

Step 1: Claim your profile and prove you control the domain

If your product is not on SaaS.Vote yet, add it. If it is already listed (reviewers can add products too), open its page and claim it. When the email of your LinkedIn account is on the product’s domain, the claim is approved automatically; otherwise SaaS.Vote reviews it.

Next, prove that you control the product’s domain. Several tools depend on it: customer list uploads, email invitations and API verification. You can do it in one of these ways:

  • verify an admin email address on your website’s domain in the product settings;
  • own the profile with a SaaS.Vote account whose email is on that domain;
  • place the SaaS.Vote widget, or a link to your SaaS.Vote profile, on a page of your website. A background check confirms it and keeps re-checking. The profile then shows “SaaS.Vote badge verified”.

Then add colleagues from the team tab as managers or moderators (they need a SaaS.Vote account). Managers can also handle the customer list and invitations; moderators can reply, confirm customers, report reviews and run the feedback board.

Step 2: Connect customer verification

The Verified customer label separates your real customers from everyone else. It matters most on a bad day: during a review campaign against you, outsiders show up as unconfirmed. There are three ways to provide that proof.

Upload a customer list

In the “Customers & invites” tab, upload a CSV file or paste addresses, one per line or separated by commas or semicolons. SaaS.Vote finds the email column on its own, with or without a header row.

  • Up to 5 MB per file, 10,000 addresses per upload and 50,000 per product.
  • You can add to the current list or replace it.
  • Addresses are trimmed and lowercased, and only their SHA-256 hashes are stored. If you prefer, upload such hashes instead of addresses.
  • After an upload, reviews still waiting for verification are checked against the new list within a few minutes.
  • Clearing the list does not remove labels from reviews that were already verified.

A review is matched by the reviewer’s account email or by an email they confirmed with a one-time code on your review form. An address someone simply typed into the form is never checked.

Or connect your own API

If your user base changes daily, connect a verification endpoint instead. SaaS.Vote sends an HTTPS POST request with one email address and your shared key in the X-Saas-Vote-Key header. Your endpoint answers { "verified": true } or { "verified": false }. Your customer list never leaves your servers. The integration tab has a test tool and request examples.

Or confirm customers by hand

For a reviewer you can identify yourself, use “Confirm customer” in the reviews tab. It is irreversible and it appears in the public moderation log, so only use it when you are sure.

Step 3: Invite customers

Waiting for reviews to arrive on their own rarely works. There are two ways to ask.

Every product gets an invite link that opens its review form, in English or Russian, and a QR code you can download as an SVG. Use them wherever customers already meet you: in the product after a milestone, in onboarding emails, on invoices, in support signatures, at events.

Email invitations

You can also let SaaS.Vote email your customers. The email comes as “your product via SaaS.Vote” in English or Russian, with your logo and colour, five stars that open the review form, a short paragraph from you and an unsubscribe link. Your paragraph is plain text without links, and the rest of the email is fixed, which keeps the channel from being used for anything but an honest request. One reminder can follow if the customer has not reviewed. The rules:

  • up to 50 addresses per batch and 200 per product in any 24 hours;
  • the same address gets an invitation to your product at most once every 30 days;
  • people who unsubscribe never get review invitations from SaaS.Vote again, from any product;
  • you confirm that you have the right to contact each person, for example customers who agreed to receive email from you;
  • your product page must be published, and you must have proven domain control.

Addresses and link tokens are stored as hashes. The tab shows how many invitations were sent, how many were not delivered and how many led to a review.

The “Invited” label

Reviews that come through your link or an email invitation are publicly marked Invited. You cannot choose which reviews get it, and they publish immediately under the same rules as other reviews. Buyers expect vendors to invite customers, so the label does not hurt you. Inviting only your biggest fans does: it shows up as a wall of identical praise.

A few habits that keep invitations honest:

  • Invite a whole segment, such as every account that finished onboarding last month, instead of hand-picking.
  • Ask at a natural moment, after a real result rather than on day one.
  • Never offer a reward. Paying for reviews or offering incentives breaks the SaaS.Vote terms.
  • Don’t suggest what to write. Ask for specifics instead. The review form has optional fields for pros and cons, aspect ratings, usage time, company size and role, and buyers use them to find reviewers like themselves.

Step 4: Reply to reviews

Your team gets an email when a new review arrives (each person can switch notifications off), and the reviews tab shows which ones still need a reply. Owners, managers and moderators can post one public reply per review and update it later. The author gets an email when the first reply appears.

Replies are read by future buyers more than by the reviewer. What tends to work:

  • Answer critical reviews first. A calm, specific reply to a two-star review builds more trust than thanks under a five-star one.
  • Be concrete. Say what you changed or plan to change, and roughly when.
  • Don’t argue about the reviewer’s experience, and never reveal details about their account in public.
  • Follow up when you ship the fix. The author may update the review, and the edit history shows the improvement to everyone.

Reviews and author edits publish immediately. Your team cannot choose when a review appears.

What your team cannot do

These limits apply to every product, including yours:

  • Edit, hide or delete reviews, or change a rating.
  • Choose labels. “Invited” is set by the link the reviewer followed. “Verified customer” comes from your list, your API or your manual confirmation, which is public. No label can be removed by the team.
  • Review your own product. Owners, team members and people whose LinkedIn workplace is your company cannot submit a review of it.
  • Hold back a review. Reviews publish immediately. Only moderators can remove a review after considering a report.
  • Pay to change your rating. A Featured spot on the home page is a labeled placement and does not change reviews or ratings.

If a review breaks the rules (a competitor posing as a customer, personal data, spam), report it from the reviews tab with a reason. SaaS.Vote moderators decide, and the outcome appears in the public moderation log. Read more in Transparent moderation: what the public log shows.

Step 5: Show your rating on your site

The widget tab builds an embeddable rating widget. Choose a variant (badge, card or minimal), a light, dark or automatic theme, an accent color, border, width, language and label, and whether to show the rating and the review count. Then paste one script tag and one HTML snippet into your site.

The widget links to your full profile, critical reviews included. That is the point: buyers trust a badge that leads somewhere they can check. Placing it on a page of your website also lets SaaS.Vote verify your domain and gives your profile the “SaaS.Vote badge verified” label. Product pages with reviews also carry structured data that search engines can use to show your rating.

Every claimed product also gets a public feedback board where customers suggest and vote for ideas. It does not affect your rating, but it shows buyers that you listen.

Checklist

  1. Claim your profile and prove domain control.
  2. Upload a customer list or connect your API.
  3. Share the invite link and QR code; send email invitations to whole segments.
  4. Reply to every critical review with specifics.
  5. Add the widget to your site.

For an overview of everything available to SaaS teams, see SaaS.Vote for business. To understand how buyers will read your labels, see How SaaS.Vote verifies B2B software reviews and How it works.