Sending Your First Message with Linxi
Once your number, webhooks, and contacts are all in place, sending is the easy part. Here's the three ways to do it and how to read what happens after you hit send.
Three ways to send
- Individual — open a contact's thread from the Linxis tab and send a one-off message
- Reply — respond directly to an inbound message in the same thread
- Campaign — send the same message (with personalization) to many contacts at once
Sending an individual message
Open Linxis, pick (or search for) a contact, and type in the thread the same way you would in any messaging app. This works the moment your number and webhooks are configured — it doesn't require A2P approval to send to a single number you've already been messaging with, though delivery to some carriers may still be filtered until your Campaign is approved.
Creating your first campaign
- Go to Compose & Send
- Choose a channel — SMS, Email, or Both
- Select recipients — everyone, a specific group, a list, or a tag
- Write your message
- Preview it, then send
Understanding delivery status
A message moves through Queued → Sent → Delivered. "Queued" means Twilio has accepted it but hasn't reported carrier confirmation yet; "Sent" means it left Twilio; "Delivered" is the carrier's own confirmation, which arrives via the status webhook (see Webhook Configuration) sometimes several seconds to a couple minutes later. Undelivered means the carrier rejected it — check the Flow tab for the specific error code Twilio recorded.
Why Verizon specifically might not deliver yet
Verizon enforces A2P 10DLC filtering more strictly and consistently than most other US carriers. AT&T and T-Mobile are generally more lenient while your Campaign is still under review, but Verizon in particular tends to block traffic outright from an unapproved or pending campaign. See Troubleshooting for error 30034, the specific carrier-block code this usually shows up as.
