New Member Workflow Overview

This guide is intended to outline the workflow and processes that need to occur for a new member to join the mesh. This follows a member from their initial contact through to them successfully being connected to the mesh.

This information is likely subject to change as our processes and systems evolve over time.

Join Form:
Everything begins when a user fills out our Join Form.
Submitting it assigns the user an install number, sends a support ticket, and adds a row to a spreadsheet in Google Docs we refer to as our "main spreadsheet."

We consider any new join request a "Potential Install" and they are displayed as gray dots on our map and are rendered from the spreadsheet using the map-nodes code on our Github.

Main Spreadsheet:
New nodes are displayed as gray dots on our map. They are rendered from the spreadsheet using the map-nodes code on our Github.

Support Ticketing

We use OSTicket for support tickets

Install viability, panoramas etc

A main bottleneck is figuring out which installs are viable. Usually this means line-of-sight to one of our supernodes, or a nearby kiosk.

Scheduling an install

Once an install is deemed viable we send a link to our calendar so the new member can book an install.

Acuity calendar

Info to come.

General Workflow Description:

  1. User fills out the join form

Ticket is automatically assigned the help topic "010-join form / rooftop" or "010-join form / standard".
Row with node number and user info is created in the main spreadsheet.
Ticket is created in OSTickets to be claimed by a NYC Mesh volunteer ("agent").
OSTickets sends auto-response asking for confirmation and a panoramic image of the user's view.

  1. Ticket is claimed by an agent.

On the ticket, agent should assign the Help topic “01 waiting for pano” and save.

  1. If no response from the user (maybe auto-response went to spam) agent sends Spam SMS following this procedure:
  1. User responds with a pano.

Agent should then reassign ticket to Jason Howard to add the pano the map.
Jason will assign the ticket back to Agent when pano is added.

  1. Agent should correspond with the user until install type is determined.

  2. Agent should then encourage the user to schedule an install.

On the ticket, send the canned response "25-Schedule an Install"

  1. The user will be directed to Acuity Scheduling where they will select an available install time slot.
  1. Installer volunteers to do install.

  2. Install info here.


Revision #4
Created 9 December 2023 04:39:59 by Willard Nilges
Updated 8 September 2024 02:08:01 by Lydon Thorpe