Getting the message "Message delivery status ERROR_DELIVERING", is there a way to automatically resend the sms? - clickatell

I have clickatell connected to my marketing platform, and I'm sending a general message. My question is, when I get the message "Message delivery status ERROR_DELIVERING" (in clickatell), is there a way in clickatell, to resend it automatically?

Related

Why would messages not be received by recipients?

When I send messages no one receives them. When I check the activity log on my twilio account it shows they've been sent. The only messages that actually get delivered are the ones sent to my own phone.

Slack - confirm before send

Is there a way, by means of some setting or programmatically, to allow a user on Slack to confirm that the user really wants to send a message before the message is sent? Often times we end up sending messages on the wrong channels or DMs. How can we prevent these?
Assuming by "send a message" you mean "post a message" to a channel.
Via Settings
No. There is no Slack setting to enable confirmation before a message is posting.
Programmatically
No. Its possible to retrieve all messages that are posted to a channel with a Slack app (e.g. via Events API) and then react to them, but only after the fact. To the best of my knowledge it is not possible to insert some kind of confirmation logic into the standard process of posting a message.

How are Alert Triggers for Message Delivery Errors set up using the Twilio Console?

I am building some SMS functionality into a CRM, and I cannot seem to get notifications for message delivery errors.
30001: Message Delivery - Queue overflow
30002: Message Delivery - Account suspended
30003: Message Delivery - Unreachable destination handset
30004: Message Delivery - Message blocked
30005: Message Delivery - Unknown destination handset
30006: Message Delivery - Landline or unreachable carrier
30007: Message Delivery - Carrier violation
30008: Message Delivery - Unknown error
Alert Triggers for both "Any Error" and "Error - 30007" are set up.
After they were set up, a few "30007 Carrier Violation" undelivered errors were created. They do show in the logs, however, they don't trigger any alerts, show in the current value column on the Triggered Alerts page, or show in the debugger.
When I visit the debugger, or even the dashboard, I see errors and warnings listed (i.e. 81011, 82001, etc.), but I see no 3000* errors, even though 3000* errors do exist in the programmable SMS logs.
Is there a setting I'm missing to see message delivery errors like I see other errors?
Thank you in advance!
Twilio support got back to me. They made a change to my account that fixed this.

Receiving two-way SMS messages with Twilio and Link Inbound message with Outbound message

We are using Twilio for sending outbound message to our customers.
When we send Outbound SMS to Customer then we are storing Outbound message details in our Database.
Also we have implemented Inbound SMS. So if we receive any inbound SMS from customer then we are creating inbound message record in database.
Now our requirement is that if sent a sms to Customer and then customer replied to that outbound message then we have need to store Inbound SMS under Outbound SMS, so we can relate inbound message with Outbound message.
Is there any way to identify in twilio that inbound message that we have received is related to which Outbound message (may be can we use any unique identifier)?
Thanks,
Raj
Twilio developer evangelist here.
There is no affordance in SMS to reply to specific messages. You can see this yourself by opening your SMS app on your phone and trying to reply to the second to last message you received from someone. It's simply not possible.
So, you can either make the assumption that if you have sent a message to a user that their next inbound message to your number is in response to that.
Or, you can use multiple numbers to send different messages, associating responses based on the number that sent/received the message.
Hope that helps.
Full disclosure I work at Till Mobile.
I believe you can achieve this using our A2P SMS platform (which happens to utilize Twilio).
Till creates a unique id for the to and from phone number combination when an outbound message is sent.
When an inbound message is received it is tagged with the same unique id. In the Till API this id is called the project_launch_guid.
Using the Till API
You can get a free username and api_key via https://tillmobile.com/
Send the outbound message
curl -H "Content-Type: application/json" -X POST -d '{
"phone": ["phone_number"],
"questions" : [{
"text": "Welcome to the customer appreciation program. If you have a question please respond.",
"webhook": "http://requestb.in/1ilpbfd1"
}]
}' "https://platform.tillmobile.com/api/send?username=username&api_key=api_key"
Which returns
{
"project_launch_guid": "some_guid",
...
}
Retrieve the inbound message
If a user later responds the message will be POST'd to the webhook defined above in this format including the same project_launch_guid returned from the send:
{
"project_launch_guid": "some_guid",
"participant_guid": "585897f2-2c30-43f5-8f6b-7c243e8ac4b0",
"participant_phone_number": "phone_number",
"question_guid": "685897f2-2c30-43f5-8f6b-7c243e8ac4b0",
"question_text": "Welcome to the customer appreciation program. If you have a question please respond.",
"result_guid": "885897f2-2c30-43f5-8f6b-7c243e8ac4b0",
"result_timestamp": "2016-11-27T11:57:14.060474",
"result_answer": "How do I redeem my points?",
...
}
Note: the webhook is optional. If it is not provided the inbound message can be retrieved via our results API:
curl "https://platform.tillmobile.com/api/results?username=username&api_key=api_key&project_launch_guid=some_guid"
Using either the webhook or results API the project_launch_guid can be used to tie the outbound and inbound messages together. The result_answer attribute value will contain the user's inbound message.
FYI We treat each send like a session. They persist indefinitely unless another send is created with the same to and from phone numbers. In that case the second send is queued behind the first and a configurable TTL is set on the first.
We have more documentation available here https://till.readme.io/docs/
Don't hesitate to let me know how we can assist further.

Outlook REST API Push Notification always send the same ResourceData

I subscribed to Outlook Push Notification Services, precisely I want to receive push notifications for sentitems.
Consequently, I use https://outlook.office.com/api/v2.0/me/MailFolders/sentitems/messages as Resource in my #Microsoft.OutlookServices.PushSubscription POST request to the url https://outlook.office.com/api/v2.0/me/subscription
As expected, I receive the push notification when I send an email. The problem lies in the fact that the ResourceData is always the same. The Id never changes and correspond to the one I received after the first Notification.
I also remarked that even when no mail is sent I keep receiving notification with "ChangeType":"Created" (and always the same ResourceData.Id).
This may be a bug, or should I send back something to the subscriptions after receiving a notification?
This is because the webhook responded to the push notification request with status code 500. Hence Outlook Push Notification Services treated this request as failed and then retried it later for several times. As the notifications of the same subscription are processed in sequence, later notification won't be sent until the earlier notification was successfully sent out. That's why you saw multiple notifications with the same resource data and change type even when no change happened.

Resources