When I send a test sms from https://www.twilio.com/user/account/developer-tools/api-explorer/message-create with a predefined friendly name, it doesnt apear on my phone. I only see the number.
-if this isnt possible, do you know other providers with this function that work?
[UPDATE]: Twilio now supports this feature.
You can now send messages from an alphanumeric sender ID using Twilio. I wrote up a blog post on how you can achieve this in Ruby and you can check out this article on how to get started with an alphanumeric sender ID on Twilio for more of an overview. Then check out the documentation on how to send an SMS message from an alphanumeric ID.
[UPDATE] Previous answer is below.
Twilio developer evangelist here.
You're absolutely right, the friendly name defined in your account is actually for your uses only and is not intended to appear in place of the number when sending an SMS. We have a few reasons for this, which might be interesting to you depending on your use case.
I don't have a particular company that I can recommend that does allow you to do this. A Google search might help though.
Related
I use twilio to send sms messages but in the message I am trying to create it is a very long url and therefore won't send in 160 characters so twilio cuts the message off and url doesn't work.
If I use the automated twilio Shorten SMS the same thing happens.
I assume there is a limit to the amount of characters Twilio will send and I believe it cannot join concatenated messages in Australia from Twilio.
Edit: as of August 2019 Twilio has discontinued its URL shortening service. You should consider using a 3rd party service that allows you to set a unique base URL.
Sharing a static base-URL for a link shortener can cause unexpected carrier filtering issues with U.S. 10-digit long codes (short codes are not carrier filtered). Carriers sometimes spam filter messages by content, and the base-URLs of the links being shared appear to be one way that they categorize spam.
Twilio is working on a next-generation URL shortener that provides randomized base URLs as an add-on to a messaging service. If you are interested in this functionality contact Twilio support.
You should check to see that URL shortening is explicitly enabled in your account before attempting to send messages.
https://www.twilio.com/console/sms/settings
I've been using Twilio to send SMS and things work great. The only issue is that Twilio charges for both outbound and inbound messages. As such, we've been looking for other solutions.
We thought we found it with Plivo as their pricing was more favorable for SMS.
However, with Plivo, very quickly our outbound messages are being marked as spam or something and they're not being delivered.
We are sending the exact same message every day to about 5k users at a given time in the day. The message has a url in it, but it is something our users signed up for.
Two questions:
1. Why does everything work on Twilio and not on Plivo?
2. Is there a code change I can make to ensure our outbound messages sent with Plivo are not marked as spam by carriers and then stopped?
You need to contact Plivo about this. I experience this problem too. Their carrier mark our number as spammer since we are sending almost the same messages (verification). They called their carrier and our number was white-listed.
Plivo Sales engineer here. This is indeed an issue with the carrier marking your messages as spam. We can definitely help you overcome this. Could you please drop an email to ramya(at)plivo.com and we can sort this out?
You need to contact with Plivo support , there may be problem for number prefix for country like if you are using twilio you have to add +(with country prefix) but not in Plivo. It will be better to contact with Plivo support.
Thank You
I dont know how Pilvo work but usually with SMSC there is Message Queue associated sometimes with each SMPP Client and also with Mobile Station. You can't always send messages until your certain number of request are still pending. there is a specific error code that SMSC sent to its client about message queue overflow.
BADABING BADABOM! After having a look in the Plivo administration I noticed a new option under other-settings "Automatic Encoding Of Unicode Characters". As Norway uses inernational characters this is definately a setting for me, and after enabling it all SMS are delivered as expected. So remember to enable this setting.
MAKE SURE TO ENABLE THIS:
Path: Plivo admin / Messages / Settings / Other settings
Feature: Automatic Encoding Of Unicode Characters -> Enable
I am making an event organisation platform. Whenever user creates an event, the candidate gets an email notification as well as sms notification asking whether the suggested time fits or not. The problem is that since it is event organisation, there may be more than one occurance of candidate's mobile phone. So I need to have some unique information to identify to which event candidate is responding to.
I have tried identify using Message SID, but then I realised that Message SID is different on reply message.
So my question would be: is there any way to authenticate to which message candidate is replying to?
Hi Twilio developer evangelist here.
Because every message is idempotent, you wouldn't be able to track them just via the call sid. however, there's way to get around that such as passing a code that goes with each message which you can then read, or using cookies.
I think you are probably going to be more successful using cookies, and luckily enough there is an article on twilio's website that describes just how to do that. And because I noticed you're using PHP, I'm pointing you directly to the PHP article on tracking SMS conversations.
Hope this helps you
Could anyone tell which countries would be able to send and receive SMS AND calls to Latvia?
I can't seem to find an answer, it appears that LV numbers can't send SMS, yet I see prices on the pricing page. I'm quite confused as of which country I should get a number in (and the price).
If I get a LV number, does it mean i can send, but not receive SMS? It would be fine for my app (already built, waiting to go live).
Basically, it is a browser app acting as a soft phone (single user), so no landline involved. Is there a way to solve the country problem?
Twilio evangelist here.
Looks like we currently only have Voice enabled Latvian numbers (numbers with a +371 prefix). Buying one costs you $1 US and use can use it to have Twilio make a voice phone call from it or receive phone calls to it.
For SMS, Twilio does support sending international SMS from US numbers, so you certainly could buy a US number and use it to send text messages to a Latvian number. The pricing for that is here (scroll down to see per-carrier pricing details).
Hope that helps clarify.
Is this possible and is it possible to have it POSTED along with the SMSMessage to an endpoint?
No, Twilio doesn't provide that information. Part of the goal of the Twilio API is that you shouldn't have to worry about that as it's not relevant to actually delivering the message.. it's like knowing your users' ISP.
Disclosure: Twilio employee
Unless you do!
If you are using lookup to get the carrier to send Mobile Topup to, you require the carrier name. Actually, the thing you will need is the mapping of all possible carrier names that Twilio can produce, so you can map them to our own internal carrier list.
You are required to list a carrier when attempting to verify many accounts. So even though Twilio did not anticipate this it is indeed needed. For example try verifying your facebook account. There you are required to list a mobile carrier...