News and analysis
Before sending SMS: check the number and campaign readiness
Twilio demonstrates line-type checks; HighLevel improves A2P rejection guidance. These address different workflow prerequisites.
A CRM contains a phone number, and an automation should send a message after a request. A stored contact does not establish that SMS is the right channel or that the campaign is ready. Two October developments help distinguish those prerequisites before enabling the workflow.
Number type concerns one contact
On 7 October, Twilio published a Lookup v2 example in Go, using Line Type Intelligence to identify landlines before SMS sending. This checks the type of number. It does not establish recipient consent, lead quality or guaranteed delivery.
The result needs a clear operational meaning. If the number is unsuitable for SMS, the employee needs an agreed next action rather than a disappearing task. The system might leave the request for a person to choose another channel. That is a design choice, depending on your contact records, communication rules and team capabilities.
Define what happens when the result is unknown or the lookup service fails. An automatic “allowed to send” assumption should not silently replace missing information. A lookup is also not evidence that a person wanted the message.
Campaign readiness is a different layer
On 8 October, HighLevel updated A2P rejection explanations in View Required Fixes. Guidance differs between Chat Widget Quick Setup and Manual Setup, identifying changes an owner can make and cases where resubmission will not help.
The connection is two independent boundaries: suitability of an individual number and campaign status. Correcting registration does not make every contact suitable for SMS. Checking the number does not replace campaign requirements. The vendor’s guidance does not guarantee subsequent carrier approval either.
Accept the workflow with a sample list
Prepare an approved test set with different result types. Follow the status assigned to each contact and identify who handles exceptions. Do not send real messages merely to demonstrate sorting.
Check campaign state and actions following rejection separately. The team should see what it can correct now and when the person responsible for the connection must intervene. Preserve the origin of a check and its related request, so replaying the workflow does not create an unnoticed new attempt.
The comparison suggests modelling communication readiness as several states. Number type, permission to contact and connection status should remain distinguishable. An owner can then understand why a message has not been sent and what action is required.
Our reliable CRM workflows guide helps organize exceptions. The archived CRM and chatbot project provides communication context without claiming adoption of these updates. For your CRM integration, discuss the checks needed before sending.