I do not completely understand how to handle STOP messages if I have only one campaign. Should I respond with "... text 1" when I receive STOP or can I simply opt out the user without asking them to send '1'?
EDIT:
I am trying to implement message handling for a SMS short code to be compliant with the carrier requirements. https://www.twilio.com/help/faq/short-codes. Basically, to be compliant with the requirements, I have to handle specific SMS messages that I receive, in particular, STOP message that should opt out the number that sent it from my "campaign". A "campaign" is intuitively a series of SMS messages that I sent to users. Here is Twilio help entry that explains STOP messages.
I do not understand whether I have to ask the user to text me back 1 as the page suggests if I have no other choices. Can I just handle this STOP as I would do STOPALL?
Here is a response that I received from Twilio support, in case someone else wants to ask this "non programming related" question:
"If you have one campaign, then you can opt them out the same way you would do a STOPALL."
Related
I am sending a text to a mobile number (US phone number) using the Programmable Messaging Quickstart for C# with .NET Core example. The message is sent and received successfully but the STATUS in the response shows "queued".
Is there a sample callback in C# to obtain the final status after the text is sent?
You have 3 options, either of the first two are suggested.
Subscribe to statusCallbacks, which will alert your application of the delivery status of the send message.
Use Event Streams to subscribe to specific message delivery event types (this option provides the ability to select different types of message delivery events).
Less efficient and not very scalable, make a request to the /Messages endpoint to determine the final disposition of the sent message (via its unique message SID).
Best Practices for SMS Message Logging
I have a very simple alert mechanism to alert drivers "in-the-field" when a new pickup has been assigned to them. I have had an instance twice where a driver has responded with a STOP and became un-subscribed. Once discovered we acquired the proper opt-in documentation from them. Is there any way to re-subscribe a user that opted out and changed their mind on receiving the messaging. i.e. they issued the STOP to the incorrect SMS. And have deleted the original message to START. Or do I need to code something for them to opt back in
My SendGrid provides a method to remove suppression from email but am not finding anything like that here in Twilio.
They need to send a START to the number they previously opted out of, this is currently a requirement. You will also get an error when trying to send messages to them, to alert you they opted out.
Error 21610 - Attempt to send to unsubscribed recipient
I have a notification-only bot, and I would like to send a welcome message to users only when the bot is added to a personal conversation.
I listen to 'conversationUpdate' events as stated here, though I keep receiving the same event multiple times one after the other for the same user, all events identical (except the event ID and timestamp).
I respond to the event with HTTP status 200 (I handle them via REST).
Does anyone have an idea why I would receive the same events multiple times and how to avoid it? Is it some kind of retry due to an unexpected response on my end?
It even says here: "For personal scoped bots, your bot will only ever receive the conversationUpdate event a single time, even if the bot is removed and re-added."
We had some sort of bug that queued up the same message thousands of times, each of them is undelivered because of the spam carrier restrictions, because it was a not real number or something.
We've looked around their docs and stack overflow but can't find anything that looks relevant.
It seems like Twilio keeps trying though - over and over - so it's send out thousands of the same message and keeps queueing them. Or at the very least
How can we clear our whole SMS message queue? We're happy if we never send it again, as nothing in there is mission critical.
The best approach is a ticket to Twilio support via the Twilio Console or help#twilio.com as a P1 (with you Account SID), indicating you have an out of control process queuing up thousands of SMS messages.
They will ask that you fix the process and fail the messages in queue.
There is a number that has been automatically replying with SMS, and of course each reply costs money. It was not a number that was ever sent a message to, so it is baffling as why it is sending automatic responses back.
How does one block a number so not to receive messages from?
Update : Made it clear that reply was in SMS format.
I can't comment yet but please see this
Unlike voice, there’s no way to block specific SMS messages or sending
parties