One Online row
Chat-bot ratings have no Staff Login, so the reports gather them in one Online row, with the source Chatbot or Web card.
Channel
Where the customer already is
In markets where a messenger is the default way to reach a business, the bot is the shortest route to a rating: two taps, no browser tab to find, no card to carry.
In Telegram the bot asks on the business's scale inside the chat. In WhatsApp it sends a link to a web page that asks on the same scale; a written comment there is optional.
At a glance
- Trigger one
- A request after every operation that added stamps
- Trigger two
- A permanent button in the bot menu
- Master switch
- Neither fires while collection is off
- Attribution
- One Online row in the reports
Updated
What the bot channel adds
It is the only channel where the conversation continues after the rating, and that changes what it is worth.
01
Two taps, no tab
The request arrives in a thread the customer already has open, as the last message after the operation.
02
No frequency limit
Every operation that added stamps and reaches the bot ends with the request. If that is too often, switch it off and keep the menu button.
03
A permanent way in
The menu button is not tied to any visit, so a complaint about last Tuesday still has somewhere to go.
In the thread
The request, then the rating
After an operation that added stamps the bot asks in its last message, while the impression is fresh and without anyone on the staff doing anything. The rating is stored and reaches the business; the bot offers no Google step.
Either, both or neither
The two triggers are independent, and the master switch on the profile governs both of them.
One queue still
A bot rating lands in the same Review journal as a terminal one, and the business gets an email and a Telegram message about it.
Common questions
What is 7Feedback?
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.
Do we need to integrate with our POS?
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.
Does the customer have to install anything?
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.
How often is the same customer asked?
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.
Next step
Switch on the trigger that fits your market
Some businesses only want the menu button. Some want the request after every operation. Both are one setting each.