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

[FKrauss]

Can we do deeplinking? you know, like slack has: you log in the browser and
then redirects to the app (although they are an electrum app, i.e. a mini
browser).

if yes we could simply prompt people to go to the help center and then
deeplink them to a command to open support. As in a helpcenter it is
trivial to add a search box and recommendations and all that fancy fru fru

Anyways, I guess we have plenty of material to munch through before the
call. Let's just make sure we're effective in discussing it.

I would suggest we do the following agenda, assuming not everyone will have
read this thread but just so we give enough context for those who didn't so
they can still contribute to a valuable discussion:


   - What is the current state of support (to put everyone in the same
   page) @Steve, could you talk about this? - 10 min
   - What is the desired state of support (ignoring any constraints how
   would it work from the user and the DAO perspective, assuming problems
   exist and users don't have to become sys admins to get support) - I can
   moderate this one - 15 min
   - What are the tools / functionalities we need to have in place - 5 min
   - Outcome: a clear list of agreed functionality we need to do
   - What are the constraints we have in bisq specifically? - 5 min @Chris,
   could you talk a bit about this?
   - Which tools exist that could fill these and which functionality would
   have to be built? @Steve and I can talk about these - 10 min
   - Assigning implementation goals - who owns what and who helps
   who? @Steve and I can also lead these, I can also take ownership of further
   research or writing docs/specs for whatever we uncover above - 10 min

that adds up to 55 min... I hope that is enough time to cover everything
and I can keep us on track for the time too

Do you agree, or shall we take a different order/set of topics?

On Thu, 21 Nov 2019 at 10:45, Christoph Atteneder <notifications at github.com>
wrote:

> Or we hide to opening of the support dialog with a keyboard shortcut that
> is revealed after you haven't found anything in the KB? Of course that will
> only be a one-time hurdle, but could prevent the initial flood of noob
> support requests.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/bisq-network/growth/issues/164?email_source=notifications&email_token=ABEY5S57FDXRJEJTWNRMSGLQUZKB7A5CNFSM4JI45OZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZTGMQ#issuecomment-557003570>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABEY5S4R2J7PM2DLTBIWP5TQUZKB7ANCNFSM4JI45OZQ>
> .
>


-- 
*Fábio Krauss Stabel*

+45 93 93 21 31

PGP keys
<https://keys.mailvelope.com/pks/lookup?op=get&search=0xE5058064B3E7342F>


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