How to Find Customer Objections

Does she ... or doesn't she? Only her hairdresser knows for sure!

Shirley Polykoff's 1957 Miss Clairol headline answered a particular worry: people might discover that a woman colored her hair. Dyeing it carried a stigma, Martin Mayer reported in The Saturday Evening Post in 1965.

Life magazine's executive committee had a different objection: it found the ad suggestive. After the magazine's secretaries reviewed it, the committee apologized and ran it.

The headline offered discretion to the buyer. The staff review addressed the committee's reading of the ad. Before writing an answer, identify whose doubt you're trying to settle.

Euan, an invented tutor considering the fictional Pebblewick Booking tool, points at a screenshot from an earlier calendar move. Tuesday's lesson appears twice. He wants to catch that error before students see it.

He has also mentioned the price, and you've drafted a discount. Ask what he needs to inspect before offering it: a lower bill won't show him whether Tuesday's lesson appears correctly.

Separate a doubt from a hard limit

A question about whether recurring lessons import correctly may be answerable with a demonstration. A requirement the product doesn't support may rule it out for him.

Take the screenshot to the product specialist and ask for the same recurring-lesson case in the new tool. Can Euan review the imported entries before publication? Keep the question open until you can show him the relevant screen.

Timing matters too. If Euan has no time to review a move this term, a clear demonstration won't create that time. Keep his constraint in your notes instead of treating hesitation as a wording problem.

Pebblewick Booking inquiries

Potentially answerable uncertainty

• Will a recurring lesson appear twice after import?
• Can I inspect the result before students see it?

Possible fit or timing limit

• I need payment records imported, and this tool does not do that.
• I have no time available to check a move this term.

Sales calls reveal the decision in motion

Ask Euan, "What did you compare when Tuesday's lesson appeared twice?" He opens the old calendar beside the screenshot and traces the two entries he checked before letting students see the changed schedule.

He says, "Tuesday's lesson showed up twice last time. Can I check the imported calendar before students see it?"

Keep those words beside the screenshot, with the old entries attached for the demonstration. Your interpretation, "concerned about migration," belongs in a separate field.

The voice-of-customer lesson helps you record that context. If Euan later buys, write the decision next to the question and the answer. Then ask him why he decided, instead of assuming your answer did it.

Support, refunds, and FAQ logs show different slices

Other records show where a concern turns up. An import-support question describes someone trying the move; a refund note concerns a purchase someone wants reversed. A prospective buyer who leaves without contacting you won't appear in those records.

Nielsen Norman Group recommends looking at existing organizational data when you plan customer-experience research. It treats those records as clues for shaping what to ask next. Euan's Tuesday lesson gives you one clue to follow through them.

A line in the FAQ may be the team's guess about what people ask. For "Will my lessons move correctly?", find the original question and check whether it concerned recurring lessons. Carry that detail into the answer so it addresses the same import case.

Ask about the checks people made

An interview can reach what the walkthrough can't show. Ask how many recurring lessons Euan runs and who besides him would notice a wrong time.

GOV.UK's interview guidance favors open questions about real examples. So ask about another week when a schedule change went wrong, before you mention any preview feature. Given room to explain, he may name a requirement you never thought of.

When someone stays with their current tool, ask what makes staying workable. The competitor research lesson counts that workaround among the alternatives to investigate.

For Euan's walkthrough, give the specialist the recorded Tuesday comparison. Ask them to demonstrate his case, including any exceptions that need checking by hand.

Keep hopes apart from constraints too. The customer-desires lesson helps you explore what a better scheduling week would look like, without treating that scene as evidence for your product.

Build an objection ledger with an owner

Now write a short record for the product specialist. It holds Euan's account and the question the tool has to answer. Leave room for the answer and the demonstration behind it.

The specialist opens a preview calendar. Recurring lessons can be inspected there, though exceptions still need manual review and payment history stays behind. Euan asks about those payment records before he moves on.

The record can now distinguish a demonstrated preview from an unresolved requirement. Assign the payment-history question to the specialist: Euan needs to decide whether leaving those records behind rules out the move. Keep his answer attached to that limit.

Objection record O07

Determine whether Pebblewick's preview answers Euan's question about the duplicated lesson.

Context and exact customer language

Interpretation and answer needed

Owner and demonstrated answer

Context and exact customer language

• Context: a solo tutor considering a switch before half-term.
• Source: the invented sales conversation and screenshot in this exercise.
• Euan: 'Tuesday's lesson showed up twice last time. Can I check the imported calendar before students see it?'

Interpretation and answer needed

• Possible concern: a student could see the wrong lesson time.
• Answer to check: whether the imported calendar can be reviewed before it goes live.

Owner and demonstrated answer

• Product specialist: preview demonstrated; exceptions need manual review.
• Open: ask Euan whether leaving payment history behind rules out the move.
• Page location: beside the invitation to start an import.

The ledger preserves Euan's words alongside the interpretation, answer owner, evidence and intended page location.

What does a price objection mean?

Go back to the price remark. Ask which costs Euan was counting, and write his answer in his own terms. The subscription fee and the hours spent checking imported lessons are separate things to ask about.

Keep the subscription budget in its own field. The duplicated lesson gives you a reason to investigate review work, and Euan may still have a firm limit on spending. Resolving one concern leaves the other to be checked.

Ask, "If the preview lets you check those lessons, would the subscription still exceed your budget?" Euan replies, "The fee is within my budget. I'm unsure how much time checking the move will take."

Record that answer beside the price remark. If he had said the fee exceeded his budget, you'd retain a firm price limit even after a successful demonstration. Here, his answer gives you a reason to set the discount draft aside and explain the review work.

"Save on your switch" leaves that work unexplained. Replace it with "Inspect your imported lessons before students see the calendar," and put the manual checks alongside it. Euan can then judge what the move requires within the budget he has confirmed.

Keep the stated budget in the record even when another concern turns up.

Questions for the cost discussion

Ask Euan which costs he included when comparing tools. Record his subscription budget separately from the time he has for a migration. Then ask what would make staying with the current calendar workable this term.

Match the answer to the doubt

Draft an answer Euan could check against the demonstration he just saw. Put the manual review and the payment-history limit in the public copy.

Migration reassurance the reader can check

Reassurance without an answer

Switch with total confidence. It's effortless.

An answer tied to a process

Import into a preview calendar first. Check recurring lessons and review exceptions manually before publishing. Payment history stays in your old tool.

Place this explanation beside the invitation to start an import.

The landing-page lesson on handling objections covers where answers like this go. I'd put the preview explanation right next to the button that starts a migration, where it can shape the decision to begin.

Then show the draft to a tutor who hasn't seen it, and ask what they'd review before publishing an imported calendar. Listen for the exception checks.

Ask where their payment records would be after the move. If they expect those records in Pebblewick, point to the passage that created that expectation and revise it before showing the page again.

Write the unresolved question

Pick one unresolved objection from your own material. Find the original account behind its shorthand label, and write the question an answer would have to settle. The Research collection has methods for following it up.

Put the proposed answer beside the account and mark the part still waiting on the buyer. For Euan, the preview can answer where he checks Tuesday's entries; the payment-history limit still needs his decision.

Leave the new opening beside the import limits and turn the preview to Tuesday. Euan pulls the old calendar closer and starts comparing the entries, looking for the lesson that appeared twice last time.