-
Notifications
You must be signed in to change notification settings - Fork 1
Compare PMM, V4S and Hybrid
- Managing multiple Programs and Services and tracking impact and outcome
- Volunteers doing programmatic work
- Connecting Volunteer to a specific service delivery
- Volunteers doing programmatic work
- One on one Mentor/ Mentee Tracking
- Simple Volunteer Tracking
- Supporter Group Tracking
Benefits/ Considerations:
- Lightning Ready
- On the Salesforce Roadmap
Additional Setup Needed For:
- Online Volunteer Signups
- Email/Outreach
- Use Campaign/Members/ Mass Email Tool
- Use DLRS for rollup of volunteer hours
- Mass Volunteer Engagement/ Signups Shift Management
Benefits/ Considerations:
- Supported by Salesforce
- No innovation
- Limited number of volunteers (mass engagement may not want to use PMM)
- Volunteers doing programmatic work
- Connect Volunteer to a specific service delivery
- Lightning Ready
- Bulk Service is not Mobile Friendly, but single selection is mobile friendly.
Current Overlap/Where do Volunteers Fit into PMM without Customization or V4S:
- In PMM, there’s a contact lookup called “Service Provider” on Service Delivery Object
- In PMM on the Program Engagement there’s a role picklist that includes “volunteer”
How to configure/use:
- Contacts: Each volunteer should be a Contact
- Program Engagements: Create a Program Engagement for each volunteer
- Role = Volunteer
- Service Delivery: When a volunteer delivers a specific service, they should be listed as the Service Provider on the Service Delivery
PMM Supporter Module Use Case 1: Brain/Spine Org: P2P Support Group , Weekly Group, Moderators Meet / FB Sharing
-
Programs: Neuro Groups, Helpline, Information to Charities and Individuals
-
Services: Peer to Peer Support Groups
- Each group led by a volunteer
- Service Schedule:
- Monday Group led by Volunteer A (Primary Service Provider field)
- Service Session:
- Monday Group on Sept 21
- Monday Group on Sept 28
- Tuesday Group led by Volunteer B
-
Program Engagements:
- Volunteers Signed Up/ Leads
- Group participants
-
Program Cohorts:
- 2 Groups/ Regional/ National
-
Service Deliveries:
- Volunteer A and B will enter information: Participation/ What happened/ by Service Participant or another unit or measure or anonymous 10 people.
- Example: Participant X attended Monday Group on Sept 21 for 1 hour.
- Service Provider = Volunteer A
Existing Customers Migration:
- Archiving strategy
- Start from Scratch
- Migrate Historical Data
The goal of a hybrid model solution is to allow data to live in both products. This solution is aimed at cleanly syncing the data across the two products. Data entry can be minimized (e.g. don't need to enter everything into PMM and V4S). It will also help define how to leverage main features such as volunteer search.
Suggested Steps
- For the 1 to 1 volunteer to client scenario, link Volunteer Hour to Service Delivery
- Create lookup fields for Service Delivery on Volunteer Hours and Volunteer Hours on Service Delivery
- Create lookup field for Volunteer Jobs on Services
- Create Flow for Service Delivery to look for existing Volunteer Hours. If it does not exist, create new Volunteer Hours.
Questions/considerations: Would there be multiple volunteer jobs for each service?