Testimonial forms: the 5-7 fields, the field order, and the 4-step deployment

A working testimonial form has 5-7 fields in a specific order. The fields: full name, role and company, a star rating, the testimonial text (or video upload), and explicit permission to publish. The order: identity fields first, rating second, content third, permission last. The right form captures specific, attributed content in under 2 minutes. The wrong form produces vague, unusable testimonials that nobody publishes.

This page is the form mechanism. The how to collect testimonials page is the collection process. The how to ask for a testimonial page is the asking side. The testimonial questions page is the prompts. This page is the form itself: the fields, the order, the templates, the deployment.

The 5-7 fields the form should have

The 5 required fields, in the order they should appear: full name, role and company, star rating, the testimonial itself (text or video), and permission to publish. The 2 optional fields: a photo of the customer, and a link to the customer’s public profile (LinkedIn, Twitter, website).

Field 1 is full name. The name is the attribution. The form should require both first and last name. The “first name only” form produces testimonials that are not credible because the customer could be anyone. The full name is the smallest unit of credibility.

Field 2 is role and company. The role is the context. The form should ask for both in one field (“Role at Company” or “Title, Company”). The role+company is the second unit of credibility. The reader can verify by looking up the person on LinkedIn.

Field 3 is the star rating. The form should ask for a 1-5 star rating. The rating is the structured output that powers the Schema.org Review markup. The rating is also the trust signal that appears on the wall. The rating should be required because it is the structured data input.

Field 4 is the testimonial content. The form should offer both text and video options. The text field should accept 50-2,000 characters. The video field should accept files up to 500MB. The customer picks the format. The form should default to text and let the customer upgrade to video if they want.

Field 5 is the permission to publish. The form should ask: “I give permission to publish this testimonial on [company]’s website and social channels.” The permission is required. The permission is a checkbox, not a typed answer. The form should also have a “what to publish” option: with or without the customer’s photo, with or without the company logo.

The field order rationale

The order matters. The form that asks for the testimonial first, before the name, before the rating, produces higher drop-off because the customer feels the request is too big. The form that asks for the name first, then the role, then the rating, then the content, then the permission, produces higher completion because each field is small and concrete.

The identity fields (name, role, company) come first because they are the easiest to fill out and the least anxiety-producing. The customer types their name without thinking. The momentum carries them into the next field.

The rating comes before the testimonial text because the rating is a small, low-friction input. The customer clicks 5 stars in 2 seconds. The act of rating produces a positive emotional state. The positive state makes the testimonial text easier to write.

The testimonial text or video comes after the rating because the customer has already committed small (name, role, rating). The larger commitment (the testimonial) is the next step. The momentum carries through.

The permission comes last because the customer has already given the substantive content. The permission is the administrative wrap-up. The form is almost done. The customer clicks the box and submits.

The required vs optional policy

Required fields: name, role and company, star rating, testimonial content, permission to publish. The form cannot submit without these. The form’s value is in the structured output, and the structured output requires all five.

Optional fields: photo, public profile link. The form can submit without these. The form’s value is preserved without them. The fields are there for the customers who want to add them, not for the customers who do not.

The “all fields required” form produces lower completion. The “required = 5, optional = 2” form produces higher completion because the customer who wants to be quick can be quick, and the customer who wants to be thorough can be thorough. The flexibility is what produces the higher overall submission rate.

The 3 form templates (text-only, video, mixed)

The text-only template is the simplest. The form has the 5 required fields plus the 2 optional fields. The testimonial field is a textarea with a 50-2,000 character limit. The form is 5-7 fields. The form takes 1-2 minutes to complete. The text-only template is right for B2B SaaS where most testimonials are text.

The video template prioritizes the video upload. The form has the 5 required fields, but the testimonial field defaults to video upload, with text as a fallback. The form is 5-7 fields. The form takes 2-5 minutes to complete (including recording). The video template is right for ecommerce or product-led brands where video is the strategic format.

The mixed template offers both equally. The form has the 5 required fields, with the testimonial field showing both options: “Write your testimonial” or “Record a video.” The customer picks. The form is 5-7 fields. The form takes 1-5 minutes depending on the choice. The mixed template is right when the team is unsure which format will dominate, or when both are strategically important.

The 4-step deployment process

Step 1: Pick the template. Start with the text-only template unless the team has a specific reason to use video or mixed. The text-only template is the fastest to deploy, the highest-completion, and the easiest to A/B test against the alternatives.

Step 2: Configure the form. Add the 5 required fields, the 2 optional fields, the character limit on the testimonial, the file size limit on the video, and the permission text. Set the form to require the 5 required fields and allow the 2 optional fields to be empty.

Step 3: Test on mobile. Open the form on a phone. Fill it out. The form should take under 2 minutes on mobile. The fields should be large enough to tap. The video upload should work from the phone’s camera. The form should not require horizontal scrolling.

Step 4: Generate the shareable link. The form’s URL is what gets shared with customers. The URL should be a clean, readable link (not a 200-character query string). The URL should work on any device without login. The URL should pass the shareable-link test: if you text it to a customer, they can open it and submit a testimonial without creating an account.

The 3 most common form failure modes

The first failure mode is the too-long form. The form has 15 fields. The form takes 8 minutes to complete. The form completion rate is 5%. The fix is to cut the form to 5-7 fields. The fields the team thinks are essential (industry, company size, use case) can be set in the curation step, not in the collection step.

The second failure mode is the account-required form. The customer has to create an account before they can submit. The customer abandons. The form completion rate is near zero. The fix is to remove the account requirement. The customer should be able to submit a testimonial without signing up for anything.

The third failure mode is the wrong-permission form. The form asks for permission but does not specify what the permission covers. The customer is uncertain. The customer does not submit. The fix is to make the permission specific: “I give permission to publish on your website and LinkedIn” with a checkbox, not a typed “I agree” with no context.

The mobile optimization checklist

First: the form should be one column on mobile. Two-column layouts do not work on a phone screen. The customer should not have to scroll horizontally.

Second: the input fields should be large enough to tap. The recommended tap target is 44×44 pixels. The form should not have small inputs that require precise tapping.

Third: the video upload should work from the phone’s camera. The customer should be able to record a video in the form, not download the form to a desktop to record.

Fourth: the submit button should be visible without scrolling. The customer should be able to see and tap the submit button at all times. A submit button that requires scrolling to find is a conversion killer.

Fifth: the form should save partial progress. If the customer closes the form and comes back, the form should remember what they typed. The customer should not have to start over.

The journey after this page

If you have the form and want the collection process, the how to collect testimonials page is the parent reference.

For the asking side (the outreach that gets customers to the form), the how to ask for a testimonial page is the lifecycle reference. For the questions to put in the testimonial field, the testimonial questions page is the prompts reference. For the WordPress-specific deployment of the form, the testimonials on WordPress page is the platform reference.

For the format the customer submits in the form, the testimonial examples page is the gallery of good testimonials that the form should produce. For the asking templates that link to the form, the testimonial request templates page is the email and message templates that include the form link.

For teams that want the form wired up to a shareable collection link with no account requirement and mobile-first design, Testivo is one tool that supports the 5-7 field structure with text and video options. The form is the capture touchpoint. The wall is the display surface that follows.