SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site,, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Default Messaging Service

Starting April 18, 2024, Twilio will begin auto-generating a default messaging service on all Twilio accounts. All Twilio accounts will have this default messaging service available in the future.


What is a messaging service?

A messaging service is a higher-level "bundling" of messaging functionality around a common set of senders, features, and configuration. The same settings and feature configuration apply to all of the senders (long code numbers, short codes, toll-free numbers, etc.) in the Messaging Service's pool. Review Twilio’s Messaging Services doc and Messaging Service API Resource to learn more.

What is the default messaging service?

The default messaging service is a messaging service generated by Twilio. Each Twilio Account will have only one default messaging service. This default messaging service's name is “[Auto-generated] Default Messaging Service”.

This default messaging service will be used to process your message traffic if no messaging_service_sid is used in your Messages API POST request. This default messaging_service_sid value will be visible in Messaging Logs/Messaging Insights.


How is the default messaging service different than a normal messaging service?

Messages “route” through the default messaging service when a Messages API POST request is made without explicitly passing a messaging_service_sid.

You can change the configuration for your default traffic by updating the messaging service settings in Twilio Console or via the API.

If you haven’t specified a messaging_service_sid in your API request, you can use these attributes:

  • Link Shortening (if shortenUrls is set to True)
  • Content Settings (Smart Encoding, MMS Converter)
  • Validity Period

Note: adding your sender(s) to the sender pool will cause the default messaging service configuration (if configured) to handle the following:

  • Incoming Messages (ie. defer to sender's webhook, drop the message, etc.)
  • Delivery Status Callback (only if you pass the messaging_service_sid in your POST request)
  • A2P & Compliance
  • Opt-Out Management

Can I delete the default messaging service?

No, you can’t delete the default messaging service.

Where can I see the default messaging service?

The default messaging service can be seen in the following locations:



Have more questions? Submit a request
Powered by Zendesk