Messaging Policy

Modified on Wed, 3 Jan at 9:48 AM

This communication policy is applicable to all accounts utilizing LC - Phone for messaging within the CRM system.


We anticipate that our desired messages will be delivered without being hindered by filters or blockers. To fulfill this expectation, it's crucial for both LC - Phone and our users to work towards preventing and eradicating unsolicited messages.


Our commitment is to guarantee that all messages sent via LC-Phone are directed to individuals who have given their consent and adhere to relevant laws, industry norms, and guidelines. Additionally, we aim to uphold standards of fairness and propriety, especially in situations that may be ambiguous.


LC - Phone Messaging Policy

All messaging transmitted via the platform - regardless of the use case or phone number type (e.g., long code or toll-free) - must comply with the Application-to-Person (A2P) messaging. All A2P messages originating from the system are subject to this Messaging Policy, which covers messaging rules and /or prohibitions regarding:

  • Consent (“opt-in”): Consent can't be bought, sold, or exchanged. For example, you can't obtain the consent of message recipients by purchasing a phone list from another party. And SMS should only be sent to the opted-in contacts.

  • Revocation of Consent (“opt-out”): The initial message that you send to an individual needs to include the following language: “Reply STOP to unsubscribe,” or the equivalent so that Individuals have the ability to revoke consent at any time by replying with a standard opt-out keyword.

  • Sender Identification: Every initial message you send must clearly identify you (the party that obtained the opt-in from the recipient) as the sender, except in follow-up messages of an ongoing conversation.

  • Messaging Usage: You should not be sending messages in any way related to alcohol, firearms, gambling, tobacco, or other adult content.

  • Filtering Evasion: As noted above, we do not allow content that has been specifically designed to evade detection by unwanted messaging detection and prevention mechanisms. This includes intentionally misspelled words or non-standard opt-out phrases which have been specifically created with the intent to evade these mechanisms. We do not permit snowshoeing, which is defined as spreading similar or identical messages across many phone numbers with the intent or effect of evading unwanted messaging detection and prevention mechanisms.


This policy applies to all customers who use LC - Phone messaging services to safeguard their messaging capabilities and services.




How We Handle Violations?

When we identify a violation of these principles, we will work with customers in good faith to get them back into compliance with the messaging policy. However, to protect the continued ability of all our customers to use messaging for legitimate purposes freely, we reserve the right to suspend or remove access to the platform for customers or customers’ end users that we determine are not complying with the Messaging Policy, or who are not following the law in any applicable area or applicable communications industry guidelines or standards, in some instances with limited notice in the case of serious violations of this policy.




1. Ramp-Up Model:

  • Every new sub-account (from April 20, 2022) that are on LC - Phone System going forward will follow the "Ramp Up Model."
  • The SMS limit is multiplied each day by the number of days (till the 7th day) the account has spent with us. Starting the 8th day, the account will be limited to 5000 SMS/day. Below is the table which will give you a detailed idea:

Why the change?


LC - Phone policy was implemented to:

  1. Avoid SMS Spam blasts from fake signups. New sub-accounts on LC - Phone will follow the Ramp-Up Model
  2. Avoid getting sub-accounts blocked due to suspicious activity
  3. Avoid legal actions due to increased spamming to non-consenting customers. Only bulk SMS sending will have daily limitations to avoid sub-account suspension due to non-compliant messaging activity.



What error screens or notifications will a sub-account see during a violation?

  1. Conversation Error: You have exceeded your SMS sending limit.
  2. Bulk Action: You can send 5000 message(s) in a day. You have already sent 5000 messages (s). If you wish to proceed, 1 Message(s) will be failed.

  3. How to update the limit for a sub-account?

    If you would like to increase the limit to more than 10K/day, Reach out to your Agency Admin with the Email Subject <Increase SMS Daily Limit> with your account, new limit details, and your use case for the new limit.




    2. Spam Message Handling:

    Each of the messages sent out from the sub-account ends up with the following 4 statuses:

    1. Sent: The messages whose response we did not receive from the carrier can be in any of the three statuses below.
    2. Delivered: The messages which were successfully delivered and sent to the contact.
    3. Failed: The messages that were canceled or not sent to the carrier to forward to the contact.
    4. Undelivered: The message sent was suspicious or did not fulfill the messaging policy.


    As part of this feature, we will only consider Undelivered messages. All the undelivered messages end up with a particular error code, and we will start storing them at each message level. We will further use them to enable Temporary/Permanent DND at a contact level so that new SMSs are not sent to them, increasing your deliverability rate. 


    The below table summarizes the undelivered SMS error codes and what each of them means, and the relevant remediation measure we are taking:


    Response Code
    Code Description
    Remediation
    30005

    User Inactive/Number does not exist

    Enable Temporary DND
    30003

    Unreachable- Out of Service

    Enable Temporary DND
    30004

    Do not want SMS/DND enabled

    Enable Permanent DND
    30006

    Landline/Incapable to receive SMS

    Enable Temporary DND
    30008
    None of the above scenarios matched
    Do nothing


    Temporary DND: The agency or account can revoke the DND set at a contact level.

    Permanent DND: The DND set at the contact level cannot be revoked by the agency or the account as the contact cannot receive the message or has opted out from receiving messages.

    Opt-Out Keyword: Individuals must be able to revoke consent at any time by replying with a standard opt-out keyword like STOP, Unsubscribe, etc. In this case, a permanent DND will also be enabled at the contact level.

Advantage:

  • This will restrict the account from sending SMS to non-relevant contacts, eventually increasing the deliverability rate and decreasing the possibility of getting blocked.
  • The accounts will only send messages to the contacts who have opted in. 

Spam messaging error screens:

  1. Conversation: Cannot send messages as DND is active for SMS.


  2. Bulk Action: All SMS sent via features like workflow and bulk SMS will automatically skip the DND-marked contacts from the sender list.




How to revoke the DND for a contact?

  1. For Temporary DND, go to the contact details and remove the DND flag; below is the screenshot of the sample screen:


  2. For Permanent DND, you cannot revoke the same from UI. To revoke the permanent DND, request the contact to send a reply with the "START," "YES," and "UNSTOP" keywords to the number. This should automatically remove the DND from the contract.


        3. Inclusion of Opt-Out Language


It's imperative to understand that consent for sending communications cannot be purchased; it must be explicitly obtained from the user for SMS campaigns and communications. This consent is acquired by a specific entity, which in our case, are the sub-accounts that act as the actual senders of these communications.


To adhere to messaging policies, each initial message dispatched by the company to an end-user must contain two essential pieces of information: the Sender ID and the opt-out language. Regarding the opt-out language, it's crucial that the end user has the ability to withdraw their consent at any time. Therefore, just like the sender ID, each initial message should include opt-out keywords such as STOP, UNSUBSCRIBE, etc. Additionally, we will incorporate the following opt-out language: “Reply STOP to unsubscribe."


3. Opt-Out Language addition


  • The consent for sending out communications cannot be bought, and the only way is to take explicit consent from the user for the SMS campaigns and communications.
  • The consent is taken by a specific entity, in our case, sub-accounts that are the actual sender of these communications.
  • To comply with the messaging policies, each of the initial messages sent out by the company to an end-user should have below two mandatory information, i.e., Sender ID and opt-out Language:
  • Opt-Out Language: The end user should be able to remove the consent at any time, so like above, each initial message should also have opt-out keywords like STOP, UNSUBSCRIBE, etc. We will additionally add the opt-out language: “Reply STOP to unsubscribe."

4. Addition of Sender Information


It is essential to recognize that consent for communication cannot be acquired through purchase; rather, it must be explicitly granted by the user for SMS campaigns and communications. This consent is obtained by a specific entity, which in our scenario, are the accounts that serve as the actual sender of these communications.


In alignment with messaging policies, each initial message sent by the company to an end-user must include two critical pieces of information: the Sender ID and the opt-out language. As for the Sender ID, every message dispatched must clearly identify you (the entity that received the opt-in from the recipient) as the sender. This is mandatory for all messages, except in the case of follow-up messages in an ongoing conversation. We will also incorporate sender information in the format: “Thanks, <account Name>."



Sample message screen:

How can I customize the opt-out message?

Go to Sub-account -> Settings -> Business Info -> General, where you can customize the opt-out message; below is the screenshot for reference:

5. Error and Opt-out Rate Monitoring

  • We are focused on helping our customers deliver trusted communications. Ensure the carrier does not permanently block or suspend the account based on bad usage.

  • We will be monitoring the delivery rate of the overall account and be taking proactive measures(as mentioned below) to keep the delivery rate in check:
    • Violation Email - We will send out an email notification as soon as the subaccount hits the error rate of 8% and opt-out rate of 1%.
    • Temporary Account Restriction - We will send out a suspension email as the subaccount hits the error rate of 12.5% and opt-out rate of 2.5%.

What should we do when we get a violation email?

  1. Stop all your workflows, campaigns, triggers, and/or bulk actions to contacts who have not explicitly opted in to receive messages from the sub-account.

  2. Enable and customize the Opt Out language and SenderID message as per your use case so that all the upcoming messages are not flagged.

  3. Please discuss this with your client to make no bulk communication or messages blast or cold prospecting message campaigns are sent in the near future before we receive your reply to this ticket.

What are error and opt-out rates, and is it good to have a threshold?

  • High Opt-Out Rate indicates that contacts receiving your messages have objected, generated complaints, or marked your SMS as spam. A good opt-out rate is typically in the range of 0—1%. Once the opt-out rate hits 2%, the sub-account will be locked for sending text messages for 24 hours.
  • High Delivery Error Rate indicates that you send SMS to contacts that are no longer in service, are unreachable, or use a non-SMS-capable device such as a landline. This may also mean that external carrier filters are refusing to deliver your SMS due to bad sending behavior in the past. A good error rate is typically in the range of 0—6%. Once the error rate hits 12%, the sub-account will be locked for sending text messages for 24 hours.


What do I do to get the subaccount suspension removed early?

Your LeadConnector Phone System account can get suspended due to policy violations involving sender identification, opt-out language, and large-scale similar messaging. Furthermore, the account's opt-out and error rates may have exceeded acceptable levels.


Here's how you can address these issues:


Sender Identification: Ensure each message identifies you, the sender, particularly in the first message of each conversation. The recipient needs to recognize to whom they've consented.


Opt-Out Language: Include an option in your initial message, for example, "Reply STOP to unsubscribe." For this purpose, use standard keywords such as STOPALL, UNSUBSCRIBE, CANCEL, END, or QUIT.


Similar Messaging: Avoid sending identical or similar messages to many phone numbers unless you have a proper business justification. This can be perceived as spamming and can lead to further restrictions.


If you wish to appeal this decision, please explain your business use case that necessitates such messaging practices.


Regarding opt-out and error rates, maintain rates in the following ranges for optimal results:


Opt-out rate: 0—0.3%

Error rate: 0—6%

  • The first step to rectify your opt-out rate is to ensure that your message always includes the sender's identity. Make it a point to inform the recipient how they opted into your communication, such as through form submission. The initial message should also include clear instructions to opt out.
  • Also, when dispatching similar messages across various phone numbers, be cautious. Any perceived spamming activity can result in carriers blocking messages. If there's a legitimate business case for this, communicate it to the support team
  • To manage error rates, validate phone numbers before sending SMS. Turning on phone number lookup in your agency view settings can help reduce errors. Also, ensure your messages don't contain keywords that might flag them as spam.
  • Finally, we recommend adding leads into campaigns in small groups for efficient communication and better error management.
  • Establishing a double opt-in process can further help improve your messaging practices. You can achieve this by directing your leads to a form where they can agree to receive SMS, followed by asking them to reply with a specific keyword to confirm their subscription. Always remind them of the option to opt out by including "Reply STOP to unsubscribe" at the end of every message.

  • Once you've implemented these changes, share a walkthrough video of your new setup with us. We can then communicate with the phone system provider to lift the account suspension.
    However, the subaccount suspension will be lifted in 24 hours if the sub-account is permanently suspended. 


FAQs


How often does the SMS limit last?

The SMS limit will refresh every 24 hours. If the account is brand new, then each day, the increments will increase according to the table above. Once you have hit the 8th day, your SMS limit will be capped at 5000 daily.



I want to send more than 5000 SMS daily; how can I increase my limit?

Once your account(s) hit the 8th-day mark (5000 SMS per day), you may reach out to your Agency Admin with the Email Subject <Increase SMS Daily Limit> with your account, new limit details, and your use case for the new limit.



What happens when we hit our daily limit? Will we be able to respond to SMS if a lead replies?

No, you cannot respond manually to incoming messages. SMS daily limits will affect all messaging activities, including manual SMS in conversation, automation within workflows, and bulk actions.



Can we undo the DND option in bulk?

No, we cannot because this prevents sending SMS in bulk again after DND is enabled for the contacts. 



Is the auto append Sender ID and Opt-Out Language feature also applying to every first text of workflow or manual SMS?

This feature only applies to Bulk action (Bulk SMS) and does not apply to One on One conversations, Workflow, or Campaigns.





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article