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.
Related
I am working in an application that gathers a user's voice input for an IVR. The input we're capturing is a limited set of proper nouns but even though we have added hints for all of the possible options, we very frequently get back unintelligible results, possibly as a result of our users having various accents from all parts of the world. I'm looking for a way to further improve the speech recognition results beyond just using hints. The available Google adaptive classes will not be useful, as there are none that match the type of input that we're gathering. I see that Twilio recently added something called experimental_utterances that may help but I'm finding little technical documentation on what it does or how to implement.
Any guidance on how to improve our speech recognition results?
Google does a decent job doing recognition of proper names, but not in real time just asynchronously. I've not seen a PaaS tool that can do this in real time. I recommend you change your approach and maybe identify callers based on ANI or account number or have them record their name for manual transcription.
david
I know Autopilot doesn't support Portuguese, but this is a major bummer.
My bot asks a "yes or no" question (sim ou não) and if the answer is without accentuation (nao), it doesn't understand it means 'não'.
I can't even type in 'nao' as a synonym in the custom field type, it says 'FieldValue already in use'.
I asked the Twillio support 9 days ago and haven't got a reply yet. What do you guys think? Is there a way around this? =/
Twilio developer evangelist here.
The Autopilot speech recognition engine is only working for English, so the transcribed text will always be in English: having "não" as a field value won't work for queries like "nao", but it would be helpful to add "nao" as a field value with synonym "não".
It seems your assistant does not have samples with fields which means if you do not use the Collect Action, those values will never get recognized even when not using voice, since the model does not have those values. Using Collect will be useful in your case; otherwise, I think you should add samples with fields to certain tasks.
Let me know if this helps at all!
I've skimmed through the Keywords Performance Report of the API documentation, and couldn't understand whether it would be possible for me to use this report to determine daily keyword costs.
What I want is basically to be able to look for keyword to an API request result and get the cost associated with it. Is such a thing possible? Am I looking in the right place?
Apparently, it's not possible to do so, since all costs on all Display Network items are listed with a special ID (3000000) in costs, meant to capture all GDN displays.
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.
Does anyone know of a way to get view counts broken down by demographic (age/gender) for a for video and/or a channel?
The YouTube Analytics API is only providing that breakdown by percentage (of logged in users), which is great, but our for our requirements, we need the raw counts. And unfortunately, we can't accurately derive the raw counts from the percentage because the api does not seem to give us the number of logged in users, or enough precision.
Any guidance would be appreciated!
Thanks,
Kris
Sorry, I don't believe that we make those raw counts available on either the web interface or the API—I just checked the web interface and it only shows percentages as well. Feel free to file a feature request and I'll see if there's any chance that we could start exposing more details.