I have twilio account and it is upgraded.I have IOS application where from customers number the call will be send to many number so it mandiate to verify the number of the user? and if Yes could any one please let me know if there is any automatic verification process to verify that number without disturbing the customer to verify manually?
Twilio developer evangelist here.
You can verify caller ids via the REST API using the Outgoing Caller IDs resource.
Essentially you make a POST request to that endpoint with the number you want to verify. Twilio will respond with a code that you need to show the user. Twilio will also initiate a call to that phone number asking for the user to enter the code. Once they have done so correctly, the number will be verified.
Related
We have a query to ask regarding the Twilio voice communication and hope you will help us.
We are having a client and they are having business with Health care domain having Doctor-Patient communication happening through Twilio cloud.
We know that a non-twilio number can be used for caller id after verification with twilio by 6 digit input from the user.
The client requires a mechanism like when they sell the product to many customers, each customer just input any valid work number (office number) and wants to use those number as Caller Id without the verification process.
We would like to know whether Twilio us offering such custom caller ids without doing the verification steps ? Like with means of a high-level membership plan with twilio or for utlizing any bulk purchase schemes or by trusting the client with any documents or by any other means of ?
Please give your suggestions in this.
Thanks
No. You need to verify each number to use it for your caller ID. Another way of doing it is that you buy the number via Twilio when the customer signs up and that's their outbound caller ID. Would be much easier to do.
david
I was tasked with writing a web app which would allow customers to type and send a message on their browser (mobile or desktop) to a business. I was able to achieve this using Twilio, however the business requested that they received the messages from the customer themselves and NOT the Twilio number.
Basically, they want to establish a connection between the customer and the client via SMS
This is the way I forwarded the message:
Customer Browser -> Twilio -> Business Phone
The SMS body would include customer message, name and phone number.
The problem with this approach is that the business employees want to be able to simply press "reply" on their phone messaging app and connect directly with the customer instead of receiving the text message from a Twilio number, and starting a new message to send to the customer (apparently this doesn't integrate properly with their database).
Is there a way to send an SMS from a Twilio number but appear as if it was sent from a customer number? Hence, change the "from" / "reply-to" number.
Thank you.
Edit: I think its possible that I request and authorize customer numbers to my Twilio account. However this would mean storing customer phone numbers and I'm not sure if I have the permission to do this.
This is how you send a message (NodeJS):
client.messages.create({
body: 'Hello from Node',
to: '+12345678901', // Text this number
from: '+12345678901' // From a valid Twilio number
})
The from attribute MUST be a valid (authorized) Twilio number. Hence why customers would need to give away their number in order to become valid.
In my opinion, this is not possible and that is very good so. Think about the implications if you could just send a message from a number that you don't own. Furthermore, it is not optimal if you would request access to your customer's phone numbers. However, you could use the Twilio proxy service in order to set up the conversation between the client and the customer. For more information please visit the proxy docs. It is still in Beta but works reliably IMO.
You cannot.
Even with the authorized numbers feature, it requires an opt-in via a phone call or SMS response which your customer would have to field.
Perhaps allow a customer to include their number in the message body, which with modern phone's is as simple as clicking the number to bring up the ability to message that number
For more info see here twilio docs
I am unable to find a way to verify my Twilio number is correct before I use it as "from". Does the API allow for validation of the number? I want to validate it before attempting the call which fails.
Twilio developer evangelist here.
If you want to use a number as the caller ID, you need to verify it in your Twilio console here: https://www.twilio.com/console/phone-numbers/verified.
Is it Required to Verify receiver numbers on twilio for making calls after the account has been verified?
Twilio developer evangelist here.
Once you've upgraded your account you will not be required to verify any of the outbound numbers you want to call or text to.
Have a look at this article for more information.
I am working on an Opt-In /Opt-Out api that integrates with Twilio. The way our Opt-In/Opt-Out works is each company (our customer) signs up for one or more Twilio phone numbers and their customers can opt-in/opt-out into these numbers.
When Twilio receives these opt-in/opt-outs we want Twilio to call us into a webhook URL.
So my question is: how do we register these callback URLs? Do these have to be defined at the time when each company signs up for a phone number? If so whats the API end point for that?
These numbers can be added by different companies at any time. Please advise how to do that. We already have URLs defined for sending and receiving SMS messages with Twilio. In this case we first send the message to Twilio and we specify a callback url in that. Can the Opt-In/Opt-outs work with these already registered end points?
All the phone numbers these companies sing up for are created as a subaccount under us. So is that fine with Twilio and can Twilio call us back on the already registered end points (URLs).
If you have any documentation on how to set up an Opt-In/Opt-Out,please include that. I couldn't find one anywhere. The API method we use for creating subaccounts when companies sign up for a phone number is CreateSubAccount and there is no parameter to specify an call back endpoint URL. I tried contacting their support but they haven't gotten back to us yet.
Twilio developer evangelist here.
I'm not sure exactly what you mean when you say "When Twilio receives these opt-in/opt-outs" as the only thing you will get webhooks for is when a number receives an incoming SMS (or phone call, but we're talking SMS right now).
You can set a different SMS webhook URL per each phone number using the API when you buy the phone number. As part of the POST request to the Incoming Phone Numbers resource you can add the optional parameters SmsUrl and SmsMethod.
Once you have purchased the number, you can also update the webhook URLs for it, by POSTing or PUTing to the instance resource, using the same parameters.
Let me know if this helps at all.