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

[Christoph Atteneder]

> the only issue is overwhelming the support agent with low touch requests, things that would be solved by checking slack or so. maybe we make a mix of helpcenter/knowledge base articles and support chat? Similar to what most websites have where you first need to dig the KB a bit before you can talk to a human for support
> […](#)
> On Thu, 21 Nov 2019 at 10:13, Christoph Atteneder ***@***.***> wrote: Maybe similar to arbitrator/mediator selection a random support agent is selected and the message is encrypted with its public key. The support agent has to decrypt the message after in the support tool of choice. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#164?email_source=notifications&email_token=ABEY5SY25YL37M4GASPUQJ3QUZGLNA5CNFSM4JI45OZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZQCEI#issuecomment-556990737>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABEY5SZTVGK634J7SZU3A73QUZGLNANCNFSM4JI45OZQ> .
> -- *Fábio Krauss Stabel* +45 93 93 21 31 PGP keys <https://keys.mailvelope.com/pks/lookup?op=get&search=0xE5058064B3E7342F>

Unfortunately the regular common support SDK integrations with this KB article suggestions is no way for us. Implementing it ourselves might be quite a lot of work. Maybe it is enough to point the user to the knowledge base website first and if she opens a support ticket within the app it has a cost (BSQ?). But I probably would be pretty pissed if I have to pay for support if there is a bug in the app itself.

-- 
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-557002930
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191121/a96ea324/attachment.html>