When my friends text my Twilio bot, Twilio responds from another number which is not even Twilio's and is named "SMSInfo". I expect the bot to respond from the same number. I assure you that I haven't set any logic there that a response should come from another number. Also, note that "SMSInfo" is a number which often sends them verification codes for Fiverr or other things.
I just submitted a ticket to Twilio support and a bot automatically suggested me few articles. One of them solved the issue.
Sender ID change may occur when you send messages from a Twilio number
that is not local to your recipients, for example using a US Twilio
number to send SMS to Polish mobile users. This is often done to
comply with local regulations, or to ensure the highest possible
delivery rate for your messages.
Related
I have had a couple of customers wondering if they can use their own phone numbers to send out SMS using Twilio.
I am wondering if this is possible?
What are the carrier charges in this case and do I need to verify this number before enabling this functionality for an individual user?
The number you want to send messages from (or to) needs to be controlled by Twilio. However, it is possible to port your number from your current provider over to Twilio and thus give Twilio control over that number. This is possible, at least in some countries.
This support article here describes how this can be done for US numbers.
So I'm using Zapier to send text messages to people added to a MailChimp mailing list. A lot of the subscribers are from other countries so I'm just wondering how the interaction works with Twilio.
Will I need a separate number for each country?
Twilio developer evangelist here.
You don't necessarily need another number, Twilio numbers can send internationally (mostly, check the individual settings on the number to be sure, UK landline numbers, for example, can't send internationally).
However, receiving a message from an international number may not be a good experience for your users as they might expect a local number. Good news is that it is easy to build this.
You can create yourself an SMS messaging service. Messaging services are a combination of a number pool along with smart uses of the number pool. You can start your messaging service with one number and add others later. When you add more than one number the messaging service will geomatch between the people you are sending to and the numbers available in the pool, picking the best number for the user.
I'm not entirely sure how this works with Zapier, whether you can set a messaging service ID for your Zap. If that's not possible, you could use Zapier to send a webhook to something like a Twilio Function which you could set up to send the message.
Let me know if that helps at all.
I have a several Twilio phone numbers to send SMS messages to users (2-way sms).
And I want to try Copilot and Messaging service features, but I have my own logic around how I chose the number to send SMS from.
So I need to be able to choose a "from" number by myself.
If I will provide "from" number and MessagingServiceSid at the same time, will this disable Messaging Service Scaler logic?
Sorry, but I can't just test it on my account right now. But I see Twilio Java SDK want me to provide "from" number OR "MessagingServiceSid" but not both. Many thanks.
Twilio developer evangelist here.
You can't set both a MessagingServiceSid and a From number when sending a message. You can either let the messaging service decide which number to use to send your messages (using it's Geomatching, fallback and scaling features) or you need to send the messages using the From number of your choice using the regular API.
If a customer sends STOP to my app's twilio number, twilio will block me sending to that number until the customer texts START. Is there any way around this so that if the customer gave me consent verbally, for example, I can turn the number back on? Or can I configure a long code so that I handle the consent in my app?
Twilio developer evangelist here.
There is no way around this other than having the customer send an SMS saying START, YES or UNSTOP to your number.
Note, when a user opts out of getting messages from one of your Twilio numbers, so you could contact them on a different Twilio number if you had different reason to believe that the user wanted to opt in again without sending one of the above messages.
Let me know if that helps at all.
How does one link a single twilio number to multiple phones such that:
When new people text the twilio number, all of the phones linked to the twilio number receive the text.
When any one of the twilio phones respond to the text, it appears to the original texter that a single number is responding to them (irregardless of which of the twilio phones sends the text).
Picture texts work also in the way described in (1)-(2).
This is very similar to what Google Voice can do, except google voice sometimes doesn't work with picture texts.
You would need a backend of some sort, where you can store subscribers for a number, you can then handle in your language of choice, when you receive a sms perhaps containing the word "subscribe", you would then simply save that into your backend along with the number that the sms was received upon.
When receiving a sms that contains other text, you would then simply query your backend and find all the numbers that have subscribed to the number that you have just received the sms on, you would then simply use the Twilio api, to send the message to all the results from your backend query.
You could also allow unsubscribe functionality, where users only have to send unsubscribe to the number, and you would remove them from your backend or flag them as to not send to them again.