Insights

Correct Answer, Wrong Customer? The Applicability Gap | Figsite

The fastest answer is not always the most helpful answer. Sometimes superior customer care begins with one more question.

A customer calls your business and asks:

“Is this covered under warranty?”

Your employee checks the current warranty policy.

Five years.

Simple enough.

They tell the customer:

“Yes. You’re covered.”

The answer came from a real policy.

The policy is current.

Nothing was invented.

There is only one problem.

The customer’s product was purchased under the previous warranty.

The employee did not lie.

The company did not have an outdated policy.

The answer itself was not false.

It simply did not apply to this customer.

And that distinction can damage trust almost as quickly as an answer that was completely wrong.

A trustworthy answer needs more than accuracy

Businesses spend a great deal of effort trying to make information accurate.

They should.

But accuracy alone does not always produce the right customer answer.

A statement can be completely true and still be wrong for a particular:

  • customer;
  • product;
  • model;
  • revision;
  • location;
  • purchase date;
  • installation;
  • contract;
  • application;
  • service condition.

That creates a business problem many owners do not have a name for.

At Figsite, we think about it as an:

The Answer Applicability Gap

The Answer Applicability Gap is the distance between having a generally correct answer and knowing whether that answer applies to this customer’s exact situation.

Consider these statements:

“This accessory is compatible.”

True—for Revision B.

Wrong—for the customer who owns Revision A.

“We service Los Angeles County.”

Generally true.

Wrong—for the address outside the company’s current service boundary.

“This repair is covered.”

Potentially true.

Wrong if the customer’s warranty period has expired.

“That service is included.”

The firm absolutely provides the service.

But not under this client’s current agreement.

“The software supports that feature.”

True.

But only on a particular plan or with an additional integration.

None of those general statements has to be dishonest.

They are simply incomplete.

And incomplete context can turn good information into a bad customer experience.

The general answer is not always the customer’s answer

That is one of the most important distinctions a growing business can learn.

A customer rarely experiences your company at the level of a general policy.

They experience it through their specific situation.

They are not really asking:

“Does your company have a warranty?”

They are asking:

“Does the warranty cover what happened to me?”

They are not asking:

“Do you sell compatible accessories?”

They are asking:

“Will this particular accessory work with the exact product I already own?”

They are not asking:

“Do you serve this region?”

They are asking:

“Will you come to my address?”

That difference is where context becomes customer care.

Sometimes the disagreement is not in the answer. It is in the missing question.

Imagine a manufacturer receives this question:

“Does Accessory B work with Model X?”

Sales says yes.

Engineering says only sometimes.

Customer service finds a product page that appears to say yes.

Who is wrong?

Possibly nobody.

Sales may be thinking about the current Model X.

Engineering may know Revision A had a restriction.

Customer service may be reading a page written for the latest configuration.

The real problem may be that:

“Does Accessory B work with Model X?”

was never specific enough.

The business may actually need to answer:

“Is Accessory B compatible with Model X, Revision B, operating at this voltage, under this installation condition?”

Now the company has a question it can meaningfully investigate.

That is a very different approach from forcing every employee to memorize the same generic sentence.

Consistency without context can standardize the wrong customer experience

Businesses often say:

“We just need everyone giving customers the same answer.”

Sometimes that is exactly right.

But not always.

Different customers may legitimately require different answers.

Two customers can ask the same words:

“Am I covered?”

One may be covered.

One may not.

Two customers can ask:

“Can I use this component?”

One may own the correct product revision.

The other may not.

The goal is therefore not blind consistency.

The better goal is:

The same question, under the same relevant context, should lead toward the same supported answer.

That distinction is subtle.

It is also extremely important.

Your customers are increasingly expecting contextual help

B2B buyers are becoming more self-directed, but current research shows that humans remain especially important when buyers need validation, context and decision support.

Gartner reported in 2026 that 69% of surveyed B2B buyers preferred to validate AI-generated insights with sales representatives. Buyers used an average of seven information sources during a recent purchase, while 45% reported using generative AI for vendor and product research. Gartner concluded that sellers increasingly add value by helping buyers validate information, reduce risk and move forward with greater confidence.

That is important.

Customers can find more information without you than ever before.

But finding information is not the same as determining what applies to their particular situation.

Gartner’s other 2026 buyer research emphasized the importance of helping buyers understand value within their specific role and business context, rather than relying only on static information.

And McKinsey’s 2026 Global B2B Pulse found that buyers now use an average of ten channels during the purchasing journey. It also identified inconsistent information across teams and difficulty accessing knowledgeable support as leading reasons buyers switch suppliers.

The message for smaller businesses is clear:

More information channels make context more important, not less.

The customer should not have to figure out what applies

Imagine your customer doing this:

They read the general answer on your website.

They download a technical PDF.

They ask an AI assistant.

They call your salesperson.

The salesperson gives another answer.

Then customer service asks for the model number and realizes there is an exception.

The customer has now spent their time reconstructing your business rules.

That is work your business should be trying to remove from the customer experience.

The customer should not need to become an investigator just to learn which version of your answer applies to them.

Better customer care sometimes begins with one more question

Imagine two service interactions.

The customer asks:

“Is this covered?”

The first employee responds:

“Yes.”

Fast.

Confident.

Potentially wrong.

The second employee responds:

“I can check that for you. Can I confirm the product model and purchase date so I apply the right warranty?”

That response takes slightly longer.

But it is better service.

The employee understands that the question requires context before an answer.

That is not hesitation.

It is professionalism.

The fastest answer is not always the most helpful answer.

Sometimes the best service begins with one more question.

The Context Test

You can test this inside your own company.

Choose one consequential question customers regularly ask.

Then determine whether the answer changes according to any of these conditions.

Who?

Does the answer depend on customer type, account status, eligibility, membership or another customer-specific factor?

What?

Does it depend on product, model, service, revision, component or configuration?

When?

Does purchase date, contract date, installation date or policy period matter?

Where?

Does geography, jurisdiction, service area or installation location change the answer?

How?

Does installation method, use condition or application change what is permitted?

Under what agreement?

Does a contract, warranty, proposal, service plan or pricing agreement control the answer?

What information is still missing?

Is there something the business must know before giving a responsible response?

If changing any of those details changes the answer, then your business does not have one generic answer.

It has a context-dependent answer.

That distinction should be visible to the people serving your customers.

“It depends” is not always a bad answer

Customers usually dislike hearing:

“It depends.”

And understandably so.

Sometimes companies use those words because nobody knows the answer.

But there is another kind of “it depends.”

A responsible one.

For example:

“It depends on which model you have. If you give me the model number, I can determine which answer applies.”

That is not ambiguity.

That is useful context.

The problem is not that an answer depends on something.

The problem is when the business cannot explain what it depends on.

That creates another useful test:

If your most experienced employee says “it depends,” could a new employee explain exactly what it depends on?

If not, important business knowledge may still be trapped in experience rather than established as something the organization can reliably use.

This problem appears in almost every industry

For a manufacturer:

“Can these components be combined?”

It may depend on model, revision, voltage or mounting condition.

For a contractor:

“Is this covered under our workmanship warranty?”

It may depend on installation date, contract terms and the nature of the repair.

For a distributor:

“Can I substitute this product?”

It may depend on application, temperature rating, certification or manufacturer approval.

For a professional-services firm:

“Is this included in the engagement?”

It may depend on the signed scope and the nature of the requested work.

For a multi-location company:

“Is this offer available?”

It may depend on location, timing or participating franchise.

For a software business:

“Does the product support this?”

It may depend on plan, version, configuration or integration.

Different businesses.

Same underlying challenge.

The answer may be correct somewhere without being correct here.

AI does not remove the need for context

AI makes this challenge even more interesting.

Modern AI systems can search, summarize and explain huge amounts of information remarkably quickly.

That does not remove the need to establish:

Which customer’s situation are we actually answering for?

Suppose an AI tool correctly retrieves:

“This product has a five-year warranty.”

Excellent.

But does it know:

when this customer purchased the product?

which model they own?

whether registration was required?

whether an exclusion applies?

whether the customer is asking about parts or labor?

The information may be correct.

The application may still be wrong.

So better AI does not make business context irrelevant.

Better use of AI often makes good business context more valuable.

This is where a Figsite Business Knowledge Catalog is different

Figsite does not begin by trying to collect every fact your business possesses.

We begin with the questions your business cannot afford to answer inconsistently or without the context that changes them.

Then the work can examine:

  • the question that actually needs answering;
  • the supporting information;
  • the conditions that change the answer;
  • conflicting or missing evidence;
  • what remains unresolved;
  • and who inside the business has authority to approve the company’s position.

Your company keeps the decision authority.

Figsite helps make the knowledge behind that decision clearer.

Some questions reach a supported, company-authorized answer.

Some remain conditional.

Some require additional customer context.

Some remain visibly unresolved.

And sometimes the responsible response is:

“We need one more piece of information before we can answer this correctly.”

That is not a weakness.

That is superior customer care.

Better Business Knowledge changes the experience without the customer ever seeing the Catalog

Your customers may never open your Business Knowledge Catalog.

That is perfectly fine.

They experience its value through the business.

Sales knows which questions require additional context.

Customer service understands which policy applies.

Technical teams spend less time reconstructing the same decision.

New employees have clearer guidance about exceptions.

Management can see where important questions remain unresolved.

Marketing has a stronger foundation for future approved public claims.

AI tools can eventually work from better-established knowledge when the company chooses to use them.

The customer experiences the result as something much simpler:

“This company understands my situation.”

That is the goal.

Start with the question that always gets answered with “it depends”

You do not need to reorganize your entire business to begin.

Think of one question customers ask where the answer regularly starts with:

“It depends.”

Now ask:

What does it depend on?

The product?

The model?

The customer?

The purchase date?

The location?

The application?

The contract?

The configuration?

If your business cannot clearly identify those conditions—or if only one experienced person knows how to work through them—that may be an excellent starting point for a Business Knowledge Catalog project.

A defined project—not another forced subscription

The initial Figsite Business Knowledge Catalog is a scoped, one-time professional project.

A required ongoing subscription is not part of that initial engagement.

If the relevant facts behind your answers change infrequently, the initial Catalog may remain useful for a meaningful period.

If products, policies, services, warranties, configurations or other important facts change regularly, optional monitoring may make sense.

The decision should follow the business’s rate of change.

Not a subscription requirement.

Build the knowledge foundation once. Monitor it only when the business changes enough to justify monitoring.

The better question is not simply “Is this answer true?”

It is:

Is it true for this customer?

For this product?

For this version?

At this time?

In this location?

Under these conditions?

Under this agreement?

And if the business does not yet know—

does it know enough not to guess?

That is a much higher standard for customer care.

It is also a much more useful standard.

Figsite helps businesses know not only which answers they can stand behind—but when those answers actually apply.

If there is one important customer question in your company where the answer changes depending on who is asking, what they own, when something happened, where they are located, or another critical condition—

bring us that question.

And tell us:

What does it depend on?

We can discuss whether a scoped Figsite Business Knowledge Catalog project is the right next step.

Because your customers do not merely deserve an answer that is generally correct.

They deserve the answer that is correct for them.


The initial Business Knowledge Catalog is a scoped professional engagement. Ongoing monitoring is optional and separately agreed. A private Catalog does not automatically distribute information to employees, websites, partners, search engines or AI systems. Public distribution requires separate authorization and appropriate implementation. Figsite does not guarantee search rankings, AI recommendations, indexing or third-party platform outcomes.

Which business answer needs a better foundation?

Start with one important product, policy, or service question. Figsite can help examine the evidence, document unresolved issues, and keep your company’s approval decision in the right hands.

A scoped professional engagement. Ongoing monitoring is optional; search results and indexing are not guaranteed.