You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are over 10k volunteers who are not mapped and need to be contacted regularly. Currently outside the system. Need a system to message them by adding an 'Unapped Volunteers' list - just an exact replica of Contacts but unlike contacts, these people can be sent transactional SMS messages rather than only Promotional SMS messages. See this faq for the difference.
So essentially we can use the same SMS API to send messages to Volunteers as well as this new Unmapped Volunteers using the existing transactional interface.
The text was updated successfully, but these errors were encountered:
May be we need multiple contact sheets with different permissions. This
could become another contact sheet with only some people have permission to
view and edit, but every ward/AC coordinator can send SMS. Does it look
like a good idea?
There are over 10k volunteers who are not mapped and need to be contacted
regularly Currently outside the system Need a system to message them by
adding an 'Unapped Volunteers' list - just an exact replica of Contacts but
unlike contacts, these people can be sent transactional SMS messages rather
than only Promotional SMS messages See this faq for the difference http://wwwnccptraigovin/nccpregistry/FAQspdf
So essentially we can use the same SMS API to send messages to Volunteers
as well as this new Unmapped Volunteers using the existing transactional
interface
—
Reply to this email directly or view it on GitHub #2.
This seems to be his funnel. Delhi volunteer data (unverified and unmapped) is pulled at some interval, they are called and verified willingness to volunteer (outside of VMS) and they end us as unmapped with us. Even the Contacts from what I learned is data that will move to the Unmapped Volunteers category and then from there to regular volunteers. Balu was very clear we wont use this for public messaging.
Oh, the unmapped volunteers will minimum have a district and it will be up to the district coordinator to call and get them verified. Personally it is not a great idea. What workaround can we give?
There are over 10k volunteers who are not mapped and need to be contacted regularly. Currently outside the system. Need a system to message them by adding an 'Unapped Volunteers' list - just an exact replica of Contacts but unlike contacts, these people can be sent transactional SMS messages rather than only Promotional SMS messages. See this faq for the difference.
So essentially we can use the same SMS API to send messages to Volunteers as well as this new Unmapped Volunteers using the existing transactional interface.
The text was updated successfully, but these errors were encountered: