Technical and
social feedback
social feedback
About us
Contacts
UA
partners
RUs
ENG
Hi, we are a team from Ukraine, who has terminated all contracts with clients that are supporting the aggressor, but keeps working in war conditions. We pay our taxes, thus supporting the economy of our brave country and we are extremely happy to cooperate with new partners who share our values and strive to make a qualitative leap in the development of decentralized economy around the world.
Services
Services
The problem:
The solution:
Budget:
Time frame:
30 days
Project bugs. Every project has all kinds of bugs and misunderstandings. And it does not depend on the level of interaction with its audience and the developers staff. The services of IT and Social testers are the first solution that comes to mind in this situation. But this is expensive, and in addition, such services are often disposable, that is, they need to be repeated periodically (after updates, implementation of new features and other things).
1300$
Described the rhetoric for working with the project;
Regular search and analysis of bugs without additional reminders about them.
Our managers review all information about the project in the media space on a daily basis: system failures, design errors, objections, audience problems, etc. Daily and weekly reports on collected external and internal bugs are transmitted to the project management.
External problems include detected bugs and errors (including effective options for fixing them). Internal problems are collected in the report on support and study of the project's media space: reporting information on chat support, assessment of the mood of the project audience, squeezing out the current questions, problems and objections of the project audience (and here effective options for solving them are also attached).
Thus, the project receives full-fledged detailed reports on the state of affairs, which allows you to eliminate possible serious consequences in advance.
Our managers review all information about the project in the media space on a daily basis: system failures, design errors, objections, audience problems, etc. Daily and weekly reports on collected external and internal bugs are transmitted to the project management.
External problems include detected bugs and errors (including effective options for fixing them). Internal problems are collected in the report on support and study of the project's media space: reporting information on chat support, assessment of the mood of the project audience, squeezing out the current questions, problems and objections of the project audience (and here effective options for solving them are also attached).
Thus, the project receives full-fledged detailed reports on the state of affairs, which allows you to eliminate possible serious consequences in advance.
We have:
Wrote two separate instructions for managers on these tasks;
Determined the number of monitored chats: 17 (4 internal and 13 external);
Made 602 reports, including:
- 572 observations on chats (this report is written for manager check and supervisor evaluation, this type of report is only used in external chats to find important and interesting cases or project mentions, 1 report is written in 24 hours at a time);
- 30 daily summaries, in which the most important cases are selected and the statistics on the moderation of chats.
Collected 86 frequently asked questions from the community.
Found and fixed 60 bugs/errors in the application and on the website;
The Result:
table 1
table 2
After a month of analysis, chatting and constant feedback, we identified a large number of technical bugs in the app and on the website, which were successfully fixed. By providing timely reports and solutions to social problems, we were able to increase trust in the product as well as bring developers and the community closer together.
The developers of the project started releasing DEV.News (developer diaries), where they answered questions from their community (which we provided them);
Statistics:
Every week the developers were fixing bugs and errors in the application and website, thanks to such intensive work the crude products became more complete, having received good ratings from the community;
Users of the product started to ask for help from tech support less, because answers to frequently asked questions were given in advance.
Community trust in the developers increased by 40%, as constant interaction and feedback was seen;