Service for Account Verification Texts
Only planning to send authentication texts from the Platform? Try our free texting service for account verification!
This service handles all multi-factor authentication (MFA) texts for you. That means, no third-party setup is required. You just enable the service and start using it.
Which texts are sent through this service?
- Multi-factor Authentication – When someone logs in to MinistryPlatform or PocketPlatform, they receive a text with a numeric code to authenticate their login (if you've enabled multi-factor authentication).
- One-time Code – When someone clicks Get One-time Code on the Log In screen, they receive a text with a numeric code so they can log in.
- Account Recovery – When someone clicks Forgot your password? on the Log In screen, they receive a text with a numeric code to reset their password.
- Account Creation – When someone clicks Create an account on the Log In screen, they receive a text with a numeric code to verify their account.
Are there any requirements or charges for this service?
To use the service, you must be based in the United States. You will not be charged for the SMS number or the texting volume of account verification texts.
What if I already have a Twilio account?
If you already have texting set up, you can still use our service for authentication texts. All other texts will be sent from your outbound SMS number. Or, you can continue using your number to send all texts from MinistryPlatform. You may do this if you prefer to have all texts sent from your Twilio phone number. In this case, you don't need to do anything. The Global MFA Secure Key record has Enabled set to No by default.
Can I customize the phone number or wording that account verification texts show?
No. The phone number displays as our company's managed number, which is 1-888-292-4051. You cannot port over your phone number to use for this service. The text message wording must comply with Twilio requirements. All account verification texts use clear, direct language and include your church/organization name. For example:
Enable Texting Service for Account Verification
- You must be based in the United States to use this service.
Once the service is enabled, it's ready to use! The next time your system sends a text related to account verification (that is, the Communication Type is GlobalMFA), it will be sent using our service. Our service has a high throughput, so these important texts are delivered quickly.
Any text messages unrelated to account verification will still be sent using your Twilio account, if applicable.
People who receive texts can opt out at any time.
Employee view only: Errors and Troubleshooting
If the Global MFA configuration is invalid, the text may attempt to send through Global MFA but will fail.
| Error (ActionText) | Reason for Error |
|---|---|
| Forbidden; Global MFA Error: Invalid Key for host core.cloudapps.ministryplatform.cloud | The API key is null or invalid but the Base URL is populated. |
| Could not establish trust relationship for the SSL/TLS secure channel. The remote certificate is invalid according to the validation procedure. | The Base URL is invalid. |
| Message cannot be sent: Value cannot be null. Parameter name: uriString | The Base URL is null, with or without a valid API Key. |
| Internal Server Error | The SaaS/API is down temporarily. Only affects this service, so any other texts sent through the customer's Twilio account will still go through. |
If the Domain Connection record has Enabled set to No, the Platform will send the message through the customer's integrated Twilio account. This fallback behavior occurs regardless of whether the API Key and Base URL are populated or valid.
If the Domain Connection record does not exist or if the existing record is not set with the Connection Type "Global MFA Secure Key" (even with Enable set to Yes), the Platform defaults to sending the message via the customer's Twilio account if it's configured on the Domain record.