Skip to content
GullySales

Taxi operators · CRM

Keep the rider's details in the office, not in one driver's head.

A CRM for a taxi operator is a simple record of riders, usual pickups and trips so the office can remember them. GullySales works on choosing a tool the dispatcher will really use and setting up the fields that matter for cabs.

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 CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For taxi operators

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

  • “The driver holds the relationship”

    The regular dialysis run or the shop owner's morning trip is known to one driver. When that driver leaves, takes leave or joins another operator, the rider goes with the driver unless the office kept the record.

  • “A shared sheet holds up until two dispatchers edit it together”

    Small fleets start on a shared sheet and it serves for a while. The trouble starts when two dispatchers change it at once or a phone number is typed two ways, and then nobody trusts it.

  • “The useful fields are few”

    For cabs the record needs name, number, usual pickup, usual drop, preferred car, preferred driver and consent to contact. Fields beyond that go unfilled and make the dispatcher stop entering anything.

  • “A record without consent is a risk”

    Messaging a rider who never agreed to hear from you annoys them and may breach the rules on marketing messages. Note the consent at entry and respect a request to stop.

What we do

What we deliver for taxi operators.

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

  1. A rider record built for cabs

    The fields a dispatcher needs and no more, set up in a tool the office will open.

    Result: Every new rider can be entered in a minute at the desk.

  2. Tool choice matched to your office

    A comparison of a shared sheet and a small CRM against how your dispatchers actually work.

    Result: A decision made on your desk's habits, not a feature list.

  3. Entry rules for dispatchers and drivers

    A short guide on what is entered, by whom and at which moment, including consent.

    Result: Records are filled the same way by everyone.

  4. Regular rider tags

    Tags for dialysis, school, shop, hotel and outstation riders so the office can find each group.

    Result: A group of riders can be found when a message is needed.

  5. A clean-up of existing numbers

    Existing contacts from phones, notebooks and sheets merged into one list, with duplicates removed.

    Result: One list instead of five.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

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

Fields worth keeping

The fields a taxi office should hold so a rider belongs to the office and not one driver.

Rider name and the number they use
The dispatcher fills it at the first call. It lets any staff member answer by name and ends the habit of keeping riders in one driver's phone.
Usual pickup place and destination
The dispatcher fills it after the second trip. A rider who goes to the same clinic each time can be offered the booking before they ring.
Preferred driver, if any
The dispatcher fills it from what the rider asks for. It protects a regular rider's trust when a driver is on leave.
Trip type and the car used
The dispatcher fills it per trip. It shows which riders take outstation trips and need a quote and which only want a local cab.
Consent to message
The first caller to give a number is asked once and it is saved. It decides whether the office may send a reminder or a seasonal note.

Who it is for

This is written for these taxi operators.

  • Stand-based taxi operators at railway stations and bus stands
  • Radio and call-centre taxi fleets in a city
  • Small owner-operators with two to ten cabs
  • Outstation-focused taxi operators
  • Taxi associations and cooperatives
  • Operators who also supply cabs to apps and corporates
  • Auto and cab mixed fleet operators in smaller towns
  • Women-only or senior-citizen-focused cab services

Before you decide

When this may not be the right fit.

  • All riders ring one dispatcher who remembers each of them, so a shared record would only copy what is in one head.
  • Drivers will not give you the riders they have personally built up, so the record would begin with a list nobody trusts.

Before you decide

Agree the work. Know how to judge it.

CRM for taxi operators: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

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 taxi operators. Anything missing is noted in the written scope, with who will supply it.

Every phone book in use
Notebooks, sheets and phone contacts that hold riders, even if messy. We merge them. If drivers keep regulars in their own phones, tell us now so you can decide how those riders are shared with the office.
Your rule on who owns a rider
A decision on whether a rider belongs to the company or the driver. It shapes the entry rules. If the question is unsettled, we write a neutral rule for the office and you settle the rest with your drivers. Settle it with the senior drivers present, so the rule is not announced as a surprise on the day the tool goes live and the drivers hear it first from the office.
A dispatcher with an hour to spare
The person who will use the tool must test it with us. If the owner chooses alone, the desk may reject it. Name the dispatcher and arrange cover during the test.
Rider consent wording
A line telling riders that their details are kept to arrange rides. Your adviser should confirm the wording. Without it we limit the stored fields to the ones a ride needs.
A working phone and a data connection
The desk device and the connection the dispatcher actually has. The test must run on them, not on our laptop. If the connection drops out, we choose a tool that copes offline.

How it works

How the CRM 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

    Copy out every phone book in use

    We gather the numbers where they live now: the dispatcher's notebook, drivers' phones, a spreadsheet, the WhatsApp contacts. You tell us which sources you trust and which hold duplicates. What exists afterwards is one raw list of riders with the source of each name, which becomes the material for the clean-up.

  2. 2

    Agree what the dispatcher must see on a call

    We ask the dispatcher what they wish they knew when a number rings: the usual pickup, the car last used, the preferred driver, any complaint. You decide what is fair to store. The output is a short field list built for cabs, with fewer fields than the dispatcher fears and no field nobody will fill. We also ask which detail the dispatcher forgets under pressure, such as the gate number at a housing society, because that is the field worth keeping.

  3. 3

    Try three tools on the real desk

    We set up the same dozen riders in two or three simple tools and let the dispatcher take mock calls in each. You watch which one is quicker on a bad phone connection. The dispatcher chooses, not us. What exists afterwards is a tool picked by the person who must use it all day.

  4. 4

    Load the clean list and test the rules

    We remove duplicates, mark regular riders and import the list. Then we run the entry rules by having a driver report a ride and the dispatcher record it. You confirm who may edit and who may only view. Before launch, we check that two people can use the record at once without overwriting.

  5. 5

    Run the desk on it with us present

    For a shift, the dispatcher uses only the record, with us nearby to fix confusion. Drivers hand ride details to the desk as agreed. You decide what happens when someone skips an entry. Afterwards, we list what slowed the desk and fix those items, so the record becomes quicker than the notebook.

  6. 6

    Compare repeat rides to the starting list

    At the beginning we counted how many riders had booked twice and how many calls came from known numbers. After use, we read the same figures and the entries the dispatcher actually made. You decide whether the tool stays. No growth is promised; the counts show whether the office remembers riders better. We read the entries themselves as well, checking whether the notes are specific enough that a second dispatcher could use them on a night shift.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  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

    Sales process design

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

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    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.

Is a CRM too big for a ten-cab operator?
No. A CRM can be a well-kept sheet or a light tool. The point is one list that outlives any single driver.
Who owns the rider list?
The operator should. Put in writing that rider details are held by the office and not by a driver, and tell drivers so at joining.
What do we do when a driver leaves with the regular riders?
Make it a house rule that riders belong to the office number and that drivers hand over regulars in the record. The cure is a list the office already holds, because a rider who rings the office number will be sent to another driver on leave.
Is a CRM too big for a ten-cab operator?
No, if it is kept small. A ten-cab office needs a list of riders, trips and consent, which a shared sheet or a simple tool holds. The test is whether the dispatcher opens it during a call, so choose the one that fits that desk.
Can drivers add notes after a ride?
Yes, but through the dispatcher or a short form, not by editing the record themselves. A driver's note on the rider, the pickup gate or a complaint is useful. We set one route for it so notes arrive in the same shape. Edit rights stay with the dispatcher so the record does not drift.
What if the tool costs more than we expect?
We name the cost of each option before you choose, using the vendor's current published terms, and we do not choose for you. If none fits the office, a well-built shared sheet with entry rules is a respectable start. You can move later, and we make the first record exportable.
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.
What do you need from us?
Your brief, and a conversation. After that, access to whatever this work touches, such as your website, your accounts or your enquiry record, and time with the people who handle your enquiries.

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.