User feedback (My requests tab, replies, unread counter, offline queue)
User feedback is useful only when the person who left it can see what happened next. Bugfix gives every visitor a “My requests” tab inside the widget: their own bugs and ideas with screenshots, and the answers of your team, all in one place.
How user feedback works in Bugfix
The widget collects four types of messages: bug, idea, “unclear” and review. The feedback button inside the widget gathers impressions as well, not only breakages, so the same channel carries complaints, ideas and moments when something is unclear.
Each message goes to the team, and the answer of the team appears in the widget on the “My requests” tab. The history is kept by the identifier of the device, the time is shown in the local time zone and not in UTC, and the look of the tab follows the skin of the site.
The “My requests” tab
User feedback in Bugfix lives on this tab. It shows the visitor:
- their own bugs and ideas, with the screenshots they attached;
- the answers of the team to each of them;
- the time of every message, in local time;
- the number of replies that have not been read yet.
The visitor does not need an account for this. The list is built from the identifier of the device on which the messages were written.
Replies: threads, ticks and two kinds of answer
User feedback is a conversation, so a reply can be sent into a thread. Branches are shown with an indent, up to 3 levels deep. Next to each message there is a tick: ✓ means sent and ✓✓ means read. A counter shows how many messages are unread.
The team answers in two ways:
- “fixed in version N” with an explanation, shown as the mark “✅ Fixed in vN”;
- an ordinary reply from a developer.
A queue that does not lose messages
If a message could not be sent, it goes into a queue marked “not sent” or “not delivered” and is sent again later. A dropped network does not make the message disappear. Attachments are kept on the device while they wait.
Access to other people's requests is closed. Data is read only by the visitor's own device identifier, and there is no direct reading of the table.
Where user feedback helps and how to connect
- A visitor comes back to see what happened. The message, the screenshot and the reply wait on the tab.
- A weak connection. The visitor writes in a place with a poor network, and the queue delivers the message later.
- A bug that gets fixed. The visitor who reported it later sees the mark “✅ Fixed in vN” with an explanation, or an ordinary reply from a developer.
- Ideas and impressions. The feedback button collects them next to bug reports.
Connection is the usual one-tag installation of Bugfix with the key of the site in data-project. The loader fetches the current widget from the center.
Limits of the history
User feedback history has a few firm limits, listed here.
- The history is tied to the device and not to an account. On another device the visitor will not see it.
- Other people's requests cannot be opened: the data is read only by the own device identifier.
- Messages from the widget are received and stored on the Bugfix infrastructure, in a Supabase database, and screenshots lie in private storages.
Frequently asked questions
Where does a visitor read the replies of the team to user feedback?
On the “My requests” tab inside the widget. Replies appear in threads, messages carry ✓ and ✓✓ ticks, and a counter shows what is unread.
What happens if the network drops while a message is being sent?
The message waits in the queue marked “not sent” or “not delivered” and is sent again later. Attachments are kept on the device.
Will the history be available on another device?
No. The history is tied to the identifier of the device, not to an account, so another device starts with an empty list.