Has US connectivity been restored?

[NeilW]

Connectivity for dedicated US shortcodes (shortcodes used by only one customer) has been restored for all US networks, except Sprint Nextel & Boost. Connectivity for shared US shortcodes (shortcodes used by more than one customer simultaneously) has not been restored for any US network. Messages cannot be sent or received using these shared shortcodes. 

[LlewClaasen]

We have started restoring services for some customers on Sprint Nextel & Boost and hope to accelerate this in the near future.

[LlewClaasen]

I should clarify that the customers that have been restored on Sprint Nextel & Boost are dedicated shortcode customers.

[LlewClaasen]

A letter to our US customers from the CEO of Clickatell http://bit.ly/aWfgoz

[LlewClaasen]

We are pleased to advise that we are authorised to restore the US shared shortcode service. This service is being restored for all US carriers, except Sprint Nextel & Boost, as their policy does not support shared shortcode usage on their network.

We have already reactivated a small number of US shared shortcode customers.

Early next week, we will provide more clarity on the process that the majority of US shared shortcode customers can follow in order to reactivate their US service.

[LlewClaasen]

Connectivity for customers using dedicated US short codes has been restored through all mobile carriers except through Sprint Nextel & Boost, where we are gradually restoring services to an increasing number of customers.

Connectivity for customers using shared US shortcodes (shortcodes used by more than one customer simultaneously) is restored on all US carrier networks with the exception of Sprint Nextel & Boost, as their policy does not support the use of shared short code usage on their network. 

If you are a shared short code customer that has not yet had your service restored, we will either restore your service over the next few days, or we will provide further details on the new process that you will be required to complete in order to reactivate your shared short code service.  This requirement will depend on the nature of your message sending. 

[soonthor]

[quote author=LlewClaasen link=topic=8238.msg10031#msg10031 date=1268061467]
Connectivity for customers using dedicated US short codes has been restored through all mobile carriers except through Sprint Nextel & Boost, where we are gradually restoring services to an increasing number of customers.

Connectivity for customers using shared US shortcodes (shortcodes used by more than one customer simultaneously) is restored on all US carrier networks with the exception of Sprint Nextel & Boost, as their policy does not support the use of shared short code usage on their network.  

If you are a shared short code customer that has not yet had your service restored, we will either restore your service over the next few days, or we will provide further details on the new process that you will be required to complete in order to reactivate your shared short code service.  This requirement will depend on the nature of your message sending.  
[/quote]

Hi,

Is there a way to expedite the fixing process? My service has been down for about a week. I'm a HTTP API SMS customer. If I create a brand new API_ID, will it work right away? Or I still have to wait? Thank you for your help.

Soonthorn

[mphill]

Service is still down and not functioning.  Messages status from the send request return as successful making it impossible to determine the message failed.  How difficult would it be to at least mark the message as failed?  The API certainly need to be updated.  Messages also will not route to google voice members at all.  They just flat out fail.

[eric94z28]

Service is still down for me also.  The only good thing is that the API (SMPP) is returning a "Routing error" and not getting charged.  This is pretty bad to have service down for this long!  Anyone have referrals to any other SMS service provider?

[michelle]

I agree. why the heck can't clickatell send these messages back with an error code.

And more importantly, why didn't clickatell tell/text/email us.... their paying customers......that there was an issue....right from the start. Why did we have to hear it from my customers first? We check the codes coming back in error... so if you'd just sent them all back with an error code we'd be able to react quicker for our customers.

Why isn't clickatell telling us how they are measuring us to determine if they will turn the service back on for us? If we know what the criteria is, and we weren't abiding by it, we could be proactive and could make necessary changes so that we'd be inline.

I'm not even sure clickatell makes sense now anyway, especially if you can't send to sprint/boost.

We've gone somewhere else for our service now.

[LowVolCustomer]

Still down.  Still getting promises from Clickatell that they will be letting us know "within a few days".  Still have a bunch of angry customers and egg on our face.  Still no idea when (if) service will be restored, or what kind of "information" our customers are going to be "required" to disclose to continue to be alowed to pay for SMS message service.  Unbelievable!!!

We will implement other strategies and stay away from Clickatell ASAP.

[gcampher]

Clickatell has restored connectivity to our US customers that make use of dedicated short codes, to all participating US carriers, including Sprint/Nextel. Shared short code access will not be restored to the Sprint Nextel & Boost networks, as their policies do not support shared short codes.

The reactivation process is taking longer for our shared short code customers, because we are required to audit customer account adherence to our terms and conditions and accepted industry guidelines. We’re also classifying accounts into message service types for reactivation, which is designed to ensure that future service interruptions are minimized for all our customers; this process is time consuming, but in the best interest of guaranteeing an ongoing service to you.

If your shared short code service has not yet been restored, then you will receive specific communication around this program, very shortly.

[clickbook]

"routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error", "routing error"

ZERO messages being delivered to the USA.  HELP??  account: clickbook

[dh0llyw00d]

my test messages via the api aren't being received and messages to google voice are failing