Answers.Body: <p>This is likely related to the A2P 10DLC requirement effective September 1, 2023. You can check the error log to confirm it is  <a href="https://www.twilio.com/docs/api/errors/30034" rel="nofollow noreferrer">30034 error</a> in Twilio at Monitor &gt; Logs &gt; Error Logs. If the texts are being delivered from CiviCRM to Twilio than it is a Twilio issue.</p>
  <p>You can follow the <a href="https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC-" rel="nofollow noreferrer">instructions here to registration your brand</a>. This is to combat SMS spam. Essentially, SMS reputation rules are finally catching up with email.</p>
  <p>FWIW, Twilio has made this <em>a lot easier</em> now that it effects all organizations as it can be done all in the UI and is well-documented than a couple years ago when it was a requirement for <a href="https://support.twilio.com/hc/en-us/articles/4402972441243-Special-Use-Cases-for-A2P-10DLC" rel="nofollow noreferrer">political orgs and  special use cases</a> and could only be done in CLI.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-01T15:58:05.933Z
Answers.LastActivityDate: 2023-10-01T15:58:05.933Z
Answers.UserDisplayName: Andy Burns
Body: <p>We are using CIVICRM 5.463.</p>
  <p>We have Twilio SMS set up and it did work great for a period of time but now has stopped working for individual and group texts.</p>
  <p>The send outbound SMS cron job is completing successfully.</p>
  <p>When you send the message, CIVICRM displays the message that the text was sent successfully.</p>
  <p>Yet no texts are being received by anyone. The process ceased to work about 2 weeks ago.  No technology changes coincides with this timeframe.</p>
  <p>Any ideas where I should look to figure out the issue?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-09-26T04:23:15.210Z
Comments.Text: What do twilio records show? Is it at least reaching twilio?
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-10-01T08:58:56.903Z
Comments.Text: I have the same issue. The logs at Twilio do not show anything
Comments.UserDisplayName: Steve Schiltz
Tags: <sms><twilio>
Title: SMS Text Messaging Stopped Altogether
ThreadText: # SMS Text Messaging Stopped Altogether
  
  (Asked by: username_0 on 2023-09-26)
  
  We are using CIVICRM 5.463.
  
  We have Twilio SMS set up and it did work great for a period of time but now has stopped working for individual and group texts.
  
  The send outbound SMS cron job is completing successfully.
  
  When you send the message, CIVICRM displays the message that the text was sent successfully.
  
  Yet no texts are being received by anyone. The process ceased to work about 2 weeks ago. No technology changes coincides with this timeframe.
  
  Any ideas where I should look to figure out the issue?
  
  **Tags:** sms, twilio
  
  > **Comments:**
  > **username_1**: What do twilio records show? Is it at least reaching twilio?  
  > **username_2**: I have the same issue. The logs at Twilio do not show anything  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2023-10-01. Score: 2
  
  This is likely related to the A2P 10DLC requirement effective September 1, 2023. You can check the error log to confirm it is [30034 error](https://www.twilio.com/docs/api/errors/30034) in Twilio at Monitor > Logs > Error Logs. If the texts are being delivered from CiviCRM to Twilio than it is a Twilio issue.
  
  You can follow the [instructions here to registration your brand](https://support.twilio.com/hc/en-us/articles/1260800720410-What-is-A2P-10DLC-). This is to combat SMS spam. Essentially, SMS reputation rules are finally catching up with email.
  
  FWIW, Twilio has made this *a lot easier* now that it effects all organizations as it can be done all in the UI and is well-documented than a couple years ago when it was a requirement for [political orgs and special use cases](https://support.twilio.com/hc/en-us/articles/4402972441243-Special-Use-Cases-for-A2P-10DLC) and could only be done in CLI.
  
  
  ---
  
  