Do we need to register each and every phone number using OTP for sending sms in bulk.
for example, if we have 60-70 phones to send the sms, then do we need to register all the 60-70 phones numbers using OTPs for all the 60-70 phone numbers?
thanks to reply.
No, you don't have to "register" phone numbers that you are sending to. See the documentation for more info: https://www.clickatell.com/developers/api-documentation/rest-api-send-message/
Related
With Rocket.chat and Twilio - the incoming chat 'user' is just a mobile number. This is not very user friendly if multiple conversations are ongoing. Responding to and tracking conversations by name and not phone number is much better if possible.
I have a database that could be used to match the incoming SMS phone numbers to a human name for most of my expected incoming SMS IM's. Trying to figure out the best way to do a lookup and add that to the Twilio # identity so that the 'chat' makes more sense to the in-house user who would be using it.
Appreciate any ideas anyone might have that would save me from re-inventing the wheel w/ Twilio and Rocket.Chat.
Related to RocketChat: How to send SMS Messages to Livechat channel from mobile
Twilio developer evangelist here.
I have not used RocketChat for this before, I just took a look through the code to see what I could find.
Turns out, RocketChat has a field for phone number on the user model and when an incoming message is received it looks up a user from their phone number. If the user is found, the message is sent from the user, otherwise a new user is created.
So, what you need to do is merge your database of usernames and phone numbers with the RocketChat User model.
Hope that helps!
I recently started using Twilio to send SMS in one of my apps. Although the twilio's dashboard shows that the SMS was send using the set alphanumeric sender id. It arrives on my phone with a different number totally. Anyone have any idea why? There's nothing about this on the Twilio website.
It turns out this is a carrier problem. They can change sender id (within reason) to increase the chance that an SMS is delivered. So there's basically nothing Twilio can do about it.
If you still have doubts, contact Twilio support.
I have a Twilio test account for now. I got assigned a Belgian phone number and I validated my own mobile number. I'm trying to send simple SMS message from my assigned Twilio number to my mobile number but that doesn't work.
The dashboard indicates "Messaging is unavailable for this phone number." But in the messaging FAQ (https://www.twilio.com/help/faq/phone-numbers/which-countries-does-twilio-have-phone-numbers-in-and-what-are-their-capabilities), it is mentioned that Domestic and Global SMS is enabled for Belgium.
1) Why can't I send SMS messages if my country is listed as SMS enabled?
2) Is it because I have a trial account and will it work once I upgrade?
Answer to your questions:
1) Why can't I send SMS messages if my country is listed as SMS enabled?
For this, I can say may there something wrong in your code.
If your country is listed in SMS enabled countries, then it will work there is no issue.
2) Is it because I have a trial account and will it work once I upgrade?
From an trial account You can send SMS to the number with you registeted. To other numbers it will work after you upgrade your account.
If you share your code then will be easy to help you.
You can refer this, I think it will help you.
http://phpobserver.wordpress.com/2014/03/18/build-sms-text-message-into-your-web-apps-twilio-api/
The problem is that the phone number you have configured is a Belgian phone number. Twilio currently doesn't support sending SMS from a Belgian phone number to a Belgian phone number.
The solution is that you have to configure Twilio to to send the SMS from a US number to the Belgian phone number.
If you're on a trial account, release the assigned Belgian phone number. Then under number management section in your dashboard you will see:
You don't have any Twilio numbers, but your first number is on us. Get it now.
Click on "Get it now". Then, if you verified using a Belgian phone number it will by default show you a phone number from Belgium. Click on "Choose your own number". Then go to the dropdown box and change the country to US such that the proposed phone numbers are US numbers.
With the US numbers you will see that they are capable of sending SMS to Belgian phone numbers. The only disadvantage of this approach is that the SMS will appear to be coming from US. But depending on your application this may not be such a big problem.
Twilio evangelist here.
Its likely that the Belgian number that you were assigned when you created your account only has voice enabled on it, but the good news is that Twilio does have SMS enabled Belgian numbers.
When you click the "Buy a Number" button, you can tell Twilio to only show you numbers that are SMS-enabled:
Hope that helps.
At the time of posting, there were no SMS enabled Belgian numbers available. It seems that the pool of Belgian numbers that support both SMS and Voice is very limited and you need to be lucky to get one.
I have two questions.
I am creating a website for a client I am trying to code in Twilio SMS tools for end users and for management. I have the request and response tools built so I am all set functionally. So the questions are:
A. Can I send SMS message to any phone number OR does every number I send an SMS have to be added to twilio and verified before I can freely send SMS? It would be nice if I could just collect my phone numbers from the end users and free them from the pain of the verification process.
B. If I must verify end users then can I send SMS messages to them with their verification code? Right now an automated message call is sent to the phone number that wants SMS updates and you have to key in a six digit verification code....AND then you can send that person SMS messages. The phone call is kind of awkward.
A. Once you have a regular Twilio account, you can send an SMS to any phone number. However, some phone numbers (e.g., most landlines) cannot accept an SMS. If you try to send an SMS to those numbers with your cellphone, you will probably get a message back from the carrier that the number cannot accept SMS. However, Twilio will report success in sending the message, even though the message obviously cannot be sent to that number, and you will get no indication that the message did not go through.
But, no, there is no need to specifically add the numbers as verified for them to work with Twilio.
You can use a service like https://www.carrierlookup.com/ (which Twilio told me about) to check if a phone number can receive SMS messages.
B. -- you do not need to verify end users through Twilio, although I do think there are restrictions on a Twilio trial account that will be removed once you have a paid Twilio account.
Twilio evangelist here
Once you upgrade, you can send a message to any phone number. While you are using a trial account, you have to verify a number in order to send a message to it. More info about how a trial account works is here:
http://www.twilio.com/help/faq/twilio-basics/how-does-twilios-free-trial-work
Hope that helps.
Regarding verification: Twilio has a service that allows verifying phone numbers, including format, carrier, if it's mobile or landline, etc: https://www.twilio.com/lookup
API Docs: https://www.twilio.com/docs/lookup/api
I have code written up in Processing that works as a serial monitor for my Arduino Fio. I have a few sensors on the Fio that output a warning message when a value surpasses a threshold. How do I get warning statements sent to a phone number as a text message as well?
If you need to send email to just a particular phone (i.e. your own) or a small set of phones known in advance, many carriers have an email SMS gateway. For example, to SMS the Verizon phone 304-555-1212, just send email to 3045551212#vtext.com
See: http://en.wikipedia.org/wiki/List_of_carriers_providing_Email_or_Web_to_SMS
Here is an example on how to send email from Processing: http://www.shiffman.net/2007/11/13/e-mail-processing/
Twitter is a good place to start with this. Your thing -> twitter. Twitter -> SMS (or other clients). Otherwise, it gets expensive and more complicated.