Lost sales
Customer Objection Analytics: Turning Retail Objections Into Answers at Scale
Customer objection analytics is the counting of objections raised in real sales conversations: which ones come up, how often, in which stores, whether the advisor answered them, and whether the customer stayed in the conversation afterwards. The purpose is not a report. It is to find, for each objection, the answer somewhere in the network that keeps customers, and to get that answer to every advisor before the next customer raises it. This guide sets out the matrix, the numbers to read in it, and how the answer library is built and kept alive.
What an objection is, for counting purposes
An objection is a reason not to buy, raised while the customer is still talking. "EMI 36 months ka hi hai kya?" is an objection. "Sochke batata hoon" on the way out is not; it is what remains when an objection was not answered. The eight reasons customers give for not buying are the taxonomy at /learn/why-customers-dont-buy-in-retail-stores/; sales objection analysis uses the same buckets and adds two things: was it answered, and did the conversation continue.
Those two things are the whole difference between an objection report and objection analytics. A list of objections tells the retailer what customers worry about, which they mostly knew. The answer rate and the hold rate tell them which worries the floor can already handle and which ones are ending sales.
The objection matrix, per 100 non-buying conversations
Illustrative numbers for a durables network over one month. Raised is how many of 100 non-buying conversations contained the objection. Answered is how many of those the advisor addressed with a substantive reply. Held is how many stayed in the conversation to the offer or the number after the answer. Best answer is where the network's highest hold rate on that objection was found.
| Objection | Raised | Answered | Held after answer | Best answer found in |
|---|---|---|---|---|
| EMI tenure or down payment | 34 | 22 | 14 | Store 07, one advisor: quotes total cost across two tenures |
| Rival's price on the same feature | 27 | 15 | 6 | Store 12: names delivery, install and exchange in the comparison |
| Online price lower | 21 | 17 | 9 | Store 03: offers price match with same-day installation |
| Exchange value too low | 18 | 12 | 8 | Store 07: explains the valuation and the bonus separately |
| Warranty or service doubt | 14 | 9 | 7 | Store 19: names the service centre and response time |
| Variant not in stock | 12 | 11 | 5 | Store 03: delivery date on the spot, deposit taken |
| Need to ask spouse or family | 31 | 8 | 3 | Store 12: sends the comparison to show at home, books the family demo |
Reading the matrix
- The family objection is raised almost as often as EMI and answered a quarter as often. Advisors do not treat it as an objection; they treat it as the end. Store 12's answer, something to show at home and a booked demo, is the network's biggest single opportunity.
- The rival's price is answered in barely half the cases and held in a fifth. That is a competitor defence gap, not a pricing gap, until the network's best answer has been tried everywhere.
- Variant not in stock is answered nearly always and held rarely, because the answer is an apology. Store 03's answer converts the apology into a date and a deposit.
- EMI is the most raised and the best handled, and it still loses 20 of 34. One advisor in Store 07 holds most of the customers who raise it. That advisor's line is the coaching material for the month.
Building the answer library
- For each of the top seven objections, pull the ten conversations with the highest hold rate. Read the advisor's answer as spoken, in Hinglish if that is how it was said.
- Choose one or two answers per objection that a different advisor could plausibly say. Keep the words; strip the store-specific detail.
- Check each answer against policy. The price match in Store 03 needs to be one the network can honour, or it is a complaint, not an answer.
- Put the answers where the advisor is: the coaching session, the simulator scenario, the queryable script in the app. BorentisAcademy holds the script as something to ask; BorentisTrainer answers in the top trainer's words. Neither talks to the customer; both talk to the advisor.
- Measure the hold rate again a month later, per objection, per store. An answer that did not raise the hold rate where it was introduced is not the network's answer.
Keeping it current
Objections change with the calendar. A scheme change moves the EMI objection for a fortnight while advisors learn the new terms. A rival's festive launch creates a new comparison objection overnight, with the rival's exact claim, and the answer library is silent on it until someone on some floor finds the reply. Weekly reading of the matrix catches the new objection in its first week, and the store with the first good answer is visible by the second.
Unanswered objections that repeat across the network are not a coaching problem. A warranty doubt that no advisor can answer is a policy or a brochure problem, and a stock objection in every store is a supply problem. The matrix separates what the trainer can fix from what the category team must.
The honest limits
Objection analytics counts what was said in consented, recorded conversations. A store recording half its walk-ins reports half its objections, and the half recorded may skew towards the conversations advisors were confident about. Coverage is reported next to every row for this reason.
The best answer found in one store worked with that store's customers, in that advisor's voice. It is a starting point for the others, not a script, which is why it goes into a coaching session and a practice scenario rather than a memo. The session method is at /learn/sales-conversation-coaching-for-retail-advisors/.
Frequently asked questions
What is objection analytics in sales?
The counting of objections raised in real sales conversations by type, store and week, together with whether each was answered and whether the customer stayed in the conversation. For stores, it needs the face-to-face conversation captured with consent; for call centres it is done from call recordings.
What are the most common customer objections in Indian retail?
By frequency in measured floor conversations: EMI or finance terms, the need to consult a spouse or family, a rival's price on the same feature, a lower online price, exchange value, warranty or service doubt, and the variant not in stock. The order shifts by category and by store.
How do you handle objections better across many stores?
Find the answer that already works in one store, check it against policy, put it in coaching and practice, and re-measure the hold rate. Networks that write objection answers centrally without checking them against real hold rates get answers advisors do not use.
Is the family objection really answerable?
Often. It is answered by giving the customer something to show at home, taking the number and a date, and offering the family a demo slot. The follow-up that refers to what they liked is at /learn/how-to-follow-up-with-a-customer-who-walked-out-without-buying/.
Related reading
- Why customers don't buy in retail stores
- Customer walkout analytics
- BorentisAcademy, the queryable script
- Sales conversation coaching for retail advisors
Where Borentis applies this
- Objection Intelligence: The reason they did not buy, in their own words.
- Competitor Defence: Hear the rival the moment your customer names them.
- Coaching from Best Conversations: Your best advisor, teaching everyone.
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.