2 results found

1. Carpool Bot

   This would be an OPT-IN only feature. Create a script that recognizes where each member is coming from without disclosing their precise location. Based on starting locations and where the activity starts i.e. trail head, let participants know based on that data how much of their likely drive routes match up. For example: You would get a notification that you and another participant are likely to share 90% of the same roads to travel to the activity. The user could set the tolerance of how much of the route to share. 70, 80, 90% etc. in order to get a notification. I hear a people often say they wish they knew how close another participant was prior to as they would have carpooled.

   This would be an OPT-IN only feature. Create a script that recognizes where each member is coming from without disclosing their precise location. Based on starting locations and where the activity starts i.e. trail head, let participants know based on that data how much of their likely drive routes match up. For example: You would get a notification that you and another participant are likely to share 90% of the same roads to travel to the activity. The user could set the tolerance of how much of the route to share. 70, 80, 90% etc. in order to get a… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Rosters  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Emails generated from email roster button should indicate hike post

   When you have the same people on multiple hikes and they use the "email roster" button to communicate with the group, it can be unclear which group they are communicating with unless that participant remembers to include those details in the subject or the body of the email. We should automate including information on which hike post the email was sent from.

   For example, if I get an email from "info@moutnaineers" suggesting a post-hike activity and I'm signed up for 10 hikes, I have no idea what date/hike the email refers to. I can look at the reply to but that doesn't help if I'm signed up to multiple hikes with that same person.

   When you have the same people on multiple hikes and they use the "email roster" button to communicate with the group, it can be unclear which group they are communicating with unless that participant remembers to include those details in the subject or the body of the email. We should automate including information on which hike post the email was sent from.

   For example, if I get an email from "info@moutnaineers" suggesting a post-hike activity and I'm signed up for 10 hikes, I have no idea what date/hike the email refers to. I can look at the reply to but… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  Rosters  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating