Mapping customer objections: a template based on call recordings
The word “expensive” is found in different conversations. But the answer depends on what the customer compares the price and what prevents him from making a decision.
A good map starts with a questionOne line can mean different obstacles
Short response
The customer objection map is a table of typical buying obstacles: how they sound, in what situation arise, what needs to be clarified and what you can answer on the merits. Gather it in real conversations, saving replicas and timecodes. Check the answers on the current product conditions. Below is a template, four training examples, and a way to update a map without making up statistics.
Contents
Why does the sales department need a map
Ready-made lists of “one hundred answers to expensive” do not know your customers. One person has no budget, the second compares the proposals of different composition, the third expensive time of the team for implementation. The same workpiece can pass by all three.
The card helps the new manager to understand what to clarify and where to get the confirmed information. The manager shows repeated questions to the product: for example, customers do not understand what is included in the tariff or who helps to start work.
In HubSpot Guide to Objections The need to understand the reason for the doubt before the answer is emphasized. For a work card, it is useful to fix this with a separate column “What to clarify”, and not immediately write a refutation.
If you need a general analysis of the conversation – need, promises, mistakes and the next step – use the material about Transcriptions of Calls in Sales. Here the result is already: the base of specific objections for the team.
How to collect the original replicas from calls
Choose one product, segment and clear period. If you mix the first appeals of private customers and negotiations on corporate implementation, the card will become too common. To begin with, take a little batch of conversations and check if it is convenient to fill in the fields.
Take conversations with different outcomes: purchase, next step, pause, rejection. Only successful calls will give too good a picture; only lost ones will not show when the question really managed to clarify.
- Find the moment the client outlined the obstacle, not just asked a reference question.
- Save the replica along with the previous manager's question and the client's response to the clarification.
- Mark the stage of conversation: before the demonstration, after the price, when discussing the launch.
- Write down what happened next. Separately, what you have actually observed is your assessment.
- Remove personal data from the study copy. Leave an internal record code and timecode for verification by an authorized colleague.
Don’t write “afraid of change” if the customer only said “go back later.” This is the manager's hypothesis. It may be true, but for the time being the map should remain the question of the cause of the pause.
Objection map template
| The field | What to write |
|---|---|
| Segment and stage | Who solves what task; on what step there was doubt. |
| Precise replica | Client's phrase, conversation code, timecode. |
| Confirmed reason | What the client explained himself. If not explained, “not clarified.” |
| The clarifying question | One question that helps to distinguish the possible causes. |
| Answer on the substance | Confirmed fact, option or fair restriction. |
| Source of response | Tariff, instruction, demonstration or agreed terms with the date of verification. |
| Next step | What is agreed with the client; or a clear refusal without further contact. |
| Observed result | The question was clarified, the demonstration was appointed, the client refused, etc. |
In the final map, combine similar reasons, maintaining several characteristic formulations. You do not need to create a separate card for each “expensive” if the context and obstacle are the same.
Four examples: from replica to response
Below are the fictional dialogues for conditional service. These are examples of conversation logic, not ready promises about the possibilities or conditions of Transkribator.
'Other company is cheaper'
Clarification: “Tell me what composition of work you compare? I want to know if the same outcome goes into the price.”
After the client's response: compare specific positions. If the composition is really the same and you are more expensive, explain only the confirmed differences. Do not invent the shortcomings of the competitor.
Next step: send a consistent comparison of the composition if the client needs it.
'We don't have a person to do this'
Clarification: “What part of the work is difficult: preparation of materials, first launch or further use?”
The answer: show the real order of action and honestly name the participation that will be required from the client. If the service requires a specialist on his part, this restriction cannot be hidden.
Next step: Disassemble one model scenario with a future user if they are ready to connect.
“I need to agree with the leader”
Clarification: “What questions does the supervisor need to close to make a decision?”
The answer: Prepare a short description of the task, result, composition and limitations. Do not promise payback without calculating the customer data.
Next step: pass the material for internal discussion and ask when it is appropriate to return to the conversation.
'We don't plan to buy it'
The answer: Accept the rejection. If the context allows, you can ask once whether the task itself or the current moment is not suitable. If you do not want to discuss further, complete the conversation.
Record in the map: “refusal; the reason is not specified” unless the client has named it. Do not replace this with the phrase “could not be able to squeeze.”
How to turn a table into a working tool
Give each card a short name for the reason: “unclear price composition”, “no resource for launch”, “internal agreement”. Add replica options, but don’t force the manager to read the answer verbatim.
Take one record from the crew. Stop immediately after the objection and ask to suggest a clarifying question. Then listen to the continuation. So it is visible which explanations were guessing, and which confirmed the client himself.
The answer should have an owner: the person who checks it when changing the tariff, functionality or process. Convenient statuses - "checked", "need to clarify", "outdated". An unverified response cannot be given to the client as a fact.
If one reason is repeated, the task may go beyond the script. For example, questions about the composition of the service are a reason to check the tariff page and the commercial offer. Mark this with a separate action for product or marketing.
How to evaluate change without self-deception
Consider how many conversations a certain reason arose, and not how many times the manager said the word “price”. If one client repeated the objection five times, it is one conversation with the obstacle.
Compare similar groups and stages. The increase in the number of demonstrations after the introduction of the card does not in itself prove that it is only in the map: advertising, supply or composition of appeals could change. Save the response change date and the observed result.
- The reason is confirmed by the client or honestly noted by the unknown.
- The answer does not contain invented guarantees, discounts and cases.
- Every fact has a valuable source.
- The next contact is agreed if necessary.
- The team knows where the current version of the card is.
- Refusals are taken into account without attempting to ascribe hidden consent to the client.
Frequently asked questions
Can I start with a ready list of objections?
Yeah, like a draft list to check. Before use, replace the common replicas with your customers’ real-world wording and check each answer on the product.
How is an objection different from the question?
The question requests information. The objection denotes an obstacle to a decision or next step. The same question about the price can play a different role – look at the context and explanation of the client.
Do I need to record every rejection?
For analysis, it is useful to preserve the observed outcome and the given cause. If there is no reason, write. It is not necessary to think about it for the sake of filling the table.
What is Transkribator doing here?
Helps to get the text of the record with timecodes. The selection of objections, the verification of the reasons, the preparation of the answers and the training of the team you perform on this material.
Material for reconciliation of the approach: HubSpot – work with objections. The table and dialogues are created by the editorial office; statistics of other companies are not used.
Collect a map according to customers
Translate call records into text using Transkribator. Save accurate replicas and timecodes to discuss real situations and check the wording of the answers together with the team.
Get the call textCheck the important wording and timecodes for the original record before using the text.