Requirements for SMS Enabling

Last updated: 2025-08-28Contributors
Edit this page

Enabling SMS on RingCentral Phone Numbers

By default, RingCentral phone numbers—whether assigned directly to an extension or purchased separately—do not have SMS functionality enabled.

To enable SMS functionality, follow the appropriate steps based on the type of phone number:

Local (Domestic) Numbers

If you are enabling SMS functionality on local phone numbers in the U.S. or Canada:

  1. Register your brand and campaign: You must complete both brand and campaign registration and receive approval before proceeding.

  2. Link phone numbers to your approved campaign: Only phone numbers that are linked to an active, approved campaign will be enabled for SMS messaging.

Learn more about registering your business to send text messages.

Toll-Free Numbers

If you're enabling SMS functionality on toll-free numbers:

  1. Complete the toll-free verification process: Toll-free numbers must be verified to comply with industry regulations and to enable SMS.

Learn more about SMS toll-free verification for your numbers.

Once your number is properly registered, it will be SMS-enabled. Based on the registration configuration, the system will attach the following features to the number’s metadata, indicating that it supports sending and receiving SMS and MMS messages:

  • SmsSender – Enables standard SMS messaging
  • MmsSender – Enables MMS messaging (multimedia)
  • InternationalSmsSender – Enables sending SMS messages to international numbers

Note

  • If a phone number is provisioned for high volume SMS, the number metadata feature will be A2PSmsSender
  • If a toll-free number is provisioned for SMS, the phone number will not have the MmsSender feature as toll-free number does not support MMS.
  • The InternationalSmsSender feature is enabled if the phone number is enabled for International SMS.

Understanding Phone Number Ownership and Feature Assignment in RingCentral

In RingCentral, each account has a phone number assigned as the main company number and additional purchased phone numbers. The additional phone numbers can be assigned and reassigned to different resources. The assigned resource can be a user extension, a call queue extension, an IVR extension, a site (a site itself is a special extension) or the main site’s auto-receptionist.

Typically, all phone numbers with voice capability include the CallerId feature in their metadata, indicating that the number can be used as a caller ID. If a phone number is SMS-enabled, the phone number will also have the SMS features as discussed in the previous section.

When a phone number is assigned to a resource, the resource is the owner of the phone number, but the features of the number are assigned differently depending on the type of the resource.

  1. If the resource is a user extension, that extension is automatically assigned with all the features that number has, allowing the user extension to use the number to make phone calls and to send or receive SMS messages (provided that the number is SMS-enabled)
  2. If a phone number is assigned to a common resource, such as a site or an IVR, the CallerId feature is automatically assigned to all user extensions belonging to that common resource. The SMS features of the number can be assigned (or reassigned) to only 1 selected extension and only that selected extension can send or receive SMS messages from that phone number. The assignment can be done via the Account Admin Portal via the company auto-receptionist general settings. For step-by-step guidance, please refer to this article.
  3. If a phone number is assigned to a call queue, the CallerId feature is automatically assigned to all call queue’s members. But the SMS features of the number must be manually assigned (or reassigned) to only one user extension, regardless of if the user is a member of the call queue or not. The assignment must be done through the Account Admin Portal. For step-by-step guidance, please refer to this article.

The following table shows how the phone number features are assigned to extensions based on the type of resource which owns the phone number:

Assigned Resource Number Usage Type CallerId feature SMS features
User extension Direct Number The extension itself. The extension itself.
Auto-Receptionist Main Company Number & Company Number All extensions under the account. Dedicated assigned user/call queue extension.
Call Queue Extension Direct Number All call queue’s members. Dedicated assigned user/call queue extension.
IVR Extension Direct Number All user extensions under the site where the IVR is created for. Dedicated assigned user/call queue extension.
Site Extension Direct Number All user extensions under the site. Dedicated assigned user/call queue extension.

Only the extension assigned to a phone number’s SMS feature can send and receive SMS messages using that number.

Checking Phone Number SMS Configuration

Phone number SMS configuration data refers to the specifications of a TCR (The Campaign Registry) registration, in which a phone number is assigned to a registered SMS brand and campaign with a specific declared purpose. This configuration is the result of the SMS enabling process, which links the phone number to its associated SMS brand and campaign.

Developers can use the SMS brand and SMS campaign information from a phone number’s details to determine its eligibility and capacity for sending text messages.

To read a phone number's SMS configuration, read a user's phone numbers, then use the identifier of a phone number to call the following API.

HTTP GET `/restapi/v1.0/account/~/extension/6295925XXXX/phone-number/[phoneNumberId]/sms-configuration`

// Sample response
{
  "phoneNumberId": "121554771345",
  "phoneNumber": "+16501112345",
  "smsCampaignInfo": {
    "id": "2008",
    "externalId": "C8VLZXY",
    "status": "Confirmed",
    "registrationTier": "LowVolume",
    "useCases": [ "CustomerCare", "AccountNotification", "DeliveryNotification" ]
  },
  "smsBrandInfo": { "id": "1008", "status": "Verified", "externalId": "BG3LNOP" }
}

Note

If a phone number is not linked to any TCR campaign, it's not fully SMS enabled and the smsCampaignInfo and the smsBrandInfo objects are omitted.

The most critical fields to review are the registration status values for both the SMS brand and the SMS campaign. If the SMS campaign’s status is anything other than "Confirmed", outbound SMS messages from that phone number will fail.

The registrationTier field specifies the maximum daily outbound message volume allowed for the campaign with the possible values below:

Value Description
"LowVolume" Max 6,000 messages per day across all numbers (sent to US mobile carriers)
"StandardVolume" More than 6,000 messages per day across all numbers (sent to US mobile carriers)

And the useCases array lists the approved message categories (for example, "CustomerCare", "AccountNotification", "DeliveryNotification"). These values help ensure that messages sent align with the registered purposes of the campaign.

Use case category Description
"CustomerCare" Customer interaction notifications
"AccountNotification" Notifications on an account's activity status or renewal reminders.
"DeliveryNotification" Information about the status of a delivery.
"ConversationsInternal" Day to day messages between employees working at your company.
"ConversationsExternal" Day to day messages with external parties like customers or vendors.
"FraudAlert" Informing customers about likely fraudulent activity.
"HigherEducation" Notifications from colleges, universities or other educational regarding reopening, examination update, and so on.
"K12Education" Notifications from schools including announcements, schedule updates info for students and parents, and so on.
"MachineToMachine" Authentication notification such as one time passwords (OTP) and passcodes. A.K.A "Outbound 2 factor authentication"
"Marketing" Communications that include marketing and promotional content including discounts, special offers, or other marketing-related use cases.
"Mixed" Brands that have multiple agents, franchises or offices in the same brand vertical, but require individual localized numbers per agent/location/office.
"PollingVoting" Conducting customer surveys for non-political campaigns.
"PublicServiceAnnouncement" General announcements regarding public awareness campaigns.
"SecurityAlert" Notifications warning about security threats or breeches such as suspicious login attempts, unusual activity on their account or phishing attempts.
"Unknown" None of the above.

An SMS campaign can be registered under multiple categories. To successfully send a text message from a phone number, the message content must comply with at least one of the campaign categories associated with that number.

If your app supports sending SMS messages, it’s best practice to read the phone number’s SMS configuration and display its categories alongside the phone number. This helps remind users of the intended purpose for sending SMS messages from that number.

For example, if you need to display three phone numbers that a user can select to send an SMS from, read each number’s SMS configuration and store the information in an array, then create a dropdown list as shown below:

[
  {
    "phoneNumber": "+16501234567",
    "smsCampaignInfo": {
      ...
      "useCases": [ "ConversationsExternal", "DeliveryNotification" ]
    },
    "smsBrandInfo": { ... }
  },
  {
    "phoneNumber": "+14082223333",
    "smsCampaignInfo": {
      ...
      "useCases": [ "CustomerCare", "Marketing" ]
    },
    "smsBrandInfo": { ... }
  },
  {
    "phoneNumber": "+13125550404",
    "smsCampaignInfo": {
      ...
      "useCases": [ "ConversationsInternal" ]
    },
    "smsBrandInfo": { ... }
  }
]