Using a Twilio Messaging Service improves your customers' SMS message experience with routing and content intelligence features that you can control from the Twilio console. A Messaging Service is a higher-level “bundling” of messaging functionality around a common set of senders, features, and configuration.
This guide will help you understand what a Messaging Service can do for you and show you how to send SMS messages with a Service in your ASP.NET application. The code snippets in this guide are written using modern C# language features and require the .NET Framework version 4.5 or higher. They also make use of the Twilio C# SDK.
Sending messages at a high volume and/or at a global scale quickly balloons in complexity. That's why Twilio Programmable Messaging encourages the use of Messaging Services to manage your senders, maintain compliance with local carrier regulations, and create a smooth and consistent messaging experience for your end users.
Some Messaging Service features include:
- Sticky Sender: Use the same
Fromphone number to message a given customer for a consistent experience
- Smart Encoding: Save space (and money!) by automatically converting hard-to-catch Unicode characters to UCS-2 compliant characters
- MMS Converter: Automatically convert links to media files for areas in which MMS is not supported
- Advanced Opt-Out: Manage your opt-out, opt-in, and help keywords and messages
- Sender ID pre-registration alert: Get notifications when you are sending messages in countries that require pre-registration of your Alphanumeric Sender ID
- ...and more!
For more information, check out the list of Messaging Service Features with descriptions and configuration information for each feature.
You can create a Messaging Service through the Twilio Console or using the REST API with the following code:
Sending SMS messages requires an SMS capable phone number. You can search for and purchase available phone numbers in the Console. When you search, make sure that the number you choose is SMS capable. Check the appropriate box in the search UI to filter available numbers to those that are SMS capable.
Now, associate your Twilio number with the Messaging Service that you created.
You can do this in the Twilio Console in the Senders section under your Messaging Service. Click the Add Sender IDs button, select the Sender Type, and assign the senders to your Messaging Service.
You can also use the Messaging Services REST API to add the Phone Number you purchased to your sender pool. To do this, you will need the Phone Number's unique SID, which starts with
PNXXX. You can find this in the Phone Numbers Section of the Twilio Console.
Use the Phone Number's SID to attach to the Messaging Service that you created:
You must add at least one phone number to the Sender pool for your Messaging Service before it can send messages.
Sending a message with a Messaging Service is a lot like sending a message from a Twilio number, with one key difference. Instead of specifying a `From` telephone number in your API request, you specify a Messaging Service SID, its unique identifier.
In this example, we'll use the Messaging Service SID (It looks like "MGXXX...".) of the Messaging Service that we just created.
Run the code sample, replacing the Messaging Service SID ("MGXXX...") and the `To` number with your own mobile phone number (or a friend's!). In a few seconds, you should receive an SMS message!
Sending an SMS using a Twilio Messaging Service sets you up for efficient scaling. As your messaging needs grow, your Messaging Service will automatically handle the multiple senders in your pool as well as maintain consistent interactions with your end users around the world.
Ready to build more? Check out the following resources: