Learn Editor: Update sms-calling-errors.md

Author: revaldiv

Teams/phone-system/sms-calling-errors.md

@@ -22,7 +22,9 @@ The following sections provide a comprehensive list of potential rejection error
 
 | Error | Description | Recommended action |
 |-------|-------------|--------------------|
-| CallToActionContainsDisallowedContent | The Call to Action contains disallowed content. | Remove any prohibited content from the Call to Action. |
+|CallToActionConsentNotOptional |  The opt-in form is used for purposes beyond SMS messaging, but SMS consent is not optional. | If your opt-in form serves multiple purposes (e.g., account creation, newsletter signup), ensure SMS consent is optional. You can do this by either making the phone number field optional or including a clearly labeled checkbox for users to agree to receive SMS messages. Forced consent is not permitted. |
+|CallToActionContainsDisallowedContent | The Call to Action contains disallowed content. | Remove any prohibited content from the Call to Action. |
+|CallToActionCourtOrderedOptIn | Opt-in information implies consent is acquired through a court order, which is disallowed. | Remove any language suggesting opt-in is obtained via legal mandate or court order. Consent must be voluntary and user-initiated.|
 | CallToActionDoesNotContainRobustAgeGate | The Call to Action doesn't contain a robust age gate for age-restricted content. | Add a clear age verification step for age-restricted campaigns. |
 | CallToActionIsMissingOrInaccessible | The Call to Action is missing or inaccessible. | Make sure that the Call to Action is present and accessible to users. |
 | CallToActionMissingBrandName | The Call to Action doesn't contain the registered (DBA) brand name. | Add the brand name in the Call to Action. |
@@ -31,12 +33,13 @@ The following sections provide a comprehensive list of potential rejection error
 | CallToActionMissingExpressWrittenConsent | The Call to Action doesn't obtain express written consent for promotional message content. | Add a checkbox or statement for express written consent. |
 | CallToActionMissingHelpInstructions | The Call to Action doesn't include HELP instructions. | Add HELP instructions for user support. |
 | CallToActionMissingMessageFrequencyDisclosure | The Call to Action doesn't include the frequency at which messages are sent. | Add a statement about message frequency. |
+|CallToActionMissingOptInForm | The webpage used for opt-in does not contain an opt-in form. | Ensure the opt-in webpage includes a visible and functional opt-in form. Avoid linking to generic or unrelated pages.|
 | CallToActionMissingPrivacyPolicyLink | The Call to Action or the opt-in form doesn't include a link to the privacy policy. | Add a link to the privacy policy or a statement about data sharing. |
 | CallToActionMissingStopInstructions | The Call to Action doesn't contain STOP instructions. | Add STOP instructions to enable users to opt out. |
 | CallToActionMissingTermsAndConditions | The Call to Action doesn't contain full terms and conditions or a link to them. | Add the full terms or a link to them. |
 | CallToActionMissingVerbalScript | The Call to Action doesn't include a verbal script or required disclosures. | Add a verbal script that has the required disclosures. |
-| CallToActionOptInIssues | The opt-in URL is inaccessible or returns a certificate error. | Make sure that the opt-in URL is valid and secure. |
 | CallToActionMissingMessageType | The Call to Action doesn't mention the kinds of messages that a customer can expect. | Specify the kinds of messages that users might receive. |
+| CallToActionOptInIssues | The opt-in URL is inaccessible or returns a certificate error. | Make sure that the opt-in URL is valid and secure. |
 | CallToActionInvalidOrIncomplete | The Call to Action is noncompliant or incomplete. | Make sure that all required elements are present: brand name, HELP, STOP, frequency, fees, privacy policy. |
 
 ## Terms and conditions