In the Twilio platform, you can create an "Application" to bundle common configuration details for phone numbers. From https://www.twilio.com/docs/api/rest/applications:
An application inside of Twilio is just a set of URLs and other configuration data that tells Twilio how to behave when one of your Twilio numbers receives a call or SMS message.
Is there a limit to how many phone numbers can be joined into a single Application?
Twilio developer evangelist here.
"TwiML Applications" like the one you mention are designed to be aliases easy to use on a ton of numbers at once, we have a lot of very high volume customers using them on 10,000+ Twilio numbers and probably even a lot more.
In case you need to go beyond those numbers, it's always worth contacting sales as they will be able to increase that for you accordingly while making sure you scale well.
Hope this helps you.
Related
I am on a team that has to be on-call 24/7. Our team is comprised of 5-6 members and we each take a week. If the business calls our dedicated on-call number (Twilio), I would like that to make an outbound call to a sequential list until somebody on that list answers the phone.
Is this possible using either C# or Python along with Twilio of course? I am not a developer, but if I can be pointed in the right direction I think I can figure it out. It appears Twilio has voicemail detection so I'd imagine I would have to utilize that feature.
Target has an Open-source project you can look at that may already meet your needs, powered by Twilio.
https://github.com/target/goalert
GoAlert GoAlert provides on-call scheduling, automated escalations and
notifications (like SMS or voice calls) to automatically engage the
right person, the right way, and at the right time.
I'm struggling to locate a reference for the Carrier strings that can be returned from the Twilio phone-number lookup API.
For a problem I'm working on, I need to know the full set of possible values but API docs appear sparse.
Twilio developer evangelist here.
We don't provide a list of all carrier names for this use. From the documentation:
Please bear in mind that carriers rebrand themselves constantly and that the names used for carriers will likely change over time.
I request the Twilio Server for a AvailablePhoneNumberList.But I get three different number type.Should I purchase for Local,Mobile,or Toll-Free number?
Twilio developer evangelist here.
There are actually 4 kinds of numbers. You can read all about the different number types here. But here's a quick rundown of them:
Local numbers
These are numbers that are mapped to a local region. Normally you would be able to tell where the number was from if you were from the country, for example, in the UK numbers starting (+44)020 are London numbers. In the US a number starting (+1)415 is in San Francisco. These are useful for local businesses as the number can match up to where the business is located.
National numbers
These are similar to local numbers except the geographic area they are tied to is the entire country. They are more useful for national scale businesses that want to be easily reached from anywhere in the country.
Mobile numbers
If you want to use SMS messaging and want users to understand that easily, then mobile numbers are normally the best approach. They tend to have a different number to local or national numbers (for example in the UK they start with 07) and that stands out to users.
Toll free numbers
These numbers are national scale numbers and mean that the end user does not pay to make calls to them. They are useful for support or helpdesk lines where the business can take on the cost of the call for the user.
As I said, there is more detail on the Twilio site but I hope this helped.
I am trying to purchase mulitple numbers using c# with the Twilio API. However currently we must purchase one number at one time, It takes a lot of time to purchase 10-15 numbers in the loop.
So how can I pass a list of numbers through API so it takes less time to buy numbers from twilio.
Twilio evangelist here.
Today there is no way to buy numbers in bulk via the API. You have to make one API request per number that you want to buy.
If the library is not performing fast enough for you, first I'd love to know what kind of performance you are seeing and what you expect so I can work on improving the library.
Second, I'd suggest looking at just using the built in .NET HTTP client libraries instead of using the Twilio library. The library is pretty general purpose and tuned more for ease of use than performance. If you can use .NET 4 or higher, you can use the TPL to get some good perf gains. I've built samples using the HttpClient library and TPL that resulting in substantially higher requests/sec than the library gives me today.
Hope that helps.
Is there a way to use the Twilio API to determine if a phone number is Local, Mobile, or Toll Free?
Better yet, can this be determined at the call level?
Twilio Customer Support here.
The short answer for non Twilio numbers is no, as at time of writing Twilio does not offer a number look feature via the API.
The slightly longer answer is it depends on what country you are calling as you could create some functionality to assess the number - I can see your based in the USA, so Toll Free numbers will use 800, 888, 877, 866, 855, and 844. Unlike most other markets the USA does not distinguish between Mobile and Local numbers but other countries usually separate the two e.g. UK Mobile numbers start with +447.