How we did secure telephony for Wheely, a world-wide personal driver service.

Good afternoon, dear readers. We here have recently realized a simple thing - our blog talked for so long about how to implement this or that feature, that we completely lost sight of why . In other words, when there is a specific task, it is easy to find a tool for it. Moreover, for our part, we did the maximum so that it was simple and inexpensive.

However, we often see a situation where the client simply does not know what exactly he can do. Not “how”, namely “why”. As a result, you have a glimpse at a conference somewhere, telling a simple case, and from the ranks comes: “O, and this is a thought!”

Therefore, we decided to make several publications devoted to problems that are solved, conditionally speaking, in 10 lines of code, but the necessity of which does not always occur to us. And the first one: how we made telephony for the service of calling Wheely’s personal drivers.

Find and hide away!

I don’t know about you, but I’m personally annoyed that when I order a taxi through a conditional Uber (or its equivalent), the driver calls to find me in a densely populated place and my number stays with him in the outgoing. I use a taxi often, in different cities I also visit regularly, because of this the number also shines often. And the problem here is not even in the leakage of personal data (although this is offensive), but in the possibility of further contact attempts from this subscriber.
')
Jokes jokes, but one day I was woken up at two in the morning by a call from a drunk taxi driver from Ufa who was looking for a girl who sunk into his soul a couple of days ago. I heard stories from my friends that they received offers to “ride” immediately after a taxi ride. Unpleasant

As you understand, in the case of the service of ordering personal drivers, such an attitude towards personal data is unacceptable. Here and customers are demanding and the drivers are not quite simple drivers. Therefore, when Wheely started using our Voximplant platform, the main thing that they implemented is secure communications.

Wheely is an IT company from Russia that provides call services for personal drivers in London, Moscow, St. Petersburg, Sochi, Kazan, Yekaterinburg and Perm. The head office of the company is in Moscow. Founder Anton Chirkunov was included in the top 30 Russian entrepreneurs under 30 according to Russia Beyond the Headlines.

The call is made through the application of the same name. The passenger comes a clean car at least a Mercedes ‑ Benz E-class. The driver wears a black suit, opens the door, can meet with an umbrella, helps with luggage. Service is positioned as a premium.

As a result, the main tasks were three:

1. Hiding real telephone numbers of both drivers and clients.
2. Recording conversations to resolve conflicts.
3. Scalability as the service “opens” in new cities.

As you can see, traditional telephony was not suitable for this solution.


We are positioning the Voximplant platform as a Lego for telephony. Those. we provide the function of incoming calls to the platform and outgoing calls from the platform. And inside the magic happens, every developer is free to create his own amusement park.

How such a real and serious business case can be implemented in practice using those notorious “10 lines of code”:

Who else might need this solution?

The Wheely example well shows how exactly services can work in conditions of economy uberization, i.e. when projects are created that link multiple consumers with multiple service providers. Such startups grow like mushrooms. And in these conditions it is very important:

• to ensure the safety of communications;
• maintain control over communications, eliminating the possibility of further contact outside the service;
• provide maximum information for further analysis;
• minimize the costs of deploying, maintaining and expanding the system.

And any of these tasks is quite simple to implement.