Resources and numbers
Resources are the core assets you need to communicate with customers across different channels.
They include sender identities and communication assets like phone numbers, sender names, and email domains that give your business a presence across channels.
Before you can start communicating on any channel, you must obtain these resources through Infobip and configure them for your use case.
Learn moreIn Infobip documentation and APIs, resource, sender, and number are equivalent terms for the same concept: your communication asset on a specific channel.
- Resource: The category of communication asset: numbers, alphanumeric senders, email domains, RCS senders, and digital channel senders.
- Number type: The classification for phone numbers: virtual long number (VLN), short code, toll-free, and 10DLC. Referred to as
numberTypein the API.
For example, VLN is a sender type of the Numbers resource. In API docs and sending APIs (SMS API reference, Metrics API), you see these terms used interchangeably.
How resources work
Resources serve as entry and exit points for all communication on the Infobip platform. Every outbound message originates from a resource that customers see as the sender. Inbound messages are routed to a configured resource, giving you visibility and control over incoming traffic.
Each resource type supports a defined set of channels: a phone number can be used for SMS, MMS, Voice, and WhatsApp simultaneously, but not for Viber or RCS. Similarly, an RCS sender cannot be used for SMS. The resource type you choose determines communication capabilities, regulatory requirements, and approval timelines.
Some resources enable two-way conversation while others are one-way only. Choose the resource type that matches your use case. Consider whether you need two-way messaging, how quickly you need activation, and what regulatory requirements apply in your region.
If you are managing multiple applications, entities, or customers, see CPaaS X: Understanding resources for advanced resource allocation, associations, and multi-tenant billing models.
Resource types
| Resource | Description | Channels | Communication |
|---|---|---|---|
| Numbers | Phone numbers (VLN, short code, toll-free, 10DLC). Dedicated or shared ownership. Examples: +441234567890 (UK VLN), 12345 (US short code), +18003334444 (US toll-free) | SMS, MMS, Voice, WhatsApp* | Two-way |
| Alphanumeric senders | Custom branded names (3-11 characters) for one-way SMS. No replies supported. Examples: NIKE, ACME_CORP, YOURBANK | SMS only | One-way |
| Email domains | Custom domains with DKIM verification for branded email sending. Examples: orders@yourbrand.com, support@company.com | Two-way | |
| RCS senders | Branded A2P messaging with multimedia, buttons, barcodes, and interactive elements. Examples: CNN News, Chase Banking, Amazon Deals | RCS | Two-way |
| Digital channel senders | Custom sender names for digital messaging channels. Channel-specific requirements apply. Examples: Nike Bot (Viber), CNN (Messenger), Apple Support (Apple Messages) | Viber, Messenger, Apple Messages, LINE, KakaoTalk, Zalo, Instagram | Channel-dependent |
*WhatsApp requires separate WABA (WhatsApp Business Account) registration. Get a virtual long number (buy new, use existing, or migrate), then register a WhatsApp sender on the number and connect it to a WABA. See the WhatsApp embedded signup guide for complete steps.
Find your resource by channel
| Channel | Resource type | How to get started |
|---|---|---|
| SMS | Phone numbers (VLN, short code, toll-free, 10DLC) OR Alphanumeric senders | Buy phone numbers (direct) or Request alphanumeric senders (approval required). USA: Complete sender registration workflow |
| MMS | Phone numbers (VLN, short code, toll-free, 10DLC) | Buy phone numbers (direct). USA: Complete sender registration workflow |
| Voice | Phone numbers (VLN, 10DLC) | Buy phone numbers (direct) |
| Virtual long number + WhatsApp sender (WABA) | Register sender (multi-step) | |
| Email domains | Configure in Channels and numbers (no approval needed) | |
| RCS | RCS sender | Register and launch sender (multi-step) |
| Apple Messages | Apple sender | Configure in Channels and numbers (no approval needed) |
| Telegram | Telegram sender | Configure in Channels and numbers (no approval needed) |
| Instagram sender | Configure in Channels and numbers (no approval needed) | |
| Messenger | Messenger sender | Configure in Channels and numbers (no approval needed) |
| Viber | Viber sender (Bot or BM) | Request sender (approval required) |
| LINE | LINE sender (OA or ON) | Request sender (approval required) |
| KakaoTalk | KakaoTalk sender (Alim, Brand, or Sangdam) | Request sender (approval required) |
US SMS and compliance
US SMS is regulated by the FCC, CTIA, and major carriers (AT&T, T-Mobile, and Verizon). All USA phone numbers require brand registration and campaign approval before sending messages.
Three USA sender registration paths are available depending on your use case, volume, and timeline:
10DLC (10-Digit Long Code)
Standard virtual long number with moderate volume and fastest approval (1-2 weeks). Best for marketing, transactional, and OTP messaging.
Short code
Premium 5-6 digit number for high-volume campaigns and time-sensitive messaging. Longer approval (2-4 weeks) but superior throughput and brand recognition.
Toll-free
800/888 numbers optimized for customer service and support. Moderate approval (1-2 weeks) with inbound-focused capabilities.
All paths require brand registration, campaign approval, and TFN/TCR verification.
Learn more- USA sender registration overview: Complete workflow: buy a number, register a brand, create a campaign, and launch.
- USA SMS compliance requirements: CTIA standards, consent requirements, and opt-out compliance.
Get started with resources and numbers
Step-by-step guide to buying a phone number or registering a sender for your channel.
Numbers
Number types (VLN, short code, toll-free, 10DLC), ownership models, and coverage by country.
Alphanumeric senders
Custom branded names for one-way SMS \u2014 requirements, country restrictions, and registration.
Request resources
Choose your path: buy directly through the web interface, configure in Channels and Numbers, or submit a multi-step approval request.
Manage resources
Configure inbound routing, keywords, and channel-specific settings after obtaining your resource.
Resource request procedure
Understand the 6-phase approval process, timelines, and what to expect after submitting a request.