PlayerFirst gives you control over whether SMS is used for your brand at all, whether it can be used for MFA login codes, and automatically checks outgoing mass SMS messages for marketing language before they're allowed to send.

NOTE: Turning this off removes SMS entirely as an option — both from the mass messaging tool's message-type choices and from the quick individual message option on a contact. It's not just disabled after the fact; the option won't appear at all.

Whether the Phone on Account option appears when someone verifies their identity or logs in with a one-time code depends on two global settings — not something individual brands turn on or off themselves.

NOTE: These are RootAdmin-only global settings (Global Settings → Features tab): Enable Transactional SMS and Enable MFA SMS. Both must be turned on for the phone/SMS option to appear during login or verification — if either is off, that option simply doesn't show up, rather than failing after someone selects it.

NOTE: If the underlying API is called directly while MFA SMS is off, it responds with a 400 Bad Request and the message "MFA codes by text are currently unavailable." Customers going through the normal login flow won't encounter this, since the option is hidden from the UI rather than left there to fail.

When sending a mass text message — through the mass messaging tool, Team messaging, or product messaging — PlayerFirst checks the message for marketing or promotional language before allowing it to send.

NOTE: This check only applies to mass messaging tools — it doesn't apply to the quick individual message option on a single contact.

NOTE: Phrases like "check your email" are allowed and won't trigger this block — a good way to remind coaches or families to check their inbox for details.