Core capabilityUS SMS deliveryDocumented support for messages to US recipients. 4 points maximum | Supported4 / 4 pts US sender guidance and programmable messaging APIs. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityUS number and sender setupDocumented US sender options and registration or verification process. 4 points maximum | Supported4 / 4 pts US sender guidance and programmable messaging APIs. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkUS sender registration visibilityInspect the status or rejection reason of a US sender registration or verification. 5.6 points maximumAsk for a demonstrationShow a US senderβs current registration status and where rejected details are corrected. A scenario to run with the supplier; not a completed product test. | Supported5.6 / 5.6 pts Verification resources expose rejection reasons, status and resubmission eligibility. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkRecipient-level delivery diagnosisInspect a failed SMS delivery using recipient-level statuses, carrier responses, or error codes. 6.4 points maximumAsk for a demonstrationOpen a failed delivery and explain the recorded cause and supported next step. A scenario to run with the supplier; not a completed product test. | Supported6.4 / 6.4 pts Message diagnostics distinguish carrier errors, template failures and expired WhatsApp windows. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityBulk SMS campaignsCreate or schedule a campaign sent to a contact list. 4 points maximum | Supported4 / 4 pts Bulk Messaging API supports campaign recipient groups and per-recipient personalization; current Bulk API is public beta. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilitySMS targeting and personalizationTarget contact groups or insert recipient attributes into messages. 4 points maximum | Supported4 / 4 pts Bulk Messaging API supports campaign recipient groups and per-recipient personalization; current Bulk API is public beta. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkControlled SMS experimentsSplit recipients between SMS content variants and compare results. 5.6 points maximumAsk for a demonstrationBuild two text variants and show the audience split and separate results. A scenario to run with the supplier; not a completed product test. | Not verified0β5.6 / 5.6 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkFrequency and quiet-hour controlsConfigure both contact-frequency suppression and a recipient-appropriate quiet-time sending rule. 6.4 points maximumAsk for a demonstrationShow how an overlapping campaign and an out-of-hours message are suppressed or deferred. A scenario to run with the supplier; not a completed product test. | Not verified0β6.4 / 6.4 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityReceive and handle SMS repliesReceive customer replies in an interface or documented inbound API. 3.2 points maximum | Supported3.2 / 3.2 pts Studio processes inbound SMS, branches on reply content and sends automated follow-ups. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityTriggered SMS follow-upSend an automated SMS response or event-driven follow-up. 3.2 points maximum | Supported3.2 / 3.2 pts Studio processes inbound SMS, branches on reply content and sends automated follow-ups. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkRule-based inbound reply handlingRoute an incoming reply to an appropriate automated action, person, or team based on its content or context. 4.8 points maximumAsk for a demonstrationSend a sample reply and show how its keyword or customer context selects the next action. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts Studio routes inbound SMS using reply conditions and follow-up actions. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkAutomatic opt-out suppressionProcess an inbound unsubscribe signal so subsequent SMS campaigns or automated steps cannot message that contact. 4.8 points maximumAsk for a demonstrationSend STOP from a test number and show the resulting suppression in the next campaign or flow. A scenario to run with the supplier; not a completed product test. | Supported4.8 / 4.8 pts STOP handling suppresses subsequent sends to unsubscribed recipients. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityStore or CRM connectionsUse a supplied connector to connect business records with messaging. 2.4 points maximum | Not verified0β2.4 / 2.4 pts Not established in reviewed evidence; request this specific demonstration. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityMessaging APIs or webhooksConnect messages or customer events through programmable interfaces. 2.4 points maximum | Supported2.4 / 2.4 pts US sender guidance and programmable messaging APIs. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkExportable delivery-status eventsReceive or retrieve per-message delivery statuses through a documented API or webhook. 3.2 points maximumAsk for a demonstrationRetrieve a sent messageβs delivered or failed status using its external message identifier. A scenario to run with the supplier; not a completed product test. | Not verified0β3.2 / 3.2 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkProperty-aware business-event triggersUse order or custom business-event properties in a triggered SMS. 4 points maximumAsk for a demonstrationTrigger an SMS using a sample order or event and display a property from that event. A scenario to run with the supplier; not a completed product test. | Not verified0β4 / 4 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityAI SMS drafting or reply assistanceUse AI to write an SMS campaign or assist an SMS reply. 2.4 points maximum | Not verified0β2.4 / 2.4 pts Not established in reviewed evidence; request this specific demonstration. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityAI SMS timing, targeting or actionsUse AI beyond drafting for SMS optimization or authorized messaging actions. 2.4 points maximum | Supported2.4 / 2.4 pts Agent Connect integrates AI actions with SMS through the documented SDK; a connected AI application is required. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkAI drafting grounded in business contextSupply stored brand, product, or customer context to the AI that drafts SMS. 3.2 points maximumAsk for a demonstrationGenerate two texts using stored business facts and show the source context supplied to the AI. A scenario to run with the supplier; not a completed product test. | Supported3.2 / 3.2 pts Agent Connect supplies customer memory and knowledge search to the connected AI application. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkHuman review of AI texting actionsReview or explicitly confirm an AI-generated text or messaging action before it sends. 4 points maximumAsk for a demonstrationRequest an AI-created SMS and show the draft, approval, or confirmation step before transmission. A scenario to run with the supplier; not a completed product test. | Not verified0β4 / 4 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkQuery remaining SMS credits through an AI connectorDemonstrate "Query remaining SMS credits through an AI connector" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Query remaining SMS credits through an AI connector" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkRevoke a connected AI client's messaging tokenDemonstrate "Revoke a connected AI client's messaging token" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Revoke a connected AI client's messaging token" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkSet a message delivery expiry timeDemonstrate "Set a message delivery expiry time" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Set a message delivery expiry time" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Limited1.3 / 2.5 pts The Twilio Messaging Segment destination exposes a message validity period. Via the documented Segment destination; seconds-based validity limits apply; not a guaranteed carrier delivery deadline. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkCancel a scheduled message before dispatchDemonstrate "Cancel a scheduled message before dispatch" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Cancel a scheduled message before dispatch" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Scheduled message resources can be cancelled by their identifier before sending. Messaging Service required; documented schedule window is 15 minutes to 35 days; local SMS route eligibility separate. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkReject repeated sends using a request identifierDemonstrate "Reject repeated sends using a request identifier" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Reject repeated sends using a request identifier" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkReject SMS exceeding a configured segment limitUse a test message that exceeds the configured segment cap, including a Unicode character. Show rejection before a billable send. 2.5 points maximumAsk for a demonstrationUse a test message that exceeds the configured segment cap, including a Unicode character. Show rejection before a billable send. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkReplace eligible Unicode characters to reduce segmentsDemonstrate "Replace eligible Unicode characters to reduce segments" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Replace eligible Unicode characters to reduce segments" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Smart Encoding substitutes selected Unicode characters with GSM equivalents. Messaging Services option; emoji and character-based languages are not transliterated. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkValidate cryptographic signatures on message webhooksDemonstrate "Validate cryptographic signatures on message webhooks" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Validate cryptographic signatures on message webhooks" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|