I have to add an automated telephone verification feature for my web application. That is when the customer clicks a button in the web interface, he/she should be called (customer's phone already in the database) and asked to enter some identification number in the telephone keypad and then the calling system should notify the results to a URL.
I am searching a service provider for this. Please give me some recommendations.
Tropo or Twilio would both be appropriate for your needs.
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 am using the Verification service and all working fine. My Service Name appears in the body of the Verification message correctly but how can I change the SMS From label?
In my SMS app I see a list of messages from various contacts and companies, the message from Twilio Verification Service shows as a 5 digit code e.g 12345. How can I change that from 12345 to "MyService"?
I get messages from other companies and a short company name appears as a contact name, how can I do the same with my twilio verification service?
Thanks
Twilio developer evangelist here.
Twilio Verify uses a variety of short codes, alphanumeric sender IDs and other phone numbers in order to send the verification messages around the world. The Verify team work on ensuring the numbers/sender IDs have the best possible delivery by pre-registering them in various countries. This gives you the highest possible chances of getting authentication messages delivered swiftly. You can't customise the number by default.
If you are looking to customise the number that is used, I would recommend you talk to the Twilio sales team to see what you can arrange.
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 building a mobile-focused web application, to later convert to hybrid, and I would prefer new user registrations confirm the user's phone number versus their email address.
I would like to send a new user an SMS with a unique code. When they first log in, they must enter that code to activate their account.
I have a custom SMS service that is sending SMS fine, and would like to know how to integrate this into the Identity registration process.
Please note that I do not wish to use SMS for routine two-factor authentication.
You can use create additional actions in your account controller
and use methods from Microsoft.AspNet.Identity.Core
UserManager.GenerateChangePhoneNumberToken
Send sms with token
UserManager.VerifyChangePhoneNumberToken
Add custom logic to authorization
There are several ways to accomplish this.
Cheap but not reliable or enterprise ready is to build an app on a device you own and have those other devices send an SMS to it. You can process the SMS and reply however you like. With unlimited texting plans, it would be fine. It's just not redundant or reliable (the phone battery could die, you may need to do updates that could interrupt service, etc.)
Work with a company like Twilio (https://www.twilio.com/) and use their SMS gateway, API and services to build, quickly and cheaply (for the most part) the type of service you are looking to provide. There are competitors to Twilio and I'm not endorsing them, just providing them as an example.
Obtain your own SMS gateway (https://en.wikipedia.org/wiki/SMS_gateway) and then do heavily integrated and customized services.
If this is just a proof of concept at the enterprise level or you don't know what your user adoption rate will be, then #1 is probably fine until you need #2. #3 is rarely the best option.
I've seen several applications that use Twilio for SMS verification go from:
Sending the user a 4-5 digit code to enter on their handset
to
Pre-filling a 32+ character SMS message that the user sends from their device to the services Twilio number.
Is there any documentation out there on how to implement an approach like this?
Twilio evangelist here.
It sounds like your asking two different questions, one regarding two factor authentication and one regarding autocreating an SMS message on the device for the user to sent to Twilio.
If I've got that correct, then I'd start be working through the Two-Factor Authentication How To article that walks through setting up SMS-bsased two factor authentication.
Another resource to check out is the Add Two-Factor Authentication to your Website with Google Authenticator and Twilio SMS blog post.
As far as generating a text message on a device, I think that is going to greatly depend on what kind of mobile device you are targeting.
Hope that helps.