New Feature Feedback: SOS Support Alert - Mocks

[Michael]

Excellent!!! I totally get using the embedded map. Its organic to the app itself, and can translate over for those of us using it. I only recently discovered what3words, and really like that as a quick locator.
Again, Michael, this is fantastic, and although its a feature we all hope to never use, is certainly something that will be extremely handy if its ever needed!! Thanks for including us in the feedback for this.

When it gets closer to production, I assume you will be beta testing it externally? Would be interesting to see how this works, live, when its all rolled out and ready to go

Yes indeed - I will be able to set folks up to test - and hopefully iterate. Possibly next week. This will be the thread to watch for that. Thank you again!

 

[Michael]

This is a very good point and open to suggestions. The responder should verify the identity and credibility of the person requesting assistance. Similar to our Rally Points, Member status and Rating of the sender is a first indication of the persons legitimacy. It should be verified. Glad to dive into this topic for the best feature outcome.

I just thought of something not driven by business benefit (not the point of this feature) BUT - if this were a Member Only feature, it is unlikely the sender would have ill intent. Not guaranteed, but certainly a major filter.

 

[El-Dracho]

I like the idea. As others have written, it should be as easy to use as possible.

Perhaps more possibilities to inform members in the area can be used. For example, I use a real email address for 2 way communication on my inReach and would love to be able to get the notification there (good if no cell phone service).

Happy to participate in testing.

 

[DintDobbs]

I just thought of something not driven by business benefit (not the point of this feature) BUT - if this were a Member Only feature, it is unlikely the sender would have ill intent. Not guaranteed, but certainly a major filter.

I think that this is definitely true, and a good idea. It's unfortunate that it would be necessary, but it is better to prevent exploitation than to react to it.

It would also largely negate the risk for people abusing this app in other ways.

I personally think the feature in its proposed format is great.

Perhaps if you were using the "Record Track" function, it could be useful to show assisting drivers the path you took to get where you became stranded. Just a random thought. Like add a "Share Track" option (perhaps after an assisting driver has claimed the SOS).

Familiar users can already communicate this information using existing (member-only) features, so it might be redundant and unnecessary.

 

[socal66]

I have this unfortunate voice in my head that pops up from time to time that asks if the legal department has seen this and wonders what type of disclaimer language, terms of use, and/or related warning pop-ups they will want to ensure that OB avoids possible liabilities should things not happen or go wrong related to a call for assistance using the app.

 

[Michael]

I have this unfortunate voice in my head that pops up from time to time that asks if the legal department has seen this and wonders what type of disclaimer language, terms of use, and/or related warning pop-ups they will want to ensure that OB avoids possible liabilities should things not happen or go wrong related to a call for assistance using the app.

There will be disclaimers :)

 

[OTH Overland]

I just thought of something not driven by business benefit (not the point of this feature) BUT - if this were a Member Only feature, it is unlikely the sender would have ill intent. Not guaranteed, but certainly a major filter.

I would anticipate the likely hood of a ill intentioned person sending out a false SOS to lure in do-gooders with the intent of doing harm or relieving them of their expensive toys would be far less likely than the other way around where some lurker decides to run up and take advantage of someone in a sticky situation. They have a pretty good idea of the situation this person is in, likely how many people are with them and all kinds of info from the SOS, where as if you are the one baiting people in, you have no idea how many or who is coming and the added potential of Rangers/SAR/LEO's also being alerted. Not sure if it would even be possible, but a selector that would allow the sender of the SOS to restrict it to be received/viewable to Members Only would give them an option not to post it out to anyone that lurks around viewing, thus reducing their risk. Perhaps the SOS thread could be limited to Members Only.

 

[Michael]

Iterating on the auto-generated forum post format. Next post is the updated format. @oldsoldier181

Key info up top in line by line format, then a digest of additional info provided.

 

[Michael]

Support Alert: Created at 12:16 PM (GMT -5:00) on 12/20/2022 by (@Michael)

1. Location: 43.18421, -70.93508 (lat/lng) | 3 Word: mess.futuristic.limelight
2. Phone: 555-666-7777
3. Comms Channel 1: HAM | Channel: 146.460 | Notes:

Message:

Subaru stuck. It's not the traction...its the torque.

Additional Info:

Important links:

• OB1 Map Link
• Alert Announcement

Locations included in the Support Alert:

Location 1:
Coordinates: 60.06610, -105.10480 (lat/lng)
Address: 527 Kozey Camp, North Destinyshire, Comoros
Location note: Reiciendis eum assumenda aut modi nam.
Location 2:
Coordinates: 55.78340, 54.68340 (lat/lng)
Address: 452867, Кельтеевский сельсовет, Bashkortostan, Russia
Location note: Laboriosam et est.

Communications Channels included in the Support Alert:

Channel 1:
Type: HAM
Channel: 460
Notes: Robust hybrid monitoring
Channel 2:
Type: GMRS
Channel: 200
Notes: Pre-emptive mission-critical policy

View Support Alert

 

[OTH Overland]

I like the format!

 

[oldsoldier181]

Support Alert: Created at 12:16 PM (GMT -5:00) on 12/20/2022 by (@Michael)

1. Location: 43.18421, -70.93508 (lat/lng) | 3 Word: mess.futuristic.limelight
2. Phone: 555-666-7777
3. Comms Channel 1: HAM | Channel: 146.460 | Notes:

Message:


Additional Info:

Important links:

• OB1 Map Link
• Alert Announcement

Locations included in the Support Alert:

Location 1:
Coordinates: 60.06610, -105.10480 (lat/lng)
Address: 527 Kozey Camp, North Destinyshire, Comoros
Location note: Reiciendis eum assumenda aut modi nam.
Location 2:
Coordinates: 55.78340, 54.68340 (lat/lng)
Address: 452867, Кельтеевский сельсовет, Bashkortostan, Russia
Location note: Laboriosam et est.

Communications Channels included in the Support Alert:

Channel 1:
Type: HAM
Channel: 460
Notes: Robust hybrid monitoring
Channel 2:
Type: GMRS
Channel: 200
Notes: Pre-emptive mission-critical policy

View Support Alert

Mike, I like this format. Clean and to the point!

 

[El-Dracho]

I like the format. It is very clear and the recipient knows very quickly exactly what it is about. That is good.

I stumbled over the term support alert at the beginning. What about adding categories at the very beginning? Because sometimes you are just stuck but safe and it would not matter if someone comes to help now, in an hour or the next day. But it can also be critical, maybe because there is a danger of crashing or it happens on a beach, where maybe in 3 hours the tide sets in and the like. A good idea to consider?

By the way, I got a network timeout error when clicking on the button view support alert. Anyone else?

 

[oldsoldier181]

I like the format. It is very clear and the recipient knows very quickly exactly what it is about. That is good.

I stumbled over the term support alert at the beginning. What about adding categories at the very beginning? Because sometimes you are just stuck but safe and it would not matter if someone comes to help now, in an hour or the next day. But it can also be critical, maybe because there is a danger of crashing or it happens on a beach, where maybe in 3 hours the tide sets in and the like. A good idea to consider?

By the way, I got a network timeout error when clicking on the button view support alert. Anyone else?

Its not live. He is testing and monkeying around with it. You wont have access to it, as its still in development :). He is just soliciting feedback on a layout, info, etc

 

[El-Dracho]

Its not live. He is testing and monkeying around with it. You wont have access to it, as its still in development :). He is just soliciting feedback on a layout, info, etc

Thanks, I know, that was the reason why I gave feedback and shared my thoughts to this... but I was curious what happens when clicking the button and thought it works even in the design phase.

 

[Shahn]

Format looks awesome!

 

[UgotWheelz]

I like @Shahn idea of check boxes or radio buttons to simplify things, perhaps add a category to select the urgency of the situation, perhaps red/yellow/green coded to let people know how urgent the request is i.e. green: I have lots of gear and won't freeze if it takes a couple of days to get organized and come help, to red: rig is upside down, its raining and I have run out of cheez-its. Since it takes an internet connection to post the help request one would hope a really critical situation involved a call to emergency services or a press of an inreach button. ( a side wishlist item would be a way to text a help request into the OB system from an Inreach for non critical situations where you do not have any cell service)

Personally I’d be able to deal with the rig being upside down I’ve gotta come along I know how to use Robeson trees of being out of Cheez-Its is a major red alert!!!

 

[Michael]

Thanks, I know, that was the reason why I gave feedback and shared my thoughts to this... but I was curious what happens when clicking the button and thought it works even in the design phase.

Yup - known issue thank you! Links are not prime time yet.

 

[Michael]

I like the format. It is very clear and the recipient knows very quickly exactly what it is about. That is good.

I stumbled over the term support alert at the beginning. What about adding categories at the very beginning? Because sometimes you are just stuck but safe and it would not matter if someone comes to help now, in an hour or the next day. But it can also be critical, maybe because there is a danger of crashing or it happens on a beach, where maybe in 3 hours the tide sets in and the like. A good idea to consider?

By the way, I got a network timeout error when clicking on the button view support alert. Anyone else?

In the title the type of support requested will bold. Like:

 

[Michael]

Further post formatting - added quick copy buttons.

 

[DintDobbs]

@Michael The format is looking better and better, definitely a great idea to include the 'Copy' buttons to easily get the coordinates to an external app, if needed.

Perhaps an optional field for needed supplies which could be easily ignored in a panic situation (such as "need winch" or "need first-aid" or the like) could be added at the very end (this could be a "select all that apply"; I'd be happy to offer a list of options if this addition is considered). A level-headed person would probably just put this in the notes, but slowing the SOS sender a bit might help them to better evaluate the situation, preventing others from risking damage or wasting effort. It would be bad if a helper got stuck or injured because of coming ill-equipped to assist.

Just a thought. I know simplicity is ideal, but some times too much simplicity confuses the assister (think of 9-1-1 calls where the caller was too panicked to describe the situation correctly).