The Story of Abu Dhabi’s Toll Gate – Why Comms Shouldn’t Need to Clean Up After Others

When things go wrong, the first people to deal with the blow-back are communicators. Organizations need to involve comms early on, to better anticipate what may not work, and what the response will be

It’s been a month of chasing, of phone calls, visits and Tweets. And yet, there was no update, no new information. I’m talking here about my experience with Abu Dhabi’s new toll system. The idea is simple; Abu Dhabi, the UAE’s capital city, wanted to set up a road toll tax on drivers entering certain areas. To do this, drivers had to register on a website prior to the system going live (there’s already a road toll system operating in the UAE, in Dubai. The Abu Dhabi version is different to Dubai’s).

So far, so good. We had just over a month to get our affairs in order, before the toll gates went live on October 15. I wanted to be proactive, and so I went to the website to register my car. The questions were straightforward – I needed to provide the details of my national ID card, my car plate, an email and password. Simple, you’d think. I must have tried a couple of times, and I couldn’t register. All I kept getting was the below message (which really wasn’t helpful).

“Something went wrong” may be an accurate description of the whole IT system, but it’s not going to help users understand the issue

I call up the contact center. They ask for my national ID number before asking for my name (which I found strange), and then advise me to go in and log an issue. I do this, and register a complaint a whole month before the deadline. The adviser tells me I’ll get a call once the issue is solved. No call comes in for a couple of days. I call up, and there’s no update. What I do understand is that many other people are going through this same experience. I tweet, and get the same response over and over again. I’m not alone, sadly.

The inevitable happens, and the service’s introduction was delayed, from October 15 to January 1.

Given the need to register (if you don’t, you’ll be fined per day), I can imagine that there would have been thousands of people wanting help, and spending time reaching out to the government body in question. These channels would have been handled by the customer service/communication teams. I feel for the people manning the phone lines or the social media accounts, as there’s little they can do to control a situation, besides from repeating the line that “IT is working on it.”

This whole back-and-forth conversation reminds me of how uncommon it is in many regions for both communications to be brought into the design process, and how little user testing there actually is before a new system is rolled out.

It’s simple. A difficult experience erodes trust. A good experience builds trust. Transparency in challenges helps engender trust. Spin does the opposite (and lots of people will know when they’re being spun).

My hope is that this story will be a lesson learned, especially for governmental bodies who want to roll out new technologies, and who need to engage both their communications teams and potential users early on. Communications is there to help, so bring the right people in (preferably those with experience who ask the right questions, anticipate what may happen, and understand how to best engage with an intended audience), listen to their advice, and ensure that these people are part of the whole innovation process, from end to end. I’m sure I speak for many communicators in the region when I say that I don’t want to clean up for others; I simply want to help create a better product or experience which I can talk about. Are you with me?