[bisq-network/growth] [CALL] Addressing the Bisq Support Workflow - Bisq BRIEF for November 21 (#164)

[Christoph Atteneder]

> * Regardless of how support is "officially" handled, Bisq communication platforms are destined to be disparate, especially as it grows around the world, and people will inevitably reach out on all of them. Therefore any solution will need to handle support requests coming in from a changing array of channels. It seems to me that **a designated group of people following a designated array of channels** (adjusted and adapted as the user base changes) is the only way to conquer this. These people should follow these channels, respond where possible, and redirect any unsolved cases to the ticketing system.

One way to solve this, suggested by @wiz, is to include support within the Bisq app and use the onion address as identity handler. Support requests are sent similar as we do it with the mobile notification service over a relay server to forward the requests to a support API. Encryption and decryption of the message when forwarded it to the support system of our choice has to be discussed.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/growth/issues/164#issuecomment-556989962
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191121/bdfa75c3/attachment.html>