10dlc Registration

Register for 10DLC as a sole proprietor to enable SMS messaging in the USA. Use when setting up A2P SMS, registering brands/campaigns, or assigning phone numbers for compliant US messaging. Requires Telnyx CLI.

Security Scan

The skill's requirements, instructions, and included scripts are consistent with registering 10DLC via the Telnyx CLI and only ask for the Telnyx API key and CLI tooling they need.

Purpose & Capability

Name/description match the actual behavior: scripts and README use the Telnyx CLI and Telnyx API to create brands/campaigns and assign numbers. Required binary (telnyx) and required env var (TELNYX_API_KEY) are appropriate for the stated purpose.

Instruction Scope

SKILL.md and scripts stay within the 10DLC registration domain: they call telnyx 10dlc commands, check auth, prompt the user before assignments, and provide troubleshooting. There are no instructions to read unrelated files, access unrelated credentials, or send data to endpoints outside Telnyx/documentation links.

Install Mechanism

There is no package install spec in the registry metadata, but setup.sh installs the Telnyx CLI via 'npm install -g @telnyx/api-cli' if npm is available. Installing a global npm package modifies the system environment and requires privilege; this is expected for a CLI-based skill but users should verify the package origin/version before installing.

Credentials

Only TELNYX_API_KEY is required and declared as the primary credential. The scripts do not request unrelated secrets or other environment variables. telnyx auth setup will prompt interactively for credentials as expected.

Persistence & Privilege

Skill does not request always:true and is user-invocable. Setup modifies local state only by installing the Telnyx CLI (global npm install) and making included scripts executable (chmod). Those are reasonable for this functionality but are system-level changes the user should be aware of.

Assessment

This skill appears to do only what it claims: it wraps Telnyx CLI commands to register 10DLC and requires a Telnyx API key and the Telnyx CLI. Before installing or running setup.sh: verify you trust the '@telnyx/api-cli' package and its source, be prepared that 'npm install -g' will modify your system/node environment, and never share your TELNYX_API_KEY with untrusted parties. The scripts prompt before making assignments; run test.sh to validate CLI/auth prior to doing real registrations.

Register for 10DLC (10-Digit Long Code) to enable A2P SMS in the USA.

Quick Start with Scripts

# Interactive registration wizard
./scripts/register.sh

# Check status of brands/campaigns
./scripts/status.sh

# Assign a phone number to a campaign
./scripts/assign.sh [phone] <campaign-id>

Prerequisites

• Telnyx CLI installed: npm install -g @telnyx/api-cli
• API key configured: telnyx auth setup
• At least one US phone number

Quick Start

Interactive wizard (easiest):

telnyx 10dlc wizard

Manual Registration

Step 1: Create Sole Proprietor Brand

telnyx 10dlc brand create --sole-prop \
  --display-name "Your Business Name" \
  --phone [phone] \
  --email [e-mail]

Step 2: Verify Brand (if required)

telnyx 10dlc brand get <brand-id>
telnyx 10dlc brand verify <brand-id> --pin 123456

Step 3: Create Campaign

telnyx 10dlc campaign create \
  --brand-id <brand-id> \
  --usecase CUSTOMER_CARE \
  --description "Customer notifications and support" \
  --sample-message-1 "Your order #12345 has shipped." \
  --sample-message-2 "Reply STOP to opt out."

Step 4: Assign Phone Number

telnyx 10dlc assign [phone] <campaign-id>

Step 5: Wait for Approval

telnyx 10dlc campaign get <campaign-id>

Use Cases

Use Case	Description
2FA	Auth codes
CUSTOMER_CARE	Support messages
ACCOUNT_NOTIFICATION	Account alerts
DELIVERY_NOTIFICATION	Shipping updates
MIXED	Multiple purposes

List all: telnyx 10dlc usecases

Status Commands

telnyx 10dlc brand list
telnyx 10dlc campaign list
telnyx 10dlc assignment status [phone]

Troubleshooting

Common Errors

Error	Cause	Solution
Brand verification required	Sole proprietor brands need phone verification	Check email/SMS for PIN, run telnyx 10dlc brand verify <id> --pin <code>
Campaign rejected: insufficient description	Description too vague	Be specific about message purpose, include business context
Sample messages must include opt-out	Missing STOP instructions	Add "Reply STOP to unsubscribe" to sample messages
Phone number already assigned	Number linked to another campaign	Run telnyx 10dlc unassign +1... first
Brand pending	Still under review (24-72h typical)	Wait and check status with telnyx 10dlc brand get <id>
Invalid use case for sole proprietor	Some use cases restricted	Sole prop limited to: 2FA, CUSTOMER_CARE, DELIVERY_NOTIFICATION, ACCOUNT_NOTIFICATION
Rate limit exceeded	Too many API calls	Wait 60s and retry

Debug Tips

# Verbose output for debugging
telnyx 10dlc brand get <id> --json

# Check number assignment status
telnyx 10dlc assignment status [phone]

# List all campaigns with details
telnyx 10dlc campaign list --json | jq '.data[] | {id, status, usecase}'

Timeline Expectations

Step	Typical Time
Brand creation	Instant
Brand verification	1-5 minutes (PIN via SMS/email)
Brand approval	24-72 hours
Campaign review	24-48 hours
Number assignment	Instant (after campaign approved)

Getting Help

• Telnyx docs: https://developers.telnyx.com/docs/messaging/10dlc
• Support portal: https://support.telnyx.com
• API status: https://status.telnyx.com

Pricing

Brand and campaign registration: Free