Route declaration is the set of capabilities that is declared by the supplier to Twilio. This helps Twilio select proper routes for the right traffic. Priority one is to declare active route capabilities to not lose current traffic as Twilio will prefer to use declared routes over the undeclared. Priority two is to declare the routes where you have really competitive terms and want to propose interest in Twilio to consider using it. We suggest you first declare the HQ best capability routes.
How can I submit my route capabilities?
In the portal you have links on the left side panel and choose “routes”. This will open the full list of routes where you have submitted prices for Twilio. We have sorted the list based on current volumes but by setting proper filters you should find any route easily. At the end of each line you see the “three dot” button as in this picture below. It opens a menu with options to “edit features”.
On the details screen next picture, you see default values but you should revise each of the configuration options which reflects this account traffic logic. Consult with your Twilio account manager for better alignment.
This view allows you to declare fully featured SMS, or special use-case with limited capabilities, or none SMS alternative channel. A free-text field in the Portal is helping us understand any limitations or conditions you have for our routing team. Please note, this field is not for questions, as it is not monitored for responses.
What are the Twilio expectations in the route declaration flow?
To achieve better alignment we are now exposing which values are needed to comply with fully featured traffic types.
The first step starts from auditing new routes where you can choose between going with the suggested expectations, or go with custom selection which suits better for alternative routes. Same logic applies when you start “editing” an already audited route. On the route edit page follow the values where you see our suggestions and your choices which are still un-aligned, see the picture below.
Be cautious as the connection type must also match Twilio expectations but upgrading of the value without actual routing change on your side leads to potential conflict.
May I have an option for bulk changes?
Yes you can do bulk changes. On the first picture of the route list you see check-boxes in front of each line. This way you can group routes which share exactly the same configuration. Above the list view you see the button where you can select to apply an already configured route declaration for the selected list.
Twilio will evaluate each route declaration against our routing needs and perform the tests. In case of good match and proven quality the route is enabled and benchmarked constantly against competitive options. In case of standard traffic this benchmark is provided in Supplier Portal.
Because we can list only these routes which are submitted by the supplier from the rate deck. The global list of countries and networks might be bigger than the available list of active rates. By adding or removing rates via rate ingestion you can manage the list of routes in the portal.
Portal presents routes which are sent by you over the price ingestion emails. With the next email add price for the new destination and this will be presented soon for auditing the capabilities. You might also want to add another connection account to serve more traffic types. Reach out to your account manager for alignment.
Even when you stopped propagating new price updates for certain routes then these might be still visible in the route list because of historical reasons. Removal of the routes will be implemented in the future and will notice you then. These routes don't need an audit for capabilities and we suggest you do it only for the most competitive routes where you want to cooperate.
Termination price can be still uploaded over the rate ingestion emails, but for a hands-on experience it can be also changed in the portal on individual route level to respond to specific opportunities. Click on the three dot icon at the end of the route line and select changing the price.
Twilio conducts two sort of tests:
Capability tests which proofs your audited route working in a declared way and
Quality tests which evaluate your route performance against others.
After testing audited route capabilities we will share the summary in the route list. For more details click on the “view details” command at the end of a specific row. From the opened page you will see declared capability values and test results. Scroll to the failed situation and read the notes Twilio has provided. For example picture below explains, GSM7 body preservation not delivering specific characters and UCS2 test message was not terminated.
Twilio categorizes testing outcomes into next states:
Success: All audited capabilities function correctly, meeting Twilio's expected standards.
Decline: A test may be declined if Twilio's interest in the destination is minimal or if the capabilities audit is incomplete and prevents testing.
Failed: Indicates one or more capabilities did not perform as expected. Review the route's details page for specific issues. Failures may result from undelivered messages, sender ID preservation issues, or incorrect character set transmission. Quality not meeting expected levels can also cause failure.
Partial: describes the situation where Twilio is not able to evaluate certain capability and as this is not caused by you then it's also not considered as a failure. Your route proposal will be still evaluated.
When you adjust the initial capability configuration for the route, Twilio will automatically initiate a new test. However, if you have resolved the issues that led to a failure without altering the current capabilities, and you wish for Twilio to retest, please reach out to your account manager to request this or use the self-serve button in the portal route details page.
Why is Twilio not conducting a quality test even if our route passed capability tests?
Quality tests are taking more time and are carefully monitored. Because of bandwidth we are currently handpicking the most promising offers and focusing on the high volume destinations. Over time this process becomes automated and you start receiving faster feedback over the all remaining routes.
Quality might be not evaluated also when price or set of capabilities are not aligned with Twilio routing needs.
Yes. Twilio conducts initial tests after you add your route capabilities. If a test fails or the pricing isn't competitive enough for quality analysis, the offering enters an idle state. We understand the importance of second chances, so you can now initiate a re-test directly from the Supplier Portal. Please note that while we encourage improvement, select carefully where re-testing makes sense, as it is limited.
Click on the "View Details" link in the appropriate row of the route list. On the details page, you'll find a "Testing" button located in the upper-right corner, as shown in the image below.