Field Service CRM for Indian AC, RO, and Appliance Brands

The three tensions in Indian field service

Customers in Indian metros expect appliance service within 24 hours. Technicians in those same metros lose an average of 90 minutes per day to wasted trips — addresses that turn out to be wrong, customers who did not answer the door, and tickets that needed a different skill set. Brand owners write off 6-12% of warranty claims because they cannot prove the failure was a genuine product issue rather than user negligence. A field-service CRM has to address all three of these without making any one of them worse.

What a service ticket actually needs

A field-service ticket is not a customer-support ticket. The difference matters. A support ticket has a customer and a question. A service ticket has a customer, an address with a pincode, a specific product (with serial number, purchase date, and warranty status), a symptom in the customer's own words, a likely diagnosis (filled by the call-centre agent), an assigned technician, a scheduled time window, the technician's drive-time estimate, the spare parts that may be required, and the photo proof the technician will eventually upload. Tickets without all eleven fields produce wasted trips.

• Pincode-anchored address (not free-text 'Bangalore'); enables geo-routing
• Product serial number — required, not optional; drives warranty lookup
• Symptom in customer voice + structured diagnosis category
• Time window (10am-1pm, 1pm-4pm) — not exact appointments customers cannot keep
• Drive-time estimate from technician's previous ticket — surfaces routing inefficiency
• Photo proofs at four points: arrival, before-fix, after-fix, customer-signature

Tier-2/Tier-3 technician routing logic

Tier-1 metros (Mumbai, Delhi, Bengaluru, Chennai, Hyderabad, Kolkata, Pune) operate with dense technician networks and 4-hour resolution targets. Tier-2 cities (Indore, Coimbatore, Lucknow, Jaipur, Bhubaneswar) have one or two technicians covering a 20km radius and 24-hour targets. Tier-3 deployments rely on hub-and-spoke models with a regional technician travelling on Mondays and Thursdays only. A routing engine that does not differentiate between these three modes either over-promises in Tier-3 or under-utilizes in Tier-1.

Warranty fraud — three signals worth tracking

Brands that operate in India for any length of time encounter three forms of warranty fraud: serial-number swapping (customer claims warranty on a product they did not buy), forced-failure claims (the product was damaged through misuse, not defect), and double-claim attempts across multiple service partners. A CRM that records every claim against the serial number, photographs the failure mode, and flags claim-frequency outliers reduces fraud write-offs by 40-60% within two quarters.

Spare-part inventory at the technician level

Most appliance brands track spare-part inventory at the central warehouse and the regional service centre. A few track it at the technician level. The ones that track at the technician level have 12-18% higher first-visit resolution rates because the dispatch system asks 'does the assigned technician already carry this part?' before dispatching. A CRM that closes this loop pays for itself in technician hours saved, never mind customer satisfaction.