Skip to content
This repository has been archived by the owner on Mar 25, 2022. It is now read-only.

Add HELP DESK aka "FAQ" to New Design open for Growing #95

Open
katrinfriedmann opened this issue Oct 24, 2015 · 8 comments
Open

Add HELP DESK aka "FAQ" to New Design open for Growing #95

katrinfriedmann opened this issue Oct 24, 2015 · 8 comments

Comments

@katrinfriedmann
Copy link

LaGeSoNum HELP DESK

I have a Problem with
Pulldown or direct klicks, to what to do next or may be it s possible to work with typeform here?
Security
Authoritiez
Media

I need Food, where should ich go?
There is Food at 1pm at house J.

Questions we know the answer are answered right away.

My Number is not shown in any way since 6 weeks.

taskforce@moabit-hilft.de

@fzesch
Copy link
Collaborator

fzesch commented Oct 24, 2015

I think we should combine established techniques:

Ticket system for individual requests and complaints: refugees can file tickets and volunteers handle them.

FAQ: Collect knowledge, provide trustful information

A simple online forum is also a possibility, but usually it is hard to use on mobile devices (or does anybody know a good candidate?)

Some of our linux friend could try to set up a ticket system with support for multilingual frontends and backends.

@chrisN777
Copy link
Collaborator

@fzesch good idea! I would start in a different order. First FAQ, then Forum (if needed) and Mail or ticketing system at last. We should try to help as much as we can without a real person involved. The better the FAQ the less question we get via mail.

I found a two years old FAQ with Django Example (with tests!) https://github.com/howiworkdaily/django-faq If we add something like this @katrinfriedmann can write the questions in this wonderful json syntax: https://github.com/howiworkdaily/django-faq/blob/master/faq/fixtures/faq_test_data.json
;-)

Using an existing forums like wefugee.org was another idea today. Search for lageso covers not much for now: http://www.wefugee.org/k/questions/search?utf8=%E2%9C%93&q=lageso&submitted=

If all this doesn't help let em send a mail to the taskforce. If there are too many mails and they can't be handled by the taskforce, we could still add a ticket system. For this last step typeform seems like a beautiful solution. See the incident report for example: https://admin.typeform.com/gallery/workspaces/979764

@fzesch
Copy link
Collaborator

fzesch commented Oct 24, 2015

@chrisN777 I see your point with providing as much information as possible through FAQ and forum. But I still think we should set up a ticket system for several reasons:

  1. Documentation
  2. Prepare for scalability
  3. Enable people to collaborate on answers

This is all rather messy with plain e-mail. And from the refugee side there should not be much difference. But we can wait, of course with the ticket system. An important feature of the ticket system would be the availablity of an app, I think, or at least a mobile friendly interface.

@DaniGr
Copy link
Collaborator

DaniGr commented Oct 24, 2015

I'm fully for the ticketing system!!
Type form is very nice but doesn't work on mobile devices.

@AndreGCRamos
Copy link

@fzesch I also agree the FAQ should be a priority as it is rather easy to conceive and will do the job until the other features are ready.
Also agreeing on the ticketing system as it is better for everyone involved so we should brainstorm on that tomorrow morning and go from there. I think we (the frontenders) will have enough time to do some initial concepts and prototype for this as well, if needed.

@katrinfriedmann
Copy link
Author

@fzesch @DaniGr @AndreGCRamos Agreed! We will try to push FAQ and Ticketsystem as far as possible today!

@fzesch
Copy link
Collaborator

fzesch commented Oct 25, 2015

I think we can choose between OSticket and OTRS ? Any preferences? @DaniGr ?

@katrinfriedmann
Copy link
Author

@DaniGr @fzesch @ffflorian Design Ideas for FAQ & HELP DESK (as well transfered to @mcplanner and @AndreGCRamos)
1_lagesonum_help_desk
2_lagesonum_faq

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants