A last-mile logistics company in Delhi NCR came to us running Salesforce. Not because Salesforce was the right tool for them — they knew it was not — but because it was the most credible CRM they could name when management asked why operations were not being tracked properly. Salesforce felt like a serious answer to a serious problem.
The problem was that Salesforce is built for sales pipelines. They did not have a sales pipeline. They had trips.
What was actually happening
The dispatch operation worked like this: a client would book pickups, drivers would be assigned, trips would happen, and someone would eventually reconcile what was delivered against what was billed. The gap between “eventually” and “same day” was where the business was losing money.
In Salesforce, each trip was a “deal” in a pipeline. The pipeline stages were wrong. The fields were wrong. The reporting was wrong. So the actual coordination happened somewhere else: a WhatsApp group where the ops team and drivers communicated in real time. Every decision, every exception, every status update — all in WhatsApp, invisible to management and unrecorded for billing.
- Billing was running 12–15 days behind operations
- Roughly 12 billing disputes per month from delivery records that could not be verified
- No real-time visibility for management into what was actually happening
- Driver assignment and route coordination entirely unstructured
What we designed instead
Before writing a line of code, we spent time mapping the actual operation. Not the operation as described in the Salesforce setup — the operation as it actually ran. Who does what, in what order, when exceptions occur, what information needs to pass between drivers, ops staff, and clients.
The result was a purpose-built dispatch CRM with a data model built around trips, not pipeline stages:
- Trip creation: Pickup and drop details, client, driver assignment, scheduled time — created in under two minutes by the ops team.
- Driver status updates: A lightweight web interface drivers could use on any phone — no app download required — to mark pickup confirmed, in transit, and delivered.
- Client delivery confirmation: A link sent via SMS to the client to confirm delivery, creating a timestamped record that resolved billing disputes.
- Management dashboard: Live view of all active trips, exception flags for delays, and a daily summary of completed runs with billing-ready data.
- Weekly billing export: Pre-formatted for their accounting software, generated automatically from completed trip records — no manual reconciliation.
What happened three weeks after go-live
The WhatsApp group was retired. Not by mandate — by the ops team deciding they did not need it anymore because the system had replaced every function the group served.
Within the first month, billing disputes dropped from 12 per month to 2. The billing cycle shortened from 12–15 days to 3. The ops manager, who had been the most sceptical about the project, described it as “the first time we have had an actual record of what happened on any given day.”
The right CRM is not the most famous one. It is the one that models how you actually operate — not how a vendor assumed you would.
What this means for other logistics businesses
If you are running a logistics, dispatch, or last-mile delivery operation on a generic CRM — Salesforce, HubSpot, Zoho — and the real coordination is happening in WhatsApp, you are in the same position this company was. The tool is not the problem. The mismatch between the tool and the operation is the problem.
The fix is not a different generic CRM. It is a system built around the actual data model of your operation: trips, not deals. Drivers, not contacts. Delivery confirmations, not pipeline stages.
We have built custom dispatch and logistics software for operations across Delhi NCR. If your coordination is still running on WhatsApp, tell us what you are dealing with.