Your taxi has arrived: what happens at the pickup

The short answerTwo things can tell you: the driver has a button he presses at the kerb, and our side also watches the taxi’s own position and says it has arrived without waiting for him. Whichever gets there first is the one you receive, so the arrival is never announced twice. A message then goes out at three minutes of waiting, and your telephone rings at five. After a quarter of an hour we stop and it is the driver’s decision.
Book a taxiWhatsApp +972 53-900-0023📞 02-376-7000
A dark card with the words "At the pickup", the heading "Your taxi has arrived", a drawn yellow taxi with a TAXI roof sign waiting at a kerb, a yellow circle holding a drawn clock, and the round Hello Taxi badge with hellotaxi.co.il beside it — illustration

How do you know the taxi has arrived?

Two separate things tell you, and either one is enough on its own. The driver presses a button when he reaches you; and our side watches where the taxi actually is and says so whether he presses or not.

The second of those is the one that matters, because it does not depend on anybody remembering to press anything. A rider could once be left sitting indoors while the taxi stood outside, each waiting for the other, until one of them gave up — and we had known where the car was the whole time. Now the position itself does the talking.

Watching the position gives you two messages: one as the taxi comes close, saying it is about a minute from the pickup, so you can put your coat on; and one when it is outside. The driver’s button sends that second one too, so whichever of the two gets there first is the one you receive and the other falls silent — the arrival is never announced to you twice. The other messages on this page are separate, and each of those is sent once as well.

Why “outside” is drawn a little wider than it sounds: in a street with tall buildings a telephone’s idea of where it is can be wrong by tens of metres, so a very tight rule would fire late, or on a bad day never. It is deliberately generous enough to be reliable, which means the taxi may be a few doors along rather than directly at the number.

The driver’s own button has its own guard rails. It only appears on his screen once he is genuinely near, it only comes alive when he is nearer still, and our side refuses a press that arrives from too far away however it was sent. So “arrived” cannot be tapped from across town.

What does the app show at that moment?

The banner at the top of the live map turns green and reads Your driver is here, with The taxi is waiting outside — head out under it.

That is what a ride booked ahead shows. The banner moves through the ride’s states — Confirmed with Driver accepted your ride, then Driver En Route with Your driver is on the way once the driver presses on my way — and the green one replaces that second state. It was made to behave like that in October 2026, because before then the banner still said the driver was on his way while the taxi sat outside.

On a taxi you booked for now, expect none of that. There is no on my way step on those rides at all — the driver’s button goes straight from accepting to starting the ride — so the banner stays on Confirmed and the green one never appears, however plainly the taxi is outside. That is the commoner case, and it is why the message matters more than the screen.

Even on a ride booked ahead the banner needs one more thing: the driver must have pressed arrived. If he never pressed it — and you were told by our watch on the taxi’s position instead — the banner stays as it was. So trust the message, not the banner. The message reaches you either way.

Under the map your pickup and your destination are written out, which is worth a glance — if the pickup on that card is not where you are standing, that is the thing to ring about, immediately. Under those are the two buttons you actually want at this moment: Call Driver and Message, both live once a driver has taken your ride. If we hold no number for him the call button says so rather than doing nothing, and the message still gets through.

The notification itself arrives in Hebrew, as most of our live ride messages do. The screens are the English ones: the live map and your rides list say the same thing in English, which is why they are worth opening rather than reading the notification. What notifications we send goes through the whole set.

How long will the taxi wait for you?

At least four minutes once he has pressed arrived, because until then he is not allowed to cancel. Beyond that there is no stated number and we would rather say so than invent one — what there is, is a sequence: a message at three minutes, a telephone call at five, and nothing from us after a quarter of an hour.

WhenWhat happens
The taxi comes closeA message that it is about a minute from the pickup
The taxi is outsideA message that it is here, with the driver’s name. When it came from our watch on the taxi’s position, a plain text message follows if that one did not reach your telephone
Three minutes of waitingA message that the driver has been waiting, carrying his telephone number, where we hold one, on the WhatsApp and text-message versions
Five minutesYour telephone rings. A short line in Hebrew, then a shorter repeat, then it hangs up
A quarter of an hourNothing more from us. It is the driver’s decision by then
Each of these is sent once per ride. The first two go off where the taxi is; the last three are counted from the taxi arriving, or from the time you booked for, whichever is later.

The three-minute message is the useful one, and it is built for you to act on. On the WhatsApp and text-message versions it carries the driver’s own telephone number, where we hold one, for exactly one reason: somebody who really is two minutes away can say so and keep the ride. A driver who knows you are coming waits; a driver sitting in silence starts to think he has been forgotten.

At five minutes your telephone rings, and our usual number shows — but there is nobody at the other end to talk to. A machine voice says in Hebrew that the taxi is waiting and asks you to come out, repeats it in fewer words, and hangs up. If it reaches a voicemail it hangs up rather than talking to the tape. Nothing else reliably gets somebody off a sofa, and by five minutes the ride is genuinely about to be lost.

After a quarter of an hour we stop chasing you. That is not a threshold with a penalty attached; it is us deciding that somebody fifteen minutes late is not about to appear, and that pestering them helps nobody. From there it is the driver’s call whether to wait on or give up.

On a ride you booked for a later hour, the clock starts at the booked time or when the driver arrives, whichever is the later of the two. So a driver who parks at your door ten minutes early is not being kept waiting and you will not be chased for those ten minutes; and if he turns up after the time you booked, the clock starts when he actually gets there.

You are genuinely two minutes away — what should you do?

Tell the driver, straight away — in the app with the Call Driver and Message buttons on the live map, and on WhatsApp or by text message with his own number, which travels with the three-minute message there. That one sentence is what keeps the ride.

That is the whole reason his number is put in front of a WhatsApp or telephone rider at three minutes rather than kept back, and why the app puts the two buttons where it does. A driver who has been told “I am coming down now” almost always waits. A driver who has heard nothing has no way of telling you apart from somebody who has changed their mind, and he is losing money every minute he sits there.

Say where you are coming from if it is not obvious — the back entrance, the car park, the sixth floor with one lift. A driver who knows he is waiting on a lift waits differently from one who thinks he is being ignored.

What not to do is cancel and rebook in the belief that it will be quicker. It will not: you lose the taxi that is already outside your door and start again from nothing, and cancelling at that point has its own consequences. If you genuinely cannot come, cancelling is right — just do it rather than letting the driver sit.

And if the taxi is not where you expected it, look at the pickup address on the live map before anything else. We will have sent the driver to the point that was on the booking; a point that was never right is the commonest reason for two people standing a street apart. Giving a pickup address covers how to stop that happening next time.

What if you booked on WhatsApp or by telephone?

You are told the way you booked. A WhatsApp rider gets it in the same chat; somebody who rang 02-376-7000 gets a plain text message.

Nobody is left out of this because they have no app. The choice is made for each ride from how it was booked, so the arrival message and the three-minute message reach a telephone-line rider as ordinary text messages to the number they rang from, with the driver’s number on that second one, and the five-minute call rings that same number.

App riders have a backup for most of it, though not for all of it, and the difference is worth knowing. On the messages where silence costs you the taxi, a notification that did not actually reach your telephone is followed by a plain text message to the number on the booking — that covers the arrival when it came from our watch on the taxi’s position, the three-minute message and the rest. The one gap is the arrival when the driver pressed his button: that sends a notification and nothing else, so an app rider with notifications switched off can miss it. Keep notifications on, keep the right number on the booking, and if you are expecting a taxi it costs nothing to glance at the live map.

What a telephone or WhatsApp rider does not get is the live map, so the Call Driver button is not there. The driver’s number in the three-minute text message is the way to reach him, and booking without the app explains what else differs.

When does the ride count as having started?

When the driver starts it, or — if he forgets — by itself, once the taxi has been at your door and has then driven a couple of hundred metres of road away from it.

Drivers pick passengers up and drive off without tapping anything; that is simply what happens when somebody is doing a job with their hands full. So the ride starts itself. The rule is deliberately about road driven rather than distance from the door, because a taxi leaving a car park, a hotel forecourt or an airport terminal can drive a long way round and still be close to the door as the crow flies, and for minutes the ride would sit there saying it had not begun.

It also will not start on a car shuffling about looking for you: it has to be properly clear of the pickup as well as having driven the distance. And the driver gets a short window to undo it if we called it wrong and you are not in the car yet — after he uses that, we never start that ride by ourselves again.

A couple of rides never start themselves at all. A ride booked for a later hour will not start itself until its time is close, however near the taxi has parked. And a ride being paid by card does not start until its money is in hand, whatever the car is doing.

Why you might care: the start is what the end of the ride is measured from, and it is what turns the screen from a map of a car coming towards you into a ride in progress. If your screen still says the driver is on his way when you have been moving for several minutes, nothing is wrong with the taxi — it simply has not flipped over yet.

What happens if you never come down?

The driver can cancel, but not instantly: from the moment he presses arrived he cannot cancel for four minutes, and after that he has to say why.

Those four minutes are a floor under your feet. A driver who pulls up and immediately decides he cannot be bothered has to sit there at least that long, which in practice is enough for most people to get downstairs. On a taxi booked for now the three-minute message will have reached you well inside that time. On one booked for a later hour it may not have: his four minutes run from the moment he presses arrived, which he may do while still early, whereas the message to you is counted from the time you booked for. The floor also rests on that press — a driver who never pressed arrived was never held by it, even though you were still told his taxi was outside.

After the four minutes he can cancel, and the reason is not optional: he picks from a short list — the passenger never appeared, could not pay, the address was wrong, changed their mind, or something else he has to type. That reason is recorded against the ride. It is not a formality; it is what stops “cancelled” being a shrug that nobody can look into afterwards.

Once a ride is actually under way the cancel button is shut to him. What he can still do is report that the ride never happened, and that does close the ride and tells you so in as many words. But it is a claim rather than a decision: the money stays exactly where it is until somebody in our office has looked at it. The protection above is about the pickup, which is where the disagreements happen.

What that leaves you with: the ride is cancelled, you are told it has been, and the reason he gave is written on it. You are not left guessing which of you gave up. What happens when a driver cancels sets out what comes next and what happens to money already taken for the ride, and from there booking again is the ordinary booking.

What about Shabbat and the festivals?

No ride can be booked from candle-lighting until Shabbat goes out, or on a holy day of rest — but a ride already on the road when the closing begins is still seen through to the end, arrival messages and all.

That split is worth understanding, because it is not arbitrary. The messages that run on a timer — the chasing-up when a driver is waiting, the reminders, the are-you-still-coming ones — all check the closing before they go, so none of them fires during it. The messages that come off your own taxi’s position, or off the driver’s own buttons, check nothing: if your ride is still running as the closing starts, you will still be told the taxi is a minute away, still be told it has arrived, and still get the total at the end.

In practice that means the three-minute message and the five-minute telephone call are the two that will not reach you on a ride running into the closing. The arrival itself still will.

The closing covers both days of Rosh Hashana, Yom Kippur, the first day of Sukkot, Shemini Atzeret and Simchat Torah, the first and seventh day of Passover, and Shavuot, each from candle-lighting to nightfall. The middle days of Sukkot and Passover are ordinary working days. Open the app during a closing and it tells you so over every screen, in Hebrew with English underneath, along with the time we are back — taxis in Israel is the wider picture if you are new to the week here.

The bottom line

The minute your taxi reaches you is the one where a ride is most easily lost, by both sides, and almost all of it comes down to whether anybody said anything. So two things can tell you, and whichever gets there first is the one you receive, the arrival never being announced to you twice. The driver has a button at the kerb — it only appears on his screen when he is near, only comes alive when he is nearer, and a press from too far away is refused however it was sent — and separately our own side watches where the taxi actually is and tells you it has arrived whether or not he presses. That second one exists because it depends on nobody remembering: a rider could once sit indoors while the car stood outside. One message as the taxi comes close, so you can put your coat on, and one when it is outside. Outside is drawn a little wider than the word suggests, because a telephone’s idea of where it is can be wrong by tens of metres in a street with tall buildings, so the taxi may be a few doors along. On a ride booked ahead, the banner at the top of the live map turns green and reads Your driver is here, with The taxi is waiting outside — head out beneath it, in place of Driver En Route. On a taxi booked for now, expect none of that: those rides have no on-my-way step at all, so the banner stays on Confirmed and the green one never appears however plainly the taxi is outside. Even on a booked-ahead ride it needs the driver to have pressed arrived. So trust the message rather than the banner — the message reaches you either way. Under the map your pickup and destination are written out — glance at the pickup, because a point that was never right is the commonest reason two people end up a street apart — and under those are Call Driver and Message, live once a driver has taken your ride. After that it is a sequence, not a deadline. At three minutes a message says the driver has been waiting, and on the WhatsApp and text-message versions it carries his own telephone number, where we hold one, for one reason: somebody who really is two minutes away can say so and keep the ride. In the app that number is not in the notification — the Call Driver and Message buttons on the live map are what you use instead. At five minutes your telephone rings, showing our usual number with nobody at the other end to talk to: a Hebrew machine voice says its piece, repeats it in fewer words and hangs up, and a voicemail is hung up on rather than talked to, because by then the ride is about to be lost. After a quarter of an hour we stop, and whether to wait on is the driver’s own decision. On a ride booked for a later hour the clock starts at the booked time or when the driver arrives, whichever is later, so a driver parked early is not being kept waiting and you are not chased for it. The right move at three minutes is always the same: tell the driver you are coming, and say if it is a back entrance or a slow lift. Do not cancel and rebook hoping for something faster — you would be giving up a taxi already at your door. The driver cannot simply drive off either: from pressing arrived he cannot cancel for four minutes — that floor rests on his own press, so a driver who never pressed it was never held by it, and on a ride booked ahead he may press it while still early, so his four minutes can run out before the three-minute message has even reached you — and after that he has to pick a reason — no show, could not pay, wrong address, changed their mind, or something he types — which is recorded against the ride. Once the ride is under way the cancel button is shut to him, though he can still report that the ride never happened, which closes it and tells you so while the money waits for our office to look at it. The ride starts when he starts it, or by itself once the taxi has been at the pickup and has then driven a couple of hundred metres of road and is well clear of it; road driven rather than straight-line distance, because a car leaving a car park or an airport terminal can drive a long way and still be close to the door. He gets a short window to undo that if you are not aboard. A ride booked for later will not start itself until its time is close, however near the taxi has parked, and a card ride does not start until its money is in hand. If your screen still says the driver is on his way while you are moving, nothing is wrong. None of this depends on having the app: a WhatsApp rider is told in the same chat, and somebody who rang 02-376-7000 gets plain text messages to that number, with the driver’s number in the three-minute one, while the five-minute call rings that same number. An app rider whose notification did not reach the telephone gets a plain text message instead on the messages where silence costs the taxi — with one gap worth knowing, that the arrival sent by the driver’s own button goes as a notification and nothing else. The notification itself is in Hebrew, as most live ride messages are; the English is on the screens — the live map and your rides list. And on Shabbat and every holy day of rest, from candle-lighting to nightfall, nothing new is booked, so the three-minute message and the five-minute call do not go. A ride already on the road is still seen through: you will still be told the taxi is a minute away, still be told it is outside, and still get the total at the end.

Frequently asked questions

How will I know my taxi has arrived?
By a message, and you get it whether or not the driver presses anything. He has an arrived button at the kerb, and separately our side watches the taxi’s own position and says it is outside by itself. Whichever gets there first is the one you receive, so the arrival is never announced to you twice. When it came from our watch on the position and the notification did not reach your telephone, a plain text message goes to the number on the booking instead. The one gap is the arrival sent by the driver’s own button, which goes as a notification and nothing else — so keep notifications on.
How long does a Hello Taxi driver wait?
At least four minutes once he has pressed arrived, because he is not allowed to cancel before then. Beyond that there is no stated number of minutes. What there is: a message at three minutes saying he has been waiting, with his telephone number, where we hold one, on the WhatsApp and text-message versions; a short telephone call at five minutes, a Hebrew machine voice that says its piece, repeats it in fewer words and hangs up; and nothing more from us after a quarter of an hour, when it becomes the driver’s own decision whether to wait on.
I am two minutes away — how do I keep the taxi?
Tell the driver. In the app use the Call Driver and Message buttons on the live map; on WhatsApp or by text message his own number comes with the three-minute message, so you can ring him from it. A driver who has been told you are coming almost always waits. Do not cancel and rebook hoping it will be faster; you would be giving up a taxi that is already at your door.
Can the driver cancel the moment he arrives?
No. From pressing arrived he cannot cancel for four minutes, and after that he has to give a reason from a short list — no show, could not pay, wrong address, changed their mind, or something he types himself — which is recorded against the ride. Once the ride is under way the cancel button is shut to him; he can still report that the ride never happened, which closes it and tells you so, but the money stays where it is until our office has looked at it.
Does the waiting clock start early on a ride booked for later?
No. It starts at the time you booked for, or when the driver arrives, whichever is later. A driver who parks at your door ten minutes before the booked time is not being kept waiting, and you are not chased for those minutes.
When does the ride officially start?
When the driver starts it, or by itself once the taxi has been at the pickup and then driven a couple of hundred metres of road and is properly clear of it. Road driven is used rather than distance from the door, because a car leaving a car park or an airport terminal can drive a long way and still be close as the crow flies. A card ride does not start until its money is in hand, and a ride booked for a later hour will not start itself until its time is close, however near the taxi has parked.
I booked by telephone and have no app — will I still be told?
Yes. The arrival message and the three-minute message reach you as ordinary text messages to the number you rang from, and that second one carries the driver’s number where we hold one. The five-minute call rings that same number. What you do not get is the live map, so his number is how you reach him.
The screen still says my driver is on the way and I am already in the taxi. Is something wrong?
No. The ride has not flipped over to being under way yet, which happens on the driver’s own start or once the taxi has driven far enough from the pickup. The taxi, the driver and the fare are all unaffected.

Sources

  1. Hello Taxi code check, 11 November 2026: the moment the taxi arrives — that two separate things tell the rider, the driver’s arrived button and the server watching the taxi’s own position and saying so without him pressing, and that whichever gets there first claims the message so two are never sent; that one message goes as the taxi comes close and another when it is outside, and that the distance is drawn deliberately wide because a telephone’s position is routinely wrong by tens of metres in a street with tall buildings; that the driver’s button only appears near the pickup, only unlocks nearer still, and that a press arriving from too far away is refused on the server; that the green "Your driver is here" banner on the tracking screen also needs the ride to have been moved along to the driver-on-the-way state, which only the driver’s own “on my way” press sets and which a ride booked for now never reaches at all, so that banner never appears on an ordinary now booking; that the call and message buttons for the driver are available once a driver has taken the ride, with the call button saying so when no number is held for him; that after three minutes a message says the driver has been waiting and carries his telephone number, where one is held for him, on the WhatsApp and text-message versions, that after five minutes the telephone rings with a short recording, and that after a quarter of an hour nothing more comes from us; that the clock starts at the later of the driver arriving and the time booked; that the driver cannot cancel for four minutes from the press and must then pick a reason from a short list, and that a ride already under way is not his to cancel; that the ride starts by itself only after the taxi has been at the pickup and then driven two hundred metres of road and moved clear of it, that road driven was chosen over a straight line because of car parks and airport terminals, that the driver has a short window to undo such a start, that a ride booked ahead does not start long before its time and that a card ride does not start before its money is secured; that the door used to tell the rider is decided by how the ride was booked, so a telephone rider gets text messages and a WhatsApp rider is told in that same chat; that a text message follows the arrival notification only when that notification did not reach the telephone, and only on the path driven by the taxi’s position, the driver’s own button sending an app rider a notification and nothing else; and that the waiting sweep does not run on Shabbat while the messages that come off the taxi’s position check the closing not at all.
  2. Hello Taxi code check, 11 November 2026: the Shabbat and festival closing — that it runs from candle-lighting until Shabbat goes out and covers each of the holy days of rest listed on file here, and that the middle days of Sukkot and Passover are ordinary working days; that during the closing a "closed" notice sits over every screen a passenger can open, naming the reason and the time we reopen, Hebrew above and English under it; that the rider waiting sweep does not run at all on Shabbat, so the three-minute message and the five-minute call do not go out; and that the messages which come off the taxi’s own position or off the driver’s buttons check the closing not at all, so a ride already on the road still receives "the taxi is a minute away", "the taxi is here" and the total at the end.
  3. The facts checked on 16 and 17 September 2026 and kept on file here: that the meter sets the final amount and the driver enters it at the end of the ride; that a ride is booked in the app, on WhatsApp on 053-900-0023 or on the telephone line 02-376-7000 from any handset including a kosher one with no internet; that only approved drivers are listed; that payment is cash to the driver or by card; and that the service is closed on Shabbat from candle-lighting until Shabbat goes out and on every holy day of rest — both days of Rosh Hashana, Yom Kippur, the first day of Sukkot, Shemini Atzeret and Simchat Torah, the first and seventh day of Passover, and Shavuot — with the middle days of Sukkot and Passover open.

Book a taxi by city