Last updated September 23, 2018 by olivernyc
Everything begins when a user fills out our Join Form.
Submitting it assigns the user a node number, sends a support ticket, and adds a row to a spredsheet in Google Docs we refer to as our “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.
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.
Info to come.
General Workflow Description:
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.
Ticket is claimed by an agent. > On the ticket, agent should assign the Help topic “01 waiting for pano” and save.
If no response from the user (maybe auto-response went to spam) agent sends Spam SMS following this procedure:
Go to the ticket and copy the phone number.
Sign into firstname.lastname@example.org.
On the left you’ll see the NYC Mesh icon with a “+”. Click on the plus, and paste in the phone number. Click on “Send SMS”.
Back at the bottom of the ticket, select the canned response “15-spam sms message”. Copy the generated message. Do not send this message to the user via the ticket.
Paste this message into the SMS text area and send the SMS.
Back at the ticket, click on “Post Internal Note” and paste the message there as well.
Edit the ticket and assign it the Help topic “012-sent spam sms” and save.
If another week goes by with no response, then close the ticket.
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.
Agent should correspond with the user until install type is determined.
Agent should then encourage the user to schedule an install. > On the ticket, send the canned response “25-Schedule an Install”
The user will be directed to Acuity Scheduling where they will select an available install time slot.
- The selected time slot will appear in the “NYC Mesh Community Network” google calendar.
- The event needs to be copied into the “install requests” google calendar.
Installer volunteers to do install.
Install info here.