Mobile Directory with SMS
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
app
screenshots
.bowerrc
.editorconfig
.gitattributes
.gitignore
.jshintrc
Gruntfile.js
bower.json
package.json
readme.md

readme.md

Bridgely

Bridgely is a mobile directory with SMS capabilities that helps bridge the communication gap between HR departments and employees.

Features include:

  • Employee Registration by SMS
  • Autoresponders with uniquely generated urls
  • Send SMS messages
  • Send SMS questions and tag incoming responses as answers

Bridgely consumes the Twilio API to send and receive text messages. The Bridgely API must be configured with valid Twilio credentials in order to send or receive text messages with Bridgely.

Why Bridgely?

Bridgely is a mobile communications platform that enables company comminucation with with hard-to-reach employees, from a distributed team to an out-of-date or nonexistant mobile phone directory. It supoprts two-way communication, so companies can ask questions, store employees' responses, and filter through employees based on their answers.

Bridgely was built as a client project for ForUs, which will be using it to help corporations communicate information about retirement packages to their employees.

Screenshots

Mobile Directory: Bridgely Company Directory

Send a Question: Bridgely Send Question

Questions are stored in columns: Bridgely Show Columns

Bridgely Question Column

Bridgely Filter Employees

Company Settings: Bridgely Company Settings

Admin Companies View: Bridgely Company List

Front- & Back-end

I built Bridgely as two separate modules, a Backbone frontend and a Rails backend. I decided to take this route so the front-end could be customized and deployed for companies as necessary, and so the back-end could be scaled seperately to handle large directories and high volumes of SMS messages.

For a simple deployment the frontend can be run on the same server as the API. This is the default configuration. If your backend is served seperately, you just have to change one variable...see the Delpoyment Instructions below.

Tech Stack

Configuration

  1. If your backend is served elsewhere, point the bridgelyApp.apiUrl variable in app/scripts/main.js to your API
  2. npm install
  3. bower install
  4. grunt build

Deployment Instructions

  • grunt server to run locally.
  • Otherwise copy the dist folder to a publicly accessible folder on the server of your choice