How-to
How to Find Out Why Walk-in Customers Do Not Buy
Most retailers can say how many walk-ins did not buy. Very few can say why, beyond the three guesses everyone offers: price, stock, competition. The real reasons are said aloud at the counter, in the customer's words, and lost the moment they walk out. This guide explains why the usual sources are unreliable, what to track, and what changes when the objection is captured from the conversation itself.
Why the usual lost-reason data is wrong
- The CRM lost-reason field is filled in by the advisor after the customer leaves, from a drop-down, and 'price' is the default that ends the conversation with the manager.
- Exit surveys reach the few customers willing to stop, who are not the ones who left annoyed.
- Managers hear about the objections that were escalated to them, which are the loud ones, not the frequent ones.
- None of these keep the customer's actual words, so the same objection is filed under three different labels in three stores.
What to track
- Objection mix by store and by week, in the customer's own phrasing, grouped into themes: delivery timeline, on-road or effective price, variant or colour availability, EMI fit, competitor comparison, trust in after-sales.
- Which objections were answered and which ended the conversation. An objection with a good answer that advisors are not using is a coaching problem; one without an answer is a head-office problem.
- The rise of a new objection. A delivery-timeline objection climbing for one model is a supply signal weeks before it shows in bookings.
- Objections in converted conversations. The customer who raised the EMI and still bought tells you the answer that works.
What changes when the reason is heard, not guessed
Once consented conversations are captured, the lost-reason report is no longer a drop-down. It is a ranked list of what customers said, by store, with the line behind each entry. Pricing sees which objection is really about price and which is about the way the price was explained. Supply sees the model whose delivery date is costing sales. Training sees the objection that has a known answer nobody is using.
Customers stay anonymous in every report unless they gave a number for follow-up. What travels is the reason, not the person.
On the floor
A dealer group's lost-reason field says price for seventy percent of lost enquiries. The conversations say something else: for one model, the delivery timeline has overtaken price as the top objection for two months, and customers say it in nearly the same words. Supply is told in week one instead of at the quarter review, and the advisors who answer the objection with a committed date in writing keep customers at twice the rate of those who do not.
Frequently asked questions
Do customers state their real objection out loud?
More often than the CRM suggests. They name a delivery date, a rival price, a colour, an EMI amount. The 'I will think about it' at the end usually follows a specific objection earlier in the conversation.
How is this different from an NPS survey?
NPS asks a customer to rate the visit later. This captures what they said during the visit, unprompted, including from the majority who never answer a survey.
Can objections be fixed centrally?
Some can: a supply date, a price explanation, a trained answer. Others are local. The report tells you which is which by showing whether the objection is everywhere or in one store.
Related reading
Where Borentis applies this
- Objection Intelligence: The reason they did not buy, in their own words.
- Walk-in Recovery: The customer who left is still yours.
- Unmet Demand Signals: Demand for what you did not have.
Borentis is the Agentic Operating System for Customer Interactions, built for Indian retail floors: consented one-tap capture on the advisor's phone, every conversation scored against your playbook with the evidence behind every number, leads created when a number is heard, and coaching from your own best conversations.