From the first enquiry to the fault the vehicle reports itself.
A call about a scooter becomes a scored lead and a booked test ride. The deal waits in registration until the VIN is allotted. Months later the vehicle sends a charger fault code, and a case opens before the rider notices — with the bike, the dealer and the purchase already on it. Settl runs sales and after-sales on one customer record, for dealer networks that sell and service connected vehicles.
A sales call that ends as a qualified lead and a booked test ride.
The voice agent asks what a good salesperson asks — how the vehicle will be used, the timeline, what it is being compared against — matches the model the caller half-remembers, and books a doorstep test ride before the call ends. The answers land on the lead, scoring rules grade it, and routing rules send it to the right dealer by distance and load. The same conversation produces the same lead in Settl's CRM or in Salesforce.
A pipeline that ends at the number plate, not the booking.
Inquiry, rep assigned, demo, test ride, quotation, negotiation, booked, RTO and registration, delivered. The registration wait is a stage of its own, because that is where deals really sit for a fortnight: it refuses to open without an allotted VIN and chassis number, and delivery is refused without a plate. Each product carries a floor price no rep may sell below, and every customer's account shows what they have paid and still owe.
The bike reports the fault before the rider does.
Connected vehicles send fault codes, low-battery and charging events, GPS loss. Settl treats the vehicle as a channel: a fault code opens a case with the rider, the bike, the dealer and the warranty already attached, reads the live telemetry, and messages the rider first — on WhatsApp or the companion app — with what it found and what happens next.
- Remote fixes — reset the charger, reboot telematics, push an OTA update, on the rider's consent.
- Roadside assistance — a highway breakdown dispatches RSA from the case, with the rider's live position.
- Service bookings — a pickup or a slot at the nearest service point, with the fault already on the job card.
- Immobilise and release — where the policy allows, from the same case, with the approval on record.
WhatsApp, a tweet and a call about the same bike become one case.
A rider who messages on WhatsApp, posts publicly on X, then phones the service line is one case, matched on phone, handle or VIN, not three tickets for three agents. Public replies wait as drafts for a person; dealer-portal updates are rewritten for the rider; legal and consumer-forum notices are classified and routed, never answered by the AI.
Dealers see their own cases, their own leads, their own load.
Each dealer's open cases and leads sit against its capacity, and the routing rules that point work at it are visible and editable. A dealer-portal update lands on the customer's case and is rewritten for the customer. A test-ride no-show, a completed ride and its outcome, a manual reassignment with its reason — all on the record, with who did it.
From a pile of charging complaints to the firmware version behind them.
The command centre groups open cases by model, fault code and firmware. When charging faults spike on one firmware version, engineering hears it from the data — a cluster, a count and a recommended hold on the rollout — rather than from angry riders a month later. Predicted SLA risk shows which cases to touch today.
Sales line and service line
English, Hindi and Hinglish, about a second to first word, warm transfer to a person on the same call.
Built in, or Salesforce
Leads, accounts, test rides, dealers, products with floor prices, payments; one setting switches the target.
Telemetry and commands
Through an adapter to your vehicle cloud: readings, fault codes, remote diagnostics and commands.
One case per issue
Deduplicated across channels, SLA-predicted, closed with a checklist and a root cause.
On every lead and deal
Where the deal stands, what the customer cares about, the risk, the next step — written from the record.
What a sales manager opens
Rep scorecards, funnel conversion, time in stage, lost reasons, test-ride outcomes, by dealer and product.
Frequently asked
Does Settl work with our dealer network, not just a central team?
Yes. Leads are routed to dealers by distance and load, each dealer sees its own leads, cases and capacity, and dealer-portal updates land on the customer's case. Manual reassignments are recorded with a reason.
Can it connect to our vehicle's telematics?
Through an adapter to your vehicle cloud. Settl reads live readings and fault codes, opens cases from alerts, and sends remote commands — charger reset, telematics reboot, OTA push, immobilise — where your policy allows and the rider consents.
We already run Salesforce. Do we have to switch CRMs?
No. The same connector writes leads, opportunities, test rides and dealer assignments into Salesforce instead of Settl's built-in CRM. Switching is one setting; the conversation produces the same lead either way.
Who approves a goodwill credit or a free service?
Anything that moves money or changes a vehicle's state goes through a policy with a cap. Below it the agent acts; above it a person approves with the case in front of them, and the approval is on the record.
Which languages does the service line speak?
English, Hindi and Hinglish, switching mid-sentence. The same agent answers the sales line and the service line, with different scripts and different tools.