Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Programmable, prioritized communication methods when sending/planning checkins #218

Open
Erioldoesdesign opened this issue Oct 11, 2019 · 0 comments
Labels
Back-end issues Back end issues Design: Usability + Inclusion Ready for design usability/inclusive design Design: User Research Ready for user research Design: UX Ready for design UX Feature: Check-In An issue that is related to TenFour's check-in experience Feature: People An issue that is related to TenFour's people experience Feature request A feature that has been requested by the community or by users Front-end Issues that need Front-end code/edits Open Design issue An issue identified for an Open Design event P2 - Normal Tech debt Issues that have been a result of technical debt

Comments

@Erioldoesdesign
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
I'm always frustrated when...I cannot plan and customize the way that certain communications are sent out in TenFour and it just blasts my people with multiple methods of responding to a check-in

Describe the solution you'd like
As a user constructing a check-in to my people, I want to be able to select multiple different communication methods and prioritize or pick which method sends first, then what method sends second after an allotted time frame. The admin user could set this globally for all authors e.g. & app message (push) then SMS, the email, Slack, then call etc. with timers on each method if a reply isn’t received then TenFour follows the flow until it receives a reply. The user could also configure multiple attempts of one messaging method e.g. In-app 1, email 1, in app 2, SMS 1, email 2, SMS 2 etc.

This could also include using feature #217 as a fall back/programmable option.

@Erioldoesdesign Erioldoesdesign added Medium Priority Front-end Issues that need Front-end code/edits Back-end issues Back end issues Feature: Check-In An issue that is related to TenFour's check-in experience Feature: People An issue that is related to TenFour's people experience Feature request A feature that has been requested by the community or by users P2 - Normal Tech debt Issues that have been a result of technical debt Open Design issue An issue identified for an Open Design event labels Oct 11, 2019
@Erioldoesdesign Erioldoesdesign added Design: Usability + Inclusion Ready for design usability/inclusive design Design: User Research Ready for user research Design: UX Ready for design UX and removed Medium Priority labels Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Back-end issues Back end issues Design: Usability + Inclusion Ready for design usability/inclusive design Design: User Research Ready for user research Design: UX Ready for design UX Feature: Check-In An issue that is related to TenFour's check-in experience Feature: People An issue that is related to TenFour's people experience Feature request A feature that has been requested by the community or by users Front-end Issues that need Front-end code/edits Open Design issue An issue identified for an Open Design event P2 - Normal Tech debt Issues that have been a result of technical debt
Projects
None yet
Development

No branches or pull requests

1 participant