An extensible, customizable real-time queue system, built with Meteor!

HELPq was originally built for HackMIT, but has been used at hackathons like Blueprint, Meteor Summer Hackathon 2015, WHACK, MakeMIT and WildHacks (among others!).

It is a real-time help queue and mentor management application, targeted at hackathons and classrooms, where there is a need for issues to be claimed and satisfied within minutes. It includes a simple interface for requesting tickets, claiming tickets, administrating users/mentors, and examining metrics.

It is built with an emphasis on three fundamental user experiences:

Students should be able to log in and do exactly what they want - submit a ticket. Nothing more complicated than that.

Mentors should not receive any type of push notifications when tickets are requested. Instead, mentors should be pulling from the mentor view and claiming tickets whenever they see them. That way, mentors will not get annoyed by a feed of requests and instead provide high-quality advice because they are themselves actively seeking out people to help.

Mentors can claim tickets, complete tickets, or choose to reopen them. Mentors can only claim a single ticket at any given time. There is no ability to message a student through the app in order to encourage a mentor to find that student and help them in person. A student can, however, choose to include other contact information in case contact is needed to clarify location.

Users can request a ticket, by providing their problem description, where they are, and how they can best be contacted. This copy can be easily modified in one of the config files!

Once submitted, users have an option to cancel their ticket ("Nevermind!"). Tickets will also expire based on a value determined by the admin.

Admin can send out announcements with varying colors through the admin dashboard, which appear on on the home screen.

The mentor status bar shows how many mentors are currently online, and calculates the expected wait time based on historical ticket claim and completion times.

The current queue shows who is currently in the queue and which people are currently receiving help. Because the nature of questions available mentors can address are highly variable, tickets will often not be answered in order of submission.

Mentors should be mobile, and the HELPq is designed for mentors to browse the help tickets on their smart phones.

If a user is a mentor, they will have an inbox icon in the top right they can click to navigate to the mentor view. If the HELPq is being viewed on mobile or a very narrow window, the app is responsive and will pull up a navigation bar on the bottom for Home, Mentor, and Profile.

You can claim a ticket by selecting "Claim Ticket". This will notify the user that you are on your way! Once a ticket is claimed, you cannot claim another ticket unless you complete or reopen the ticket.

Once you are done working with a student, you should mark that ticket as completed. This will give the student an opportunity to rate their experience with you!

You can choose to reopen the ticket if you feel like you could not adequately solve the problem, or think someone would be better at addressing it.

The admin dashboard has a lot of useful features for hackathon organizers or class staff! Shown above is the Metrics dashboard.

The announcement section allows you to create announcements for the home screen, with a variety of different colors.

The users table lets you see all of the current users, and mark them as mentors or admins. You can also edit other user's information - of course, be responsible with this power!

Login is done through Github or Facebook (which can be enabled or disabled in a config file), but you can manually create user accounts.

This takes a CSV formatted string, which will then check your format, and create users asynchronously. If a user's account creation fails, the result will be shown.

This feature was designed for use in classroom settings, or other restricted access settings, so that you can create an account for each student and a password unique to them.

This feature is also useful for when a user does not want to login with Facebook or GitHub (even though only public information is retrieved).

The tickets table will show you a history of all tickets.

• Green: tickets have been completed
• Red: tickets that have been cancelled
• Yellow: tickets that have expired
• Grey: tickets that are currently claimed

The metrics pane shows a lot of information regarding the usage of the queue.

The first is a metrics summary, which includes average, median, and std dev of response time and completion time, as well as the raw average of all ticket ratings.

The leaderboard also shows the top 10 mentors with ratings. Their rating is not a raw average of their tickets, but instead blurred slightly with weighting. This is to avoid the situation where a user with a single 5 star rating would be listed above another user with four 5 star ratings and a single 4 star rating.

The feedback section is a feed of all mentor feedback, with star rating and a note. Bad ratings are highlighted.

Settings allows you to adjust various settings in the queue. Right now, you can open/close the queue and set the time for when tickets expire.

We've used this at a bunch of hackathons and we have some data on them :)

Make sure that you have meteor installed. You can install Meteor through their website.

When deploying to Heroku, you must set at least the ROOT_URL and ADMIN_PASSWORD environment variables.

  ./create_config
  meteor

Copy the private/config.json.template into private/config.json

  meteor

IMPORTANT

Without login configuration, you will only be able to login with the admin username and password specified in private/config.json (or the corresponding environment variables).

If you're not using Heroku, you can deploy with:

  meteor deploy <your domain name>.meteor.com

To configure login, edit private/config.json. Alternatively, you can configure login using the environment variables listed in app.json (this is especially useful when using Heroku).

In private/config.json (or the corresponding environment variables), provide the appropriate application id/secret combinations for either Facebook or Github authentication, or choose to disable them.

For front end branding, edit client/stylesheets/scss/_branding.scss

In this file, you will find brand variables and classes for the main splash and main banner.

You can edit these and observe the changes. There are also comments to explain what each setion does.

To edit copy, edit lib/constants.js.

In this file, you will find a place where you can change various strings across the site, including the title of your app.

The queue has been found to be most effective with an orientation with mentors and a tight integration with the way a hackathon/classroom manages mentorship. If you'd like to talk about how this could work for your hackathon/classroom, don't hesitate to email me at ehzhang@mit.edu!

Have you used HELPq or are planning to use it at your hackathon? I'd love to hear how effective it was, what kinds of metrics you got, and what kinds of things people wanted. Don't hesitate to email me at ehzhang@mit.edu!

I'd love to take pull requests! Please read the Contributing Guide first!