Should I provide feedback directly in the app or go to Discord?
- English Version
- 中文
We officially launched In-app customer support after version 1.8. Users can directly propose suggestions and feedback to the team within Heptabase desktop and web app, and can also directly report bugs.
This brings three benefits:
Better tracking of bug reports in the app
The system we chose supports creating bug reports as tickets. Each ticket has its own progress that can be tracked. When the bug is resolved, users can directly receive notifications within Heptabase. If the progress is not as expected, users can also ask us about the progress at any time. We believe that this will provide a better experience for users.
More intuitive and unified experience
Among Heptabase users, about 10% actively participate in Discord discussions. However, some users do not use Discord and prefer 1-on-1 feedback and discussions. For these users, being able to provide feedback at any time while using Heptabase will be a more intuitive experience.
Increased team efficiency
Through the new system, we can ask for a lot of necessary information when collecting user feedback, such as the operating system used, version, usage scenarios, etc. This information is necessary for identifying the cause of bugs or thinking about product solutions. In the past, we had to ask back and forth through Discord, which took more time. Now we can collect necessary information through a chatbot, which makes the team handle feedback more efficiently and thus provide better service.
On the other hand, we understand that many users really like the Heptabase Discord community. In the community, they can not only directly communicate with the team, but also interact with other users, and learn various Heptabase usage tips and tricks from user sharing. Therefore, we also want to share what types of feedback we suggest to be conducted in the app, and what types of feedback can continue to be left on Discord:
Feedback to be made in Heptabase:
Bug report
For better tracking and handling, we suggest that all bug reports be submitted in Heptabase. If you can't even log into Heptabase, we recommend sending an email to support@heptabase.com. We will assist in resolving the login issue as quickly as possible.
Feedback needs to be tracked
Since our system supports "continuing the conversation", you can supplement your thoughts on a piece of feedback or inquire about its progress.
Discussions involving personal privacy
Sometimes the content of your feedback or the information in the screenshot may not be suitable for public viewing. This type of feedback is also suitable for handling through the built-in support system that only the team can see.
Feedback to be made in Discord:
Purely casual chat, sharing, or content to encourage and praise the team
We are very welcome for you to share these types of content with everyone in the community through Discord.
Just giving suggestions or brainstorming without specifically tracking progress
We know that sometimes you are not very sure about some feedback and want to hear what other users think. For this type of content, we think it's very suitable to discuss in Discord. If after the discussion you are more certain about your ideas and want to track them later, you can repost them in Heptabase.
Finally, the above suggestions are not mandatory. We still hope that each user can provide feedback to us in the most comfortable way. We value the opinions of each user very much. Because of this, we always want to handle each user's opinions better and not let anyone feel neglected or ignored. Therefore, we look forward to making our customer support better through the launch of the new system and creating a product that meets everyone's expectations.
什麼時候該在 Heptabase 裡面回饋?什麼時候該在 Discord 裡面回饋?
我們在 v1.8 的更新後,正式啟用了 In-app 的 customer support ,用戶可以直接在 Heptabase 裡面向團隊提出建議與回饋,也可以直接回報 Bugs 。
這帶來了三個好處:
In app 的 Bug report 更好追蹤進度
我們選用的系統支援將錯誤回報創建為 Ticket ,每個 Ticket 都有他的處理進度可以追蹤,當這個錯誤解決後,用戶可以直接在 Heptabase 裡面收到通知。而若處理進度不如預期,用戶也可以隨時再向我們詢問進度。我們相信,這樣對用戶來說體驗會更好。
更直覺統一的體驗
在 Heptabase 的用戶中,大約有 10% 會積極的參與 Discord 的討論,但有些用戶並未使用 Discord ,也更喜歡 1 對 1 的回饋與討論,對於這些用戶來說,在使用 Heptabase 時就可以隨時給予回饋,將會是更直覺的體驗。
增加團隊的處理效率
透過新的系統,我們可以在收集用戶回饋的同時就詢問許多必要的資訊,例如使用的作業系統、版本、使用場景等等,這些資訊對於判別 Bug 的成因或者是思考產品的解決方案都很必要。過去透過 Discord 必須一來一往詢問,這會耗去較多時間。現在我們可以透過 Chatbot 收集必要的資訊,這將讓團隊處理回饋更有效率,也因而能提供更好的服務。
另一方面,我們也理解,許多用戶很喜歡 Heptabase 的 Discord 社群,在社群中不僅能夠直接與團隊對話,也能夠跟其他的用戶交流,並從用戶的分享中學到各種使用 Heptabase 的技巧與訣竅,因此我們也想要分享一下,接下來我們建議哪些類型的回饋要到 app 裡面進行,哪些類型的回饋可以繼續留在 Discord:
建議在 Heptabase 裡面提出的:
Bug report
為了更好的追蹤處理進度,我們建議 Bug report 都在 Heptabase 裡面提出。若連 Heptabase 都無法登入,我們建議可以寄信到 support@heptabase.com ,我們會用最快的速度協助解決無法登入的問題。
你希望能夠隨時關心處理進度的回饋
由於我們的系統支援「繼續對話」,因此你可以針對一個回饋補充你的想法,或者是關心處理的進度。
涉及個人隱私的討論
有時你回饋的內容或者截圖的資訊可能較不適合公開給其他人,這類型的回饋也適合透過只有團隊看得到的內建支援系統進行。
建議可以在 Discord 提出的:
單純閒聊性質、分享性質、或者想要鼓勵與讚美團隊的內容
這類型的內容我們還是非常歡迎你透過 Discord 跟社群的大家一起分享。
只是單純給建議或發想,不用特別追蹤進度的回饋
我們知道,有的時候有些回饋自己也不是很有把握,也想聽聽其他用戶怎麼想。對於這類型的內容,我們覺得也很適合放到 Discord 來討論。假設討論過後你更確定你的想法,希望之後能夠追蹤,你也可以再到 Heptabase 裡面重新貼一次給我們。
最後,上述的建議都不是強制性的,我們仍希望每個用戶都可以用自己最舒服的方式提供回饋給我們,我們非常重視每個用戶的意見。也正是因為這樣,我們一直想要更好地處理每一個用戶的意見,不要讓任何人有被冷落、或者是被忽略的感覺。所以我們期待接下來透過新的系統上線,我們能將 Customer support 這件事情做得更好,打造出更符合大家期待的產品。