You can change your SMS Sender ID to an alphanumeric ID (e.g., MYBIZ) or a numeric long/short code once it’s approved by the relevant registry (e.g., DLT in India, 10DLC/short code programs in the US). Submit the request in Settings → SMS → Sender ID, upload proof of brand ownership, and the new ID typically goes live in ≈ 1–48 hours.

Acronyms (quick definitions): DLT = India’s Distributed Ledger for commercial messaging; 10DLC = US 10‑digit long code for A2P; CTIA = US wireless trade association; VMN = Virtual Mobile Number; A2P = Application‑to‑Person.

Table of Contents

• Prerequisites
• Allowed formats & regional rules
• Request or change a Sender ID (step‑by‑step, UI)
• API examples (request, list, set default, send)
• Switching between multiple IDs
• Common pitfalls & quick fixes
• FAQ
• Related guides & escalation

Prerequisites

• Account role: Admin or role with Sender ID permissions.
• Brand documents: Proof of ownership (e.g., GST cert/logo for India, EIN/Trademark for US).
• Compliance: DLT (India) or TCR brand/campaign approval for 10DLC (US). CTIA rules apply to short codes.
• Messaging policy: Opt‑in and opt‑out keywords (e.g., STOP/HELP). Respect quiet hours by country.
• Plan quotas: Starter 1, Growth 3, Enterprise Unlimited active Sender IDs.

Allowed formats & regional rules

Tip: Some international routes replace alpha IDs with local numeric senders. Use Localized Sender IDs per country when available.

Request or change a Sender ID (step‑by‑step, UI)

1. Sign in to your dashboard: https://panel.myoperator.com
2. Go to Settings → SMS → Sender ID.
3. Click + Request New to launch the wizard.
4. Choose Alpha or Numeric. The UI validates length and format.
5. Upload documents (e.g., GST cert/logo for India, EIN/Trademark for US).
6. Click Submit. Status shows Pending.
7. Carrier/DLT approval arrives in ≈ 1–48 hours (you’ll get an email).
8. Toggle Set as Default. New sends will use the new ID.

Zero downtime: Your existing Sender ID continues to work while the new one is under review.

API examples (request, list, set default, send)

Replace YOUR_API_KEY, IDs, and numbers with your values.

Request a new Sender ID

curl -X POST https://api.example.com/v1/sender_ids \  -H "Authorization: Bearer YOUR_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "type": "alpha",                  "value": "MYBIZ",                "region": "IN",                  "documents": ["doc_abc123"]    }'

List Sender IDs

curl -X GET https://api.example.com/v1/sender_ids \  -H "Authorization: Bearer YOUR_API_KEY"

Set default Sender ID

curl -X PATCH https://api.example.com/v1/sender_ids/sid_789 \  -H "Authorization: Bearer YOUR_API_KEY" \  -H "Content-Type: application/json" \  -d '{"default": true}'

Send an SMS using a specific Sender ID

curl -X POST https://api.example.com/v1/messages \  -H "Authorization: Bearer YOUR_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "sender_id": "MYBIZ",    "to": ["+14155550101"],    "text": "Welcome to MyBiz! Reply STOP to opt out."  }'

Switching between multiple IDs

Common pitfalls & quick fixes

Related guides & escalation

• Register your US brand & campaign for 10DLC (A2P) (keyword‑rich anchor)
• Configure SMS keywords for replies and opt‑outs (STOP/HELP) (keyword‑rich anchor)
• Troubleshoot SMS delivery failures and sender ID rejections (keyword‑rich anchor)

Still stuck? Contact support@example.com with your request ID and any DLT/TCR emails attached.

Structured data (optional JSON‑LD for SEO)

{  "@context": "https://schema.org",  "@type": "HowTo",  "name": "Request or Change an SMS Sender ID",  "totalTime": "PT5M",  "description": "How to request, approve, and set a default SMS Sender ID via UI and API.",  "step": [    {"@type": "HowToStep", "name": "Open Sender ID settings", "text": "Go to Settings → SMS → Sender ID."},    {"@type": "HowToStep", "name": "Request new ID", "text": "Click + Request New, choose Alpha or Numeric."},    {"@type": "HowToStep", "name": "Upload documents", "text": "Provide proof of brand ownership as required."},    {"@type": "HowToStep", "name": "Submit and wait for approval", "text": "Approval typically takes 1–48 hours."},    {"@type": "HowToStep", "name": "Set as default", "text": "Toggle Set as Default to start using the new ID."}  ]}

{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {"@type": "Question", "name": "Does it cost extra?", "acceptedAnswer": {"@type": "Answer", "text": "The Sender ID request is free. 10DLC/short‑code program and leasing fees are billed at cost."}},    {"@type": "Question", "name": "Will reports break if I switch IDs?", "acceptedAnswer": {"@type": "Answer", "text": "No. Each message log stores the Sender ID used at send time."}},    {"@type": "Question", "name": "Can I test first?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Use sandbox ID TESTSMS (delivers only to verified developer numbers)."}},    {"@type": "Question", "name": "How many times can I change the Sender ID?", "acceptedAnswer": {"@type": "Answer", "text": "Unlimited within your plan quota. Each new ID requires fresh approval."}}  ]}

• DLT: Distributed Ledger Technology registry for commercial SMS in India.
• 10DLC: US 10‑digit long code framework for A2P messaging.
• TCR: The Campaign Registry, the US database for brand/campaign approvals.
• CTIA: US wireless trade association governing short‑code best practices.
• VMN: Virtual Mobile Number used for 2‑way SMS.
• A2P: Application‑to‑Person messaging (business to consumer).