Which Phone Numbers Can Receive Claim Raven SMS?
Claim Raven's current setup accepts a U.S. phone number in +1 format and requires the SMS provider to be configured, but that does not guarantee delivery to every U.S. carrier, plan, device, or destination. Carrier filtering, sender registration, roaming, blocked senders, consent state, device availability, and the specific event producer can all affect whether a text is attempted or received. Do not use a carrier name alone as proof that Claim Raven SMS will work.
Overview
Compatible does not mean guaranteed A number can pass Claim Raven's format check while a provider, sender, carrier, plan, consent rule, device, or network still blocks delivery. A compatible destination also does not create an alert when the specific Claim Raven event producer is unavailable.
What the current product actually checks
Claim Raven currently expects a U.S. number and stores it in +1 format after validation. The number must complete the current verification flow before SMS can be enabled for normal use. The SMS provider connection must be available for verification, testing, or a delivery attempt. The relevant SMS preference must be enabled, and a particular action can also have its own access or usage limit. The specific event must have an active producer. The checked product does not have a general claim-status SMS producer. Appeal, docket, and hearing preferences are forced off while live appeal sync is unavailable.
Why a carrier list is not enough
Carrier and sender filtering can change by message content, registration, traffic pattern, destination, and network conditions. The destination phone can be unavailable, roaming, out of service, full, blocking the sender, or filtering the message as spam. An accepted or sent provider status does not always mean the carrier delivered the text to the device. Consent can be sender-specific. A STOP-family reply can block future messages from that sender or Messaging Service until an applicable re-opt-in step succeeds. Short-code, toll-free, and long-code senders can have different behavior. Do not assume one keyword or carrier rule applies to every sender. Message and data rates, carrier plan limits, and device settings belong to the phone account, not to Claim Raven's feature contract.
Check a number without exposing it
Use a number you control Do not use a shared office, public, temporary, or supporter-controlled number for claim-related alerts unless you accept the privacy risk and have permission. Follow the current Settings flow Enter the U.S. number in the requested format, complete verification, and review any provider or availability message on the page. Never send the verification code to support. Use a test only as a channel check If the product offers a test for the current account, it checks one provider request at that time. It does not prove general claim alerts are active or guarantee future delivery. Review the device and carrier path Check signal, blocked contacts, spam filtering, storage, focus modes, and carrier restrictions. Use the original sender's instructions if consent may have been withdrawn. Keep an independent monitoring plan Check VA.gov and every VA notice directly. Do not rely on a carrier, test message, or quiet phone to protect a deadline.
If the number still does not work
If the number still does not work Claim Raven rejects the number. Confirm that it is a U.S. number you control. Enter only the digits requested by the current page. Do not use an international, extension-only, or obviously temporary number. Use a supported U.S. destination or another independently available channel; do not alter account facts to bypass validation. Verification succeeds, but later texts do not arrive. Confirm the specific event has an active producer. Review SMS enablement, provider availability, consent, blocked senders, and carrier filtering. Check VA.gov and the newest notice instead of waiting. Treat SMS as unavailable for consequential monitoring until the event and channel are separately confirmed. A different number or carrier receives the test. Compare sender type, destination, device settings, consent, and plan behavior. Do not infer that all numbers on that carrier work. Do not publish or send the phone numbers in a support request. Carrier names are not a delivery matrix. Troubleshoot only the affected destination with non-sensitive details. For a Claim Raven settings problem, share the page name, approximate time, channel, and non-sensitive error text. Do not include the phone number, message body, password, code, VA identifier, notice, medical record, or unredacted screenshot.
Current provider sources
Current provider sources Twilio: Debugging common SMS issues https://www.twilio.com/docs/messaging/guides/debugging-common-issues Twilio: Messaging Services https://www.twilio.com/docs/messaging/services Twilio: Advanced opt-out and opt-in behavior https://www.twilio.com/docs/messaging/tutorials/advanced-opt-out
Related alert and privacy guidance
Related alert and privacy guidance Troubleshoot a missing Claim Raven SMS /help-center/notifications-and-alerts/faq-not-getting-sms Understand which Claim Raven alerts are conditional /help-center/notifications-and-alerts/feature-claim-status-alerts Compare email and SMS without assuming delivery /help-center/notifications-and-alerts/faq-email-vs-sms Protect information that may appear in an alert /help-center/notifications-and-alerts/faq-sensitive-info-in-alerts Keep personal records and support requests safe /help-center/privacy-and-security/feature-data-protection
More information
Review the current SMS setup Check the number, verification, provider message, and enabled preference without treating a test as a delivery guarantee. Open notification settings /settings#notifications