How it works
The customer taps a rating where the visit ends and either writes to you or opens the public listing. You receive it by email with the location and the workstation attached, usually within seconds.
There is no terminal version and no bot version of the product: every channel opens the same 7Feedback page with the same options.
Updated
Either the channel asks by itself at the end of an operation, or a permanent QR sits where the experience happens. Both routes exist everywhere.
Stars, Faces or Numbers — whichever the business picked. The rating alone is a complete submission, and text, photo or video is offered but never demanded.
Write to the business, or open the public listing of this location. Both, in that order, for every rating. Nothing branches on what was tapped.
An email per submission, carrying the rating, the comment, any media, the location and the staff login it came through — so it is clear which counter and which shift it belongs to.
Almost every "it is not working" turns out to be the second one. The order matters more than anything else in setup.
7Feedback as a paid product, or Customer Feedback as an add-on inside an existing 7Stamp account. Nothing below can be switched on until this one is.
If it is offNothing else is even visible.
The master switch on the business profile. Terminals, the web card and the bot ask for a rating only while it is on, and it is off by default.
If it is offChannels stay silent, and nothing looks broken.
Inside the chat-bot channel: an automatic request after an operation, and a permanent menu button. Either, both, or neither.
If it is offThe bot simply never asks.
Sorted from what you can do this afternoon to what needs a developer on your side.
Attribution
The location is taken from the staff login the submission came through, and a staff login is a workstation: a till, a terminal, an API integration, a badge QR. There is no such thing as an unattributed submission.
In a chat-bot there is no staff login, so the customer selects the location before sending, and the selection is mandatory. That is the one place where the customer, rather than the setup, supplies the address.
Analytics report the location and the staff login — not which channel was used. If you need table tents measured against terminals, give the tents their own staff login and the split appears through the same mechanism.
7Feedback is a standalone customer feedback product. It collects a one-tap rating and an optional comment, photo or video where the visit ends — the payment terminal, the Self-Service Kiosk, a printed QR, the receipt or a chat-bot — and delivers every submission to the business with the location attached.
No. The terminal application installs next to your other Android apps and does not touch the payment flow, so it needs no payment-side certification. A printed QR or a fiscal receipt QR needs no integration at all. A deeper API integration exists for partners who want the question inside their own payment screens.
No. Scanning the code or tapping the terminal opens a web page. Rating takes one tap; a comment, a photo or a video is optional and never required, so the rating on its own is already a finished submission.
Not more often than once every few days, set per location. The frequency cap is blind to the rating: it exists to protect a regular from fatigue, not to protect the business from criticism.
A workstation: a till, a payment terminal, an API integration, or a badge QR belonging to one person. Ten tablets signed into the same staff login are one staff login. Five waiters who each need their own ratings are five.
No, and deliberately. A business picks one scale — Stars, Faces or Numbers — and every channel and location shows it. Mixing scales would make the numbers incomparable between a till, a table and a bot, which is the one thing chain analytics cannot survive.
Next step
One staff login, one table tent, one inbox. Add the terminal and the bot once you have seen what the first week brings in.
