A last-mile logistics company in Delhi NCR came to us running Salesforce. They didn't think Salesforce was right for them. They knew it wasn't. But when management asked why operations weren't being tracked properly, it was the most credible CRM name anyone could put forward. It sounded like a serious answer to a serious problem.
Except Salesforce is built for sales pipelines, and they didn't have a sales pipeline. They had trips.
What was actually happening
The operation itself was simple to describe. A client books pickups. Drivers get assigned. Trips happen. And at some point, someone reconciles what was delivered against what was billed. The distance between “at some point” and “same day” was exactly where the money was leaking.
Inside Salesforce, every trip was a “deal” moving through a pipeline. Wrong stages, wrong fields, wrong reports. So the real coordination moved somewhere else: a WhatsApp group where the ops team and drivers talked all day. Every decision, every exception, every status update lived in that group. Management couldn't see it, and billing had no record of it.
- Billing was running 12–15 days behind operations
- Roughly 12 billing disputes a month over delivery records nobody could verify
- No live view for management of what was going on
- Driver assignment and route coordination with no structure at all
What we designed instead
We didn't write code first. We spent time mapping the operation as it actually ran, which looked nothing like the version configured in Salesforce. Who does what, in what order, what happens when something goes wrong, and what information has to pass between drivers, ops staff and clients.
What came out of that was a purpose-built dispatch CRM whose data model was built around trips instead of pipeline stages:
- Trip creation: Pickup and drop details, client, driver, scheduled time. The ops team could create one in under two minutes.
- Driver status updates: A light web page drivers could open on any phone, no app download, to mark pickup confirmed, in transit and delivered.
- Client delivery confirmation: An SMS link for the client to confirm delivery. That gave us a timestamped record, which is what finally settled billing disputes.
- Management dashboard: Every active trip on one screen, delays flagged, and a daily summary of completed runs with billing-ready data.
- Weekly billing export: Generated automatically from completed trips, already formatted for their accounting software. No manual reconciliation.
What happened three weeks after go-live
The WhatsApp group went quiet. Nobody ordered it shut down. The ops team just stopped needing it, because the system now did everything the group had been doing.
In the first month, billing disputes fell from 12 to 2. The billing cycle went from 12–15 days to 3. The ops manager, who'd been the biggest sceptic, put it best: “the first time we have had an actual record of what happened on any given day.”
The right CRM isn't the most famous one. It's the one that models how you operate, not how some vendor assumed you would.
What this means for other logistics businesses
If you run logistics, dispatch or last-mile delivery on a generic CRM (Salesforce, HubSpot, Zoho) and the real coordination happens on WhatsApp, you're where this company was. The tool itself isn't bad. It just doesn't match the operation.
Switching to a different generic CRM won't fix that. What fixes it is a system built on the real shape of your operation. Trips, not deals. Drivers, not contacts. Delivery confirmations, not pipeline stages.
We've built custom dispatch and logistics software for operations across Delhi NCR, including custom CRMs built around how the business actually operates. If your coordination still runs on WhatsApp, tell us what you're dealing with.