When I send sms text message to a google voice number from Clickatell or TextAnywhere, I get a failure alert (in the reports) and the message is not sent.
Anybody had experience with that?
Google Voice doesn't support international SMSs, as per their documentation
Some providers, such as BulkSMS have had some success in getting message delivery to GV but the ability of the recipient to reply is not there.
Disclaimer: I work for BulkSMS
Related
When we send sms from twilio then we want to set reply to phone number.
So if they reply to the outbound message then incoming message will be received by agent not the twilio number form which we are sending sms.
Thanks,
Rajendra
Twilio developer evangelist here.
I'm afraid there is no concept of a "reply-to" phone number in SMS messages. The recipient of a message can reply to the number that sent the message to them.
If you are looking to try to connect users directly through a Twilio number, I recommend you check out the Twilio Masked Number tutorial (that links to the PHP version, but there are other language versions of the tutorial). It will show you how to use a pool of numbers so that you can maintain a relationship between an agent and a user.
Let me know if that helps at all.
I am sending SMS using Twilio API. During testing i found that it sometimes delivered message to the phone number but does not sends all the time. This is the case of DND activated numbers(Do Not Call List).
I knew this is because of Sender routing done by Twilio. When Twilio sends SMS using a number(only numeric sender-FROM), i received the message, but when it sends message using some alphanumeric sender(like DM-044138), it does not delivers the message.
Now my question is do we have any access to change this ? Can we set something that could guarantee the delivery even for the DND numbers ?
Any help would be highly appreciated.
Your problem is you are sending it to India.
Please review the following.
This feature is only available when sending messages to supported countries
As you can see from the list below India is not a supported country.
https://www.twilio.com/help/faq/sms/what-countries-does-twilio-support-alphanumeric-sender-id
I have a Twilio trial account, and I've been testing a web app for receiving SMS. I've assigned a URL for the inbound SMS messages, and that's been working fine. So far I haven't encountered any limitations on how many SMS messages I can receive, how fast, or anything like that. I didn't find anything on the Twilio website about this, either.
What is the limit, if anything, that my trial account has on receiving SMS messages? I don't need to send a response to the SMS sender, so I'm not worried about the cost to send SMS, or the "Sent by Twilio" that gets appended to a sent SMS.
Here's some information from Twilio's Twitter (dates back to March 27, 2014): https://twitter.com/twilio/status/449231807888621568
"There is no time limit, you can go at your own pace (unless you outpace $30) . More free trial info: http://bit.ly/1fo64aN"
You can check your current balance here: https://www.twilio.com/user/account/usage/primary
My web app sends an SMS text message to users in the US when they enter their phone number, using the Nexmo API. When the SMS contains a link, it does not get delivered to users if their carrier is Verizon or T-Mobile. For other carriers, such as Sprint and AT&T, it does get delivered. It does not generate error messages in any case with Nexmo and I still get charged for the text even if it gets blocked by the carrier.
I contacted Nexmo and they replied:
I would say it is very likely that the link in this sms caused a spam
filter to block this message, especially if other plain content
messages have been delivered to this number successfully. So the issue
with US LVNs is that they are intended for pure P2P traffic and this
is why sending a link might be suspicious and seen as a message
originated from an application. Unfortunately there is nothing we can
do about this as it is set by the US carriers.
These are not definitely not spam or marketing messages. How can I send a link in an SMS message and not get blocked?
I had the same issue recently. All major carriers have some basic checks in place which blocks the SMS from getting delivered if you use short links (e.g.http://abc.gl/1432). The SMS will get delivered as long as you have a .com in the URL (e.g. http://abc.gl.com/1432)
Well, I observed that some carriers mark it as spam if have "Some Message. Click Here http://example/somelink" format.
Removing "Click here" part worked for me.
i.e. "Some Message. http://example/somelink"
Got the same issue. I have been using twilio to a t-mobile phone in the US.
SMS Hello Alan, your code is: 146945 for website.com is not working but
SMS Hello Alan, your code is: 146945 is working fine.
I am new to Twilio API.I have trial account and I have sent Message using Twilio Rest API successfully and received message from number i.e Message as:DM-062107 and body :- Sent from your Twilio trial Account-Hello.
Now I can't able to reply this message.can any one help me to how I can reply to this and how I know that message is received.
I have contacted to Twilio technical support for same problem and get the response. Check the reason why reply option is not enabled:
Although Twilio supports sending outbound messages internationally using toll-free numbers, your Indian number may not support sending inbound messages to US toll-free numbers. I will recommend checking with your mobile carrier to see if sending messages to US toll-free numbers is supported. If not, I will recommend using a regular US number instead of a US toll-free number and kindly retest.
Twilio Evangelist here.
So, to reply to message you just send a normal SMS from your phone to the number. The way Twilio handles this is using a 'webhook'.
If you log into your Twilio account, click on the 'Number' tab, you'll see you have a telephone number there (the same one you sent an SMS with):
Once you've clicked on the number, you'll see a screen with some other details:
Here you can configure your webhook. This is basically a URL that Twilio will send your message to. So if you configure that to point to the URL of some application you have written, you'll receive an HTTP Post or Get request (you can configure which) with the contents of the message, who it is from, etc.
You can then reply to this message with Twiml, which is just XML:
<Response>
<Message>
This is the message that is sent in reply!
</Message>
</Response>
And using this you can build up a conversation!
There are a lot of details on Twilio's website with quick starts etc. There is even a video that talks it through.
Hope this helps.