Laravel Product Feedback Form for Filament | FilaForms [ ![Filaforms Logo](https://filaforms.app/logo.svg)FilaForms ](https://filaforms.app) [ Features ](https://filaforms.app#features) [ Pricing ](https://filaforms.app/pricing) [ Blog ](https://filaforms.app/blog) [ Documentation ](https://docs.filaforms.app) [ Try Demo ](https://filaforms.app/login) [ Buy a license ](https://filaforms.app/pricing#plans) [ Features ](https://filaforms.app#features) [ Pricing ](https://filaforms.app/pricing) [ Blog ](https://filaforms.app/blog) [ Documentation ](https://docs.filaforms.app) [ Try Demo ](https://filaforms.app/login) [ Buy a license ](https://filaforms.app/pricing#plans) 1. [Home](https://filaforms.app) 2. / 3. [Form Templates](https://filaforms.app/templates) 4. / 5. Let users tell you which product features to fix next Feedback & Surveys template Let users tell you which product features to fix next ===================================================== Import a Laravel product feedback form for Filament, capture ratings and detailed feedback, then route each submission into your application. [ Open this template in the demo builder ](https://filaforms.app/app/templates/product-feedback) 6 fields, 2 required. Free demo account, no card. Updated September 2, 2026 This Laravel product feedback form gives users a focused place to select the product they mean, give an overall rating, and explain their experience. Import it into FilaForms when your Laravel application needs feedback that a product team can review beside the rest of its operational data. The imported form collects a product selection, an overall rating, and detailed feedback. The field table below shows the imported structure. Your team can review each submission in the panel, then decide whether it needs a reply, a support investigation, or a place in product planning. Feedback needs a clear destination before you ask for it. Decide who reviews responses, how quickly they respond, and which kinds of feedback require follow-up. That turns a form from a collection point into an input for product decisions. Qualtrics XM Institute's Consumer Experience Trends Report, 2023, found that 33% of consumers shared feedback directly with a company after a good experience, down 5.1 points since 2021. Give users a reason to share feedback, and explain what your team will do with it. Use this template when feedback should remain in your application database. [FilaForms is a Laravel form builder for Filament](/) that lets your team build forms visually in the panel. It does not require a separate hosted feedback account for the submission record. Fields in this template (6 fields, 2 required) ------------------------------------------------ Field types used: Select, Checkbox List, Textarea. Every field is editable in the builder after import. ### Product Rating Field Type Required Validation Product Used `product` Select, 5 options Yes `required` Overall Rating `overall_rating` Select, 5 options Yes `required` How long have you been using this product? `usage_duration` Select, 6 options No none ### Detailed Feedback Field Type Required Validation What features do you use most? `most_used_features` Checkbox List, 6 options No none What improvements would you like? `improvement_requests` Checkbox List, 6 options No none Detailed Feedback `detailed_feedback` Textarea No none Turn product feedback into an owned workflow -------------------------------------------- The field table below separates the subject of feedback from the judgement and the explanation. That structure helps product reviewers avoid guessing which part of the application a rating describes. It also makes a response useful when the written detail refers to a screen, workflow, or integration. Keep the product selection aligned with terms that users see in the application. A customer should not need to translate an internal product area into your team's vocabulary. Update the options when you rename or retire a product area, and keep historic submissions understandable in reporting. The overall rating gives reviewers a quick signal. The detailed feedback gives them the context needed to decide what to investigate. A low rating without context may need a reply. A high rating with a specific request can still reveal an important gap. Do not treat every request as a roadmap commitment. Group related feedback before changing priorities, and check the account context that your application already holds. An individual response can identify a problem, but it rarely establishes the size of the problem by itself. The settings block controls the imported form's behaviour in your panel. Adjust the form visually there, rather than maintaining a hand-written Filament schema. This lets the people responsible for product feedback refine wording when product terminology changes. Adapt the template for a beta program ------------------------------------- For a beta program, add a `would_recommend` radio field. It separates satisfied testers from testers who may churn. Keep that question near the overall rating because both ask for a judgement, while detailed feedback asks for the reason behind it. Review an overall rating and the recommendation answer together. A tester may be satisfied with a narrow workflow but unwilling to recommend the beta because it lacks a required capability. That difference can point to a retention risk that an average rating hides. Make the beta context explicit in your invitation. Tell testers which release, product area, or experiment they are assessing. This helps reviewers distinguish feedback about an unfinished beta from feedback about the stable application. Avoid adding every research question to the same form. A beta manager may need interviews or usage analysis for deeper questions. Keep this form short enough that testers can submit feedback while their experience remains specific. Route submissions in your Laravel application --------------------------------------------- FilaForms emits `FormSubmitted` after a user submits feedback. A Laravel listener can read `product`, `overall_rating`, and `detailed_feedback` from the submission data. It can then add the response to a review queue, notify the responsible product owner, or send it to application code. Save this listener as `app/Listeners/LogProductFeedback.php`. Laravel 12 discovers listeners in that directory automatically. ``` submission->data; $product = $data['product'] ?? null; $overallRating = $data['overall_rating'] ?? null; $detailedFeedback = $data['detailed_feedback'] ?? null; Log::info('Product feedback received', [ 'form_id' => $event->form->getKey(), 'submission_id' => $event->submission->getKey(), 'product' => $product, 'overall_rating' => $overallRating, 'detailed_feedback' => $detailedFeedback, ]); } } ``` Replace the log call with the action your application needs. A low rating can create an internal review task. A response with detailed feedback can notify a product owner. Your application decides which submissions receive an immediate response and which join a recurring review. Keep the original submission as the source record. Derived tasks or notes should retain a link to that submission when a reviewer needs the complete wording. This preserves context when feedback is reclassified or a product owner changes. Know what this template cannot measure -------------------------------------- The rating and checkbox fields describe stated sentiment, not measured usage. A five-star rating and heavy product usage are not linked by anything on this form. Join feedback with your own product analytics only when your data model and privacy approach support that connection. This form is also not a replacement for product discovery. Use it to collect direct feedback from people who choose to share it. Use interviews, support conversations, and usage research when you need to understand behaviour beyond the submitted response. Choose this template when your developers operate the application and need feedback data close to product records. Review the [FilaForms features for Laravel and Filament](/features) when you decide which follow-up workflows belong in your application. Use this template in your own application ----------------------------------------- With FilaForms installed, one call creates the form with every field, rule, and setting listed above. Then edit it in the builder. ``` use FilaForms\Core\Support\FormTemplates; $form = FormTemplates::createFormFromTemplate('product-feedback'); ``` Template schema (JSON) ``` { "name": "Product Feedback Form", "description": "Detailed product review and improvement suggestions", "icon": "heroicon-o-star", "category": "Feedback & Surveys", "popularity": "High", "sections": [ { "name": "Product Rating", "fields": [ { "label": "Product Used", "type": "select", "code": "product", "required": true, "options": [ { "value": "Web Application" }, { "value": "Mobile App" }, { "value": "API Service" }, { "value": "Hardware Product" }, { "value": "Other" } ], "width": "50" }, { "label": "Overall Rating", "type": "select", "code": "overall_rating", "required": true, "options": [ { "value": "1", "label": "1 - Poor" }, { "value": "2", "label": "2 - Fair" }, { "value": "3", "label": "3 - Good" }, { "value": "4", "label": "4 - Very Good" }, { "value": "5", "label": "5 - Excellent" } ], "width": "50" }, { "label": "How long have you been using this product?", "type": "select", "code": "usage_duration", "required": false, "options": [ { "value": "Less than a week" }, { "value": "1-4 weeks" }, { "value": "1-3 months" }, { "value": "3-6 months" }, { "value": "6-12 months" }, { "value": "Over a year" } ], "width": "100" } ] }, { "name": "Detailed Feedback", "fields": [ { "label": "What features do you use most?", "type": "checkbox-list", "code": "most_used_features", "required": false, "options": [ { "value": "Dashboard" }, { "value": "Reports" }, { "value": "Integrations" }, { "value": "Mobile Features" }, { "value": "Team Collaboration" }, { "value": "Analytics" } ], "width": "50" }, { "label": "What improvements would you like?", "type": "checkbox-list", "code": "improvement_requests", "required": false, "options": [ { "value": "Better Performance" }, { "value": "Improved UI/UX" }, { "value": "New Features" }, { "value": "Better Documentation" }, { "value": "Mobile App" }, { "value": "Better Support" } ], "width": "50" }, { "label": "Detailed Feedback", "type": "textarea", "code": "detailed_feedback", "required": false, "placeholder": "Please share your detailed thoughts and suggestions...", "width": "100" } ] } ] } ``` Frequently asked questions -------------------------- What does this Laravel product feedback form collect? It collects a product selection, an overall rating, and detailed feedback. The field table below shows the imported structure. Can I adapt this form for a beta program? Yes. Add a would\_recommend radio field to separate satisfied testers from testers who may churn. How do I route product feedback into my Laravel application? Listen for FilaForms\\\\Core\\\\Events\\\\FormSubmitted and read product, overall\_rating, and detailed\_feedback from the submission data. Does this form measure product usage? No. The rating and checkbox fields describe stated sentiment, not measured usage. A five-star rating and heavy product usage are not linked by anything on this form. Run this form inside your Laravel app. -------------------------------------- FilaForms installs as a Filament plugin. Submissions land in your own database. [ Try it in the demo ](https://filaforms.app/app/templates/product-feedback) [ See pricing ](https://filaforms.app/pricing) More templates -------------- - [ Collect customer testimonials your marketing team can actually publish Import a Laravel testimonial collection form for Filament, collect publishable customer fe... ](https://filaforms.app/templates/testimonial-collection) - [ Let visitors report broken pages with a screenshot and the page URL Import a Laravel website feedback form for Filament to capture page URLs, issue types, and... ](https://filaforms.app/templates/website-feedback) - [ Learn who buys your product and why before you build more Import a Laravel market research survey template, capture buyer context and budget signals... ](https://filaforms.app/templates/market-research-survey) - [ Ask attendees how your event went, right after it ends Import a Laravel event feedback form for Filament, collect attendee ratings, and route eac... ](https://filaforms.app/templates/event-feedback) - [ Brief a writer with everything they need before they start Import a Laravel content request form template for Filament, collect complete writer brief... ](https://filaforms.app/templates/content-request) - [ Capture honest feedback before an employee's last day Install a Laravel exit interview form for Filament, route sensitive answers carefully, and... ](https://filaforms.app/templates/exit-interview) - [ Capture scope changes and client approval before work starts Import a Laravel change request form for Filament, record scope, cost, priority, and clien... ](https://filaforms.app/templates/change-request) - [ Enroll a student with guardian and medical details in one form Import a Laravel student enrollment form for Filament, collect guardian and medical detail... ](https://filaforms.app/templates/student-enrollment) ![FilaForms Logo](/logo.svg) FilaForms Laravel form infrastructure for Filament. Stop rebuilding forms on every project. [ Buy a license ](https://filaforms.app/pricing#plans) ### Product [ Features ](https://filaforms.app#features) [ Documentation ](https://docs.filaforms.app) [ Blog ](https://filaforms.app/blog) [ Compare form builders ](https://filaforms.app/compare) [ Templates ](https://filaforms.app/templates) [ Pricing ](https://filaforms.app/pricing) [ About ](https://filaforms.app/about) [ Contact ](mailto:hello@filaforms.app) ### Legal [ Terms of Service ](https://filaforms.app/terms-of-service) [ Privacy Policy ](https://filaforms.app/privacy-policy) © 2025-2026 FilaForms. All rights reserved. [ ](mailto:hello@filaforms.app) [ ](https://x.com/MinasyanManuk)