Skip to main content
Velor

Docs / SMS and WhatsApp

SMS and WhatsApp setup.

Velor sends and receives through your own Twilio account. Pointing the webhook is the easy half; the half that decides whether customers receive replies is registration with the carriers. Everything below restates Twilio’s own documentation, and says so where we have not been able to confirm a detail. Per-channel status is on Settings, Channels.

US texts: register before you launch

Twilio requires anyone sending application-to-person SMS or MMS over a 10-digit US number to register for A2P 10DLC: a Brand and a Campaign, with the number attached through a Messaging Service. Toll-free numbers and short codes are outside that system. Twilio: A2P 10DLC

Toll-free numbers sending to US and Canadian mobile numbers need toll-free verification. Twilio states it reviews requests within three business days, and that unverified numbers in Restricted or Pending status have been blocked since 31 January 2024. Twilio: toll-free verification

Twilio’s documentation does not state a review time for 10DLC brands or campaigns. Plan for it to take time, and do not promise a customer a launch date before the status reads approved.

What it looks like when this is missing. Twilio accepts the message, the carrier then refuses it, and the message shows as undelivered with error 30034 (long code not registered) or 30032 (toll-free not verified). In Velor that appears on the message in the inbox as Not delivered with the cause, and in the delivery-failures list.

Checking status. On Settings, SMS, Check registration status reads your Twilio account’s campaign and toll-free verification status with the credentials stored for your numbers and reports registered, pending, rejected, not found, or could not check. Twilio’s documentation describes API-key authentication for those endpoints, and we have not confirmed that an Account SID and Auth Token are accepted. When Twilio refuses them the answer is could not check, never registered and never not found. A registered result means an approved registration exists on the account; it does not prove a particular number is attached to it.

Reading a Twilio delivery error

These are the causes Twilio documents for each code (Twilio error index):

  • 30034 — the number is not tied to an approved A2P 10DLC campaign (incomplete registration, number not in the Messaging Service sender pool, or several numbers on a Sole Proprietor campaign, which supports one).
  • 30032 — toll-free number not verified.
  • 30007 — message filtered by Twilio or a carrier (for example as spam).
  • 21610 — the customer opted out (for example by replying STOP); nothing can be sent until they reply START.
  • 30004 — message blocked; Twilio lists a recipient-side block, an unavailable handset, a landline, or carrier or Twilio filtering.
  • 30003 / 30005 / 30006 — handset unreachable, number unknown or inactive, landline or unreachable carrier.
  • 21408 — the destination region is disabled in Messaging Geo Permissions.
  • 21608 — the account can only message verified numbers (trial, or no approved primary compliance profile).

A code not listed here is shown with its number and a link to Twilio’s page rather than an explanation we cannot back.

WhatsApp: the 24-hour reply window

A customer’s message opens a 24-hour window in which you can reply with ordinary text. Outside it, Twilio says you may only send an approved template; a free-form message returns error 63016. Twilio: WhatsApp key concepts

Velor checks the window before a teammate’s reply goes out and does not attempt a free-form message outside it. The reply stays in the conversation marked not delivered with the reason, and is listed under Delivery failures. If the window cannot be read, the reply is refused rather than sent.

Error 63007 (no channel found for the From address) lists these causes: a From not in whatsapp:+E164 form, a sender that is not ONLINE, a sandbox not activated on the same account, or credentials for a different account or subaccount. Error 63015 means the sandbox can only message numbers that joined it, and participants rejoin after 3 days.

Delivery receipts and failures

Twilio accepting a message is recorded as sent. Only Twilio’s own status callback moves it to delivered. A message with no receipt after an hour reads delivery unconfirmed, and a message with no delivery record reads delivery unknown. Temporary provider errors are retried automatically, up to three sends per message; everything else waits under Conversations, Delivery failures, where a resend is refused for a customer who opted out.