The situation
So far Sophie only heard back when something went wrong, as an email to customer service. Whether the packaging arrives well, whether shipping is fast enough and where new customers come from, she did not know.
Sophie sells loose tea. Three days after delivery she asks how it went: with a scale, two choice questions and a text field that only appears when something was not right.
So far Sophie only heard back when something went wrong, as an email to customer service. Whether the packaging arrives well, whether shipping is fast enough and where new customers come from, she did not know.
Shopware's product reviews belong to one product and sit on its page. A question about the delivery or the shop as a whole has no place there, and the contact form knows neither a scale nor a choice.
The follow-up "What bothered you?" appears below 7, the thank-you above 8; in between it stays with the choice questions.
Create top-level element
The slider has minimum 0, maximum 10 and a step of 1, prefilled with the default value 5. The value arrives as a number, so the column in the export can be sorted and calculated with.
Conditions on a slider compare numbers. "What bothered you?" has the rule "is less than 7", the green success message with the thank-you "is greater than 8". Whoever is happy is not held up with questions.
For "What did you like?", "Max. selections" is set to 3. Whoever ticks everything says nothing; with three ticks it becomes a choice. The form does not accept more.
As a block on the "Your opinion" shopping experience page. Sophie put the link to it into the shipping confirmation email, under Shopware's email templates; no assignment is needed.
Without a context, one row per answer: the score as a number, punctuality, likes, source and, where present, the complaint and the order number. If the customer is signed in, they appear in the fixed columns.
In the "Form" tab a thank-you is enough as the confirmation. A recipient address is there, but the email stays off.
Feedback needs no email per answer. "Active" under "Email notification" stays off; Sophie reads the answers once a week in the history.
For the success message with the thank-you, Sophie picks the satisfaction field under "Conditions", "is greater than" and the value 8. The field accepts both comma and point.
In the "Your opinion" shopping experience Sophie drags the "Form Manager" block from the "Form" block category into a section and picks the "Customer feedback" form there.
0 to 10 in steps of 1: eleven levels. In October 120 answers, so 120 rows; columns: 14 fixed and 6 for the fields, 20 in all. The score sits as a number in a column of its own, the ticks for "What did you like?" comma-separated in one.
For a scale and choice questions, yes. Shopware's reviews belong to individual products, and the contact form has fixed fields. With the plugin you build the questionnaire in the administration, without a template.
It collects them: in the history with filters and as a CSV with one column per question. Averages and charts are done in the spreadsheet.
Only without signing in. If the customer is signed in, their account is attached to the submission, and name, customer number and email appear in the export. The "Customer type" filter separates "With customer account" and "Guest".
Yes, every submit becomes a submission of its own with its time. Duplicate answers show up in the export by the order number or the customer.
A form is one page. Longer questionnaires are divided with groups into sections with their own heading, and parts are revealed through conditions.
In the history, set the "Form" filter to "Customer feedback" and "Date" to the month, then "Export CSV". All matching entries are exported, not just the visible page.