search

HTBox / allReady

This repo contains the code for allReady, an open-source solution focused on increasing awareness, efficiency and impact of preparedness campaigns as they are delivered by humanitarian and disaster response organizations in local communities.
http://www.htbox.org/projects/allready
MIT License
891 stars 627 forks source link

Status of SMS integration? #1510

Open schuback opened 7 years ago

schuback commented 7 years ago

Do we have SMS/Text set up for notification? Need to be able to ping a volunteer manually from admin, but also schedule an auto reminder alert. User needs to be able to set up alert notification type as well (email/sms)

tonysurma commented 7 years ago

@schuback @OhMcGoo can you document desired behavior / issues and then it can be implemented or updated compared to current functionality? cc @mgmccarthy as FYI

mgmccarthy commented 7 years ago

@schuback what are the existing Issues related all the items you listed in your comment above?

Our Issues are labeled P1 and P2 and I know not many P2's have been worked on at this point. I can say with a good amount of certainty that the third bulleted item has been deferred to P2.

schuback commented 7 years ago

Hi @mgmccarthy -

-Pinging a volunteer manually from the admin. -scenario. the admin needs to alert a single or multiple (selected) volunteers about a task change/update and/or during the actual task time by using a SMS message or email.
-scheduling an auto reminder alert for a task. -I look at this like a meeting reminder. Either the admin or the volunteer can set up a 1 day reminder or 2 hour reminder. -scenario. a volunteer might sign up for multiple task that happen at different times during the day (or they could be stacked backed to back). They can set up a reminder that they need to wrap up and get to the next task. -User needs to be able to set up alert notification type -Like a reminder in a calendar event, being able to set up that reminder as a text or email -scenario A volunteer or admin would set up an email reminder prior to the event but the day of the event, all reminders would be a SMS.

Thank you for the definition of the P1 and P2. I need to go back and review all the P2. I am just glad that @tonysurma assigns those for me.

Let me know if you have any questions. Thank you!!

mgmccarthy commented 7 years ago

@schuback

can we make this item automated?

Pinging a volunteer manually from the admin. -scenario. the admin needs to alert a single or multiple (selected) volunteers about a task change/update and/or during the actual task time by using a SMS message or email.

specifically, if a task changes along the data points you mention, all volunteers are notified. This would be the default behavior. Volunteers could then "opt out" of those notifications if they do not wish to receive them.

This should take the responsibility off of the admin for having to remember to do this, and instead, put the control into the hands of the people receiving the notifications.

The same thing can apply for the other items you mention. Make this an automated part of the system, and allow the people receiving the notifications opt out instead of building a UI and code that makes users specifically target and pick out people they want to notify

Thoughts?

schuback commented 7 years ago

The automated process is great. I feel that there needs to be a way for an admin/manager be able to ping 1:1 Although, if we have the phone number of the users we can have them call. This is more of safety feature and having the ability to direct contact an individual.

We can close this for v.1 and look at it once we have real events taking place and user feedback.

On Fri, Apr 28, 2017 at 1:34 PM, Michael McCarthy notifications@github.com wrote:

@schuback https://github.com/schuback

can we make this item automated?

Pinging a volunteer manually from the admin. -scenario. the admin needs to alert a single or multiple (selected) volunteers about a task change/update and/or during the actual task time by using a SMS message or email.

specifically, if a task changes along the data points you mention, all volunteers are notified. This would be the default behavior. Volunteers could then "opt out" of those notifications if they do not wish to receive them.

This should take the responsibility off of the admin for having to remember to do this, and instead, put the control into the hands of the people receiving the notifications.

The same thing can apply for the other items you mention. Make this an automated part of the system, and allow the people receiving the notifications opt out instead of building a UI and code that makes users specifically target and pick out people they want to notify

Thoughts?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTBox/allReady/issues/1510#issuecomment-298074178, or mute the thread https://github.com/notifications/unsubscribe-auth/AAyqVEnBE83h5ArXkIzc9M1-GgWtYmarks5r0jE6gaJpZM4K0zeg .

--

Pascal Schuback pascal@schuback.com 206.414.8799 @schuback

mgmccarthy commented 7 years ago

@schuback

This is more of safety feature and having the ability to direct contact an individual.

in what way is it a safety feature? can you expand on that? I just want to make sure I'm not missing an important concept here.

schuback commented 7 years ago

If the admin/event manager needs to share a message to the team lead or individual person (safety threat, concern) they can ping the person directly and not ping the whole team/public.

On Fri, Apr 28, 2017 at 3:12 PM Michael McCarthy notifications@github.com wrote:

@schuback https://github.com/schuback

This is more of safety feature and having the ability to direct contact an individual.

in what way is it a safety feature? can you expand on that? I just want to make sure I'm not missing an important concept here.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTBox/allReady/issues/1510#issuecomment-298095510, or mute the thread https://github.com/notifications/unsubscribe-auth/AAyqVLhLjO3vS83nXCHw-DhqqEYeDngNks5r0kgWgaJpZM4K0zeg .

--

Pascal

mgmccarthy commented 7 years ago

Ok, that is good info to know. We need to build a UI/functionality for that specific use case b/c it seems like an very important thing (safety threat etc..)...

Thanks!

schuback commented 7 years ago

That would be great. A UI for it would be great. It can be done on the next version.

On Fri, Apr 28, 2017 at 3:22 PM Michael McCarthy notifications@github.com wrote:

Ok, that is good info to know. We need to build a UI/functionality for that specific use case b/c it seems like an very important thing (safety threat etc..)...

Thanks!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTBox/allReady/issues/1510#issuecomment-298097596, or mute the thread https://github.com/notifications/unsubscribe-auth/AAyqVD7emyBBw7yXe6X1tR5Idu2PAspbks5r0kqMgaJpZM4K0zeg .

--

Pascal

mgmccarthy commented 7 years ago

@schuback, digging into this even deeper, what would an example be of a "safety threat, concern , etc..." for a given Campaign/Event?

schuback commented 7 years ago

@mgmccarthy https://github.com/mgmccarthy great question! I will give you some examples for different scenarios.

For a smoke detector install day. Security/safety issue could be identified threat with a location and need to round the team up without attention, possible issue back at basecamp (starting point).

For other use cases, you could have a family member/friend looking for family member/friend on different teams (example during sand bagging event, people can be separated during the team set up process). During volunteer events, like a clean up post incident, you could have a house that has been identified as a security risk that would require the team leader to know the information.

On Mon, May 1, 2017 at 5:26 AM, Michael McCarthy notifications@github.com wrote:

@schuback https://github.com/schuback, digging into this even deeper, what would an example be of a "safety threat, concern , etc..." for a given Campaign/Event?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HTBox/allReady/issues/1510#issuecomment-298320959, or mute the thread https://github.com/notifications/unsubscribe-auth/AAyqVOZDoALX3ItUbYISMFHK53Yz6Osoks5r1cF9gaJpZM4K0zeg .

--

Pascal Schuback pascal@schuback.com 206.414.8799 @schuback