How it works
The customer taps a rating where the visit ends. On the printed QR and a POS, a negative rating then opens a page for the manager and a neutral or positive one a page that can offer a Google review. You receive every review by email and in the Review journal, with the Staff Login attached.
Each channel has its own flow — one tap in Terminal Mode, follow-up pages on the printed QR and a POS, a request in the chat-bot — and all of them ask on the same scale.
Updated
Either the channel asks by itself at the end of an operation — Terminal Mode, your POS, the chat-bot — or a permanent QR sits where the experience happens.
Stars, Faces or Numbers — whichever the business picked. The rating alone is a complete review; in Terminal Mode it is the whole of it.
On the printed QR and a POS with the order id: after a negative rating, a page for the manager with a comment, up to three photos and a contact; after a neutral or positive one, a page that can offer a Google review.
An email about every review, and the review in the Review journal with its Staff Login — and, from a POS, the terminal, shift and cashier — 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 in the Customer feedback settings. While it is off, no place asks for a rating, the chat-bot included.
If it is offChannels stay silent, and nothing looks broken.
Inside the chat-bot channel: a request after every operation that added stamps, and a button in the bot's menu. 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
A rating from Terminal Mode, the printed QR or a POS carries the Staff Login it came through, and a Staff Login is a workstation: a till, a terminal, an API integration, a badge QR.
Ratings from the chat-bot and its web page have no Staff Login. The reports gather them in one Online row, and nobody is asked to pick a location.
Every rating also carries its Source — Terminal, Printed QR, Chatbot or Web card — and the dashboard and the Review journal filter by it. To tell one table tent from another, give it its own Staff Login.
7Feedback is a standalone customer feedback product. It asks for a one-tap rating in four places — Terminal Mode on the payment terminal, a printed QR, the Telegram or WhatsApp chat-bot and your own POS — and delivers every review to the business by email and in the Review journal.
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 needs no integration at all. Your own POS can ask through the Integration API if you want the question on its screen.
No. The terminal and the POS ask on their own screen, the printed QR opens a web page, and the chat-bot asks in the chat. Rating takes one tap, and the rating on its own is already a complete review.
It depends on the place. Terminal Mode asks only when the screen has nothing else to show. The chat-bot asks after every operation that added stamps, if that request is on. On a POS, the page with the Google button is offered to a customer the POS identifies at most once in ninety days, the page for the manager at most once a day. The printed QR asks whenever it is scanned. The business cannot change the spacing.
An entry point, not a person and not a device: a till, a payment terminal, an API integration, or a badge QR belonging to one person. It is signed in on one device at a time, so two tills serving at the same time need two Staff Logins. 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.
