Skip to content
GullySales

Airport taxi services · Follow up systems

Send the right message at each point in a booking, from confirmation to ride end.

A follow-up system for an airport taxi service is the set of messages and calls that surround a booking: confirmation, reminder, arrival and thanks. GullySales works on writing them, timing them against the flight and assigning who sends each.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of car rental companies at work in India

What follow up systems means

A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.

Last updated 14 Nov 2026.

For airport taxi services

Where it usually goes wrong, and what we would do.

  • “Silence after the quote loses the booking”

    A booker asked the fare, got a number and heard nothing else. A soft nudge asking whether they would like the car held keeps a quote from fading when a competitor answers.

  • “The pre-landing message prevents the missed pickup”

    A message to booker and traveller as the flight departs, with the driver's name and number, means a traveller who switches the phone on at landing already knows where to look.

  • “A delay needs a message too”

    When the flight is late, tell the booker the driver is still waiting and what the rule is. Silence sounds like abandonment, and the argument starts before the ride does.

  • “The ride-end message plants the next booking”

    A thank-you with the saved number and a review link, sent after the drop, turns one transfer into the contact the traveller keeps.

What we do

What we deliver for airport taxi services.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. A message ladder for each booking

    Written messages for quote, confirmation, departure, landing, delay and ride end.

    Result: A message exists for every stage of a booking.

  2. Flight-linked reminders

    A routine for the desk to check the flight status and send the pickup note to both phones.

    Result: Booker and traveller both receive the driver's details before landing.

  3. A quote nudge

    A polite follow-up for unanswered quotes, with a stop rule so nobody is chased endlessly.

    Result: Unanswered quotes get one clear follow-up.

  4. Delay handling script

    Wording for explaining waiting, rebooking and charges in a calm voice.

    Result: The desk has one script for late flights.

  5. Ownership chart

    A written list of who sends which message at which time.

    Result: Each message has a named sender.

How the result is measured

  • Follow-up completion rate
  • Average number of follow-ups before close
  • Enquiries closed after repeat follow-up

Recorded as a baseline before work starts, so every later report has an honest comparison.

What to capture or send

Send a message at each moment of an airport booking, from quote to ride end.

Quote sent, no reply
A short nudge with the fare method and a question: should the car be held? Do not repeat the whole quote. The booker may have asked another operator, and a clear line gets an answer.
Booking confirmed
Send the driver's name, the car number, the pickup point and the number to call, to both booker and traveller. This is the message that gets forwarded and screenshotted.
Day before landing
Ask the booker to confirm the flight number is unchanged. A changed flight is the main reason a driver stands at the wrong time.
Flight delayed
Tell the passenger the driver has been informed and is waiting. This message is what stops the later argument about waiting charges, so say it before they ask.
Ride ended
Thank them, ask for a review while the pickup is fresh, and ask who else in the office flies the same route. One request, not two.

Who it is for

This is written for these airport taxi services.

  • Fixed-fare airport transfer operators
  • Hotel-linked airport pickup vendors
  • Corporate airport transfer suppliers
  • Chauffeur-driven airport car services with premium sedans
  • Shared airport cab and shuttle operators
  • Airport and railway station dual-service taxi operators
  • Night-shift and early morning specialists
  • Operators serving several airports in one region

Before you decide

When this may not be the right fit.

  • No one owns the reply when a booker answers a message, so a sequence would send messages that go unanswered.
  • Your drivers do not tell the desk when a flight is late, so the delay message would never have anything to say.
  • You have not decided your waiting rule, and a delay message would raise it before you can explain it.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for airport taxi services: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.

Make the scope clear

Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.

Check the work in use

Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.

Know when to change course

If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from airport taxi services. Anything missing is noted in the written scope, with who will supply it.

A sample of bookings that did not confirm
Bring a short list of enquiries where the booker went quiet. Notes from the desk or chat screenshots are fine. Without them, the quote nudge is written from guesswork, and the first messages may miss the real reason people stopped. Even five or six examples show where the silence begins, and chat screenshots with names covered are enough.
The messages your desk sends today
Send us what the desk already writes, even if it is only a confirmation. We improve what works and drop what confuses. Without it, we start from blank and the tone may not match your voice. Send the confirmation, the pickup note and any thanks, even if they are plain, so we improve what the desk already says.
A way to learn of delayed flights
Tell us how the desk or the driver learns that a flight is late, and who informs the booker. A plain description is enough. Without it, we cannot write a delay script that the desk can actually follow. If no method exists, we write the delay message after talking to the driver supervisor, but nothing goes out until the desk agrees to do it.
Names for each message owner
List who sends the confirmation, the reminder, the arrival note and the delay message, with a backup for nights. Without names, each message waits for someone to think of it. Include relief and night staff, with a backup for each message, so that a delay at the small hours is still announced by a person who knows the facts.
A limit on messages for one ride
Tell us how many messages feel right to you for one ride, including the thanks. Your instinct is the guide. Without a line, we begin with the smallest set and add one only if the desk asks. One confirmation, one pickup note and one thanks is a reasonable start, and the booker's reply ends the sequence.

How it works

How the follow up systems work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Read bookings that went quiet after a quote

    We take a sample of recent enquiries where the booker asked about a fare and then said nothing. You tell us what you think happened. The pattern in these chats, not a template, decides which messages we build and where in the booking they sit. Chats are read in the order they happened, so the moment of silence is easy to spot.

  2. 2

    Lay out the messages around one booking

    We list every message a booker might receive from the first reply to the ride-end thanks: confirmation, a reminder, the arrival note and a delay message. You strike out the ones that feel intrusive. The remaining set is the message ladder for that booking type. The ladder is written on one page that the whole desk can read at a glance.

  3. 3

    Tie each message to the flight

    We link the timing of each message to the flight and the pickup, not to the calendar, so a late flight moves the reminder. You decide who updates the expected arrival. Messages that go out at the wrong moment are worse than none. A delay moves the reminder with it, and the new pickup time is confirmed to the booker.

  4. 4

    Write the words in your desk's voice

    We draft each message in short, calm sentences that carry the driver's name, the car number and the pickup point. You read them aloud. Anything that sounds like an advertisement, or promises more than the desk can do, is rewritten. We add the pickup point in words, such as the gate number or the pillar where the car waits.

  5. 5

    Agree who sends the delay message

    We decide whether the driver or the desk sends the delay message and what the backup is when the first person is busy. You approve the chart. When an owner is named for each message, the booker hears from someone and not from nobody. The chart is printed for the desk and pinned in the shared inbox so nobody has to ask.

  6. 6

    Test on live bookings and read the replies

    The desk runs the ladder on real bookings while we read how bookers reply. We compare confirmed rides, repeat bookings and lapsed quotes with the figures kept before the routine started. You see what worked and change the rest. No result is promised. Messages that confuse the booker are reworded before the next ride, and one reply ends a nudge.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 2, qualification. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Can these messages be automated?
Some can, such as confirmation and review requests, using the WhatsApp Business tools. Flight-dependent messages still need a person to check the status. Check the platform's current rules on automated messages.
When does a follow-up become too much?
Send what moves the booking forward and stop there. Each message carries new information, such as a name, a time or a change.
Should every booking get the same set of messages?
No. A one-off booker needs the confirmation and the day-before check. A corporate desk needs fewer messages and a clear billing note. A frequent flyer wants almost nothing. Tag the type at booking so the right set goes out.
Who sends the delay message, the driver or the desk?
The desk sends it, from a saved reply, once the driver reports the delay. A driver on the road should not be typing. The desk also keeps a record, which settles a later dispute about when the passenger was told.
Can any of these messages go out automatically?
Some can, such as a confirmation after the booking and a thanks after the ride, if the tool you choose supports it and the platform's current rules allow it. The delay message and the arrival note should come from a person, since only a person knows the facts. We mark which messages are automatic. Confirmation and thanks can be automatic if your tool and the platform's current rules allow, but the delay and arrival notes need a person, because only a person knows the facts. We mark each message as automatic or personal on the ladder, so the desk is never in doubt.
Who follows up when the booking came through a hotel desk?
The hotel desk is the booker, so confirmation goes to the desk first, and the traveller's pickup note goes to the guest only if the hotel agrees. Record the hotel as a source and name one contact there. The desk then knows whom to thank after the ride, and whom to tell if the flight changes. Keep these messages short and factual, because a front office handles a stack of such notes in a shift. The hotel's own policy on guest messages decides what you may send.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.