Yeah, apparently the title explains everything.
Could I configure the count of messages per month?
Thanks in advance guys!
Twilio evangelist here.
You can use the Usage Triggers API to have Twilio notify you when a certain number of messages have been sent on a monthly basis.
https://www.twilio.com/docs/api/rest/usage-triggers#create-a-new-usagetrigger-with-params
Hope that helps.
Related
How does the information about recurring payment failure/success reach me?
Do I have to ping it myself or does BT send the response?
If it is the first case then when exactly should I check that? E.g when billing date is 1st August, then at what time it is done?
Full disclosure: I work at Braintree. If you have any further questions, feel free to contact support.
You can set up webhooks that notify you when the status of your subscriptions change. These webhooks are set up in the Braintree Control Panel and send POST requests to your server endpoints when needed.
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 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
When I send the message by Twilio to someone, there is the "[CEG]" in the sending message.
I don't know how to change the message [CEG] or hide the message.
Please, help me.
Thank you.
Twilio developer evangelist here.
This is intentional behaviour in China. Chinese phone carriers require an ID to be appended to the end of a message before delivery. Twilio's ID is CEG so we append it to all messages in China, it is not possible to remove it.
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.