When app users download your app and login to the app, they have a variety of methods for authenticating:
- If they know their MP Username + Password, this is a quick and easy way to authenticate.
- If they choose to authenticate using their Phone Number or Email Address, this is another quick and easy way to authenticate. Using this method, PocketPlatform will attempt to find the person in the database and match them up.
- If the user doesn’t know their username + password, or if no match can be made, then they can always create an account. When creating an account, PocketPlatform will again attempt to find the person in the database and match them up.
In all the scenarios above, our goal is to match the data provided by the user to the right person in MinistryPlatform. Based on Think Ministry best practices, we match on the First Name, Last Name and either the Mobile Phone Number or Email Address. In many cases, we find that duplicates are created when users are providing phone numbers or email addresses that are different from the data in MP because they’ve changed / updated their phone number or email address.
We recommend that you communicate to your church members which data is most likely to already be in your database when they download and install your app for the first time. For example, if you have a very accurate and current email list that you maintain via MP, then encouraging your church members to authenticate via email address could be very effective at avoiding duplicates. On the other hand, if you think many Contacts in the database share email addresses or have old email addresses, but you’re more confident that mobile phone numbers are up to date, then encouraging your church members to authenticate via phone number could be more effective.
Whatever choice you make, it’s important to remember that duplicates will always be created, and there will always be some cleanup that is required. The good news is that each month when Think Ministry publishes their Data Honor Roll for MP customers with the “cleanest” data, the list includes several PocketPlatform customers that have been working with their church members in similar ways.
TIP: You can customize the User Specific Navigation by editing the api_PocketPlatform_getRightNav Stored Procedure. Use your own custom logic to determine what links are shown to your users based on the data available about the user in MinistryPlatform. Reference the App Links KB Article for ideas on what screens can be loaded.
Information logged in MinistryPlatform via the Connection Card Tool can be used with MP Processes to automatically contact the individual the information is logged for, or to cue a staff person or volunteer to follow-up with the individual
Ideas for Using the Connection Card
Create a Dashboard Recipe that appears during your worship services times and encourage your members to connect with their church. An articulate call to action will stimulate users to click the button and follow the steps. If the Connection Card can be announced from the stage or included in on-screen announcements, users will be even more likely to engage.
Add the Connection Card link to your User Specific Navigation so that users have a convenient way to access the Connection Card from anywhere in the App.