SPoCs

It means Single Point of Contact. But it's also a Star Trek reference; how could we resist? SPoCs are the foundation of our approach to Support. Their job is to understand the issues their users are having, think them through, troubleshoot and problem-solve, and reproduce the issue where possible. And, if needed escalate by submitting a Support request.

Your SPoC team is made up of people that both your users and our Support staff know personally. They know the user, the church, the system, and our team. Your SPoC is uniquely positioned to ensure needs are communicated fully and addressed according to church priorities. We recommend having a team of three SPoCs. And while there are no "hard and fast" definitions for each SPoC role, here are some best practices:

• User SPoC: A high-level User who is the guardian of the data in your MinistryPlatform system. Their duties may include managing what data is being used, how is it being entered, how it is kept clean, etc. The User SPoC is often expected to know how to set up Events, Groups, Opportunities, Check In, etc. The User SPoC is oftentimes also responsible for training your new or existing staff/volunteer Users on how to use MP.
• Money SPoC: A high-level User who is the master of the Stewardship and Product and Payment sections of MinistryPlatform. Their duties may include setting up Programs, Products, and Pledge Campaigns as well as the processing and reconciling of Donations and Payments.
• IT SPoC: A high-level User who is the keeper of the server and IT infrastructure that runs MinistryPlatform. IT SPoCs have access to servers/networks/etc. and their duties may include managing Users and Security Roles as well as domains, remote connections, and SSL certificates. The IT SPoC might also be involved with Portal skinning or advanced custom views.

Have a new SPoC? Contact Support with the details. If adding a SPoC, include full name, email address, and title.

Support

If needed, a SPoC can submit an issue to Support via live chat, phone call, or the case portal. Our crackerjack Support Agents are standing by!

Knowledge Base

The Knowledge Base provides an extensive, rapidly evolving, online documentation database with search-friendly articles and videos about every facet of all MinistryPlatform applications available to anyone on your team 24/7. It is written to help you use MP to its fullest no matter how you "do church."

Have Knowledge Base feedback? We'd love to hear from you! At the bottom of every KB article, you'll see a BLUE megaphone button. Give it a click to amplify your voice and let us know about your KB experience.

Procedures

The Procedures page in MinistryPlatform is a great place to document how your church uses MinistryPlatform. For example, the KB explains how to create an Event, but your Procedures explains how at My Church we decide what Visibility Level or Program to use. It's a great place for all those "church-y decisions." Users can use the “About This Page” report on any page to print a Procedures Manual of Procedures specific to that page.

MP User Community Forum

The MP User Community Forum is available for current live customers. It is a source of inspiration and ideas as churches share their own knowledge and experiences. Why reinvent the wheel? Sometimes the best ideas come from a user doing the same job at another church! Reach out to Support to activate an account on the Support Portal to learn how other churches make ministry happen with MinistryPlatform.

Webinars

From time to time, we host webinars on a variety of topics that bring value to the MinistryPlatform community. Webinars are always fun and are geared toward helping you get ministry done! 

Updates

Each MinistryPlatform application is updated separately. For each update, users set to receive notifications will receive an email detailing when the update will be deployed, update highlights, and a link to the Release Notes. Release Notes detail the fixes, enhancements, and new features included in the update and are available anytime on the application's section in the KB.