← Case studies & research

Buyer discovery · Appointment software

A relevant product missed the buyer shortlist.

The website described the requested appointment workflow, but two captured AI answers named other tools. We turned that small observation into a focused product-page verification plan.

Study type
Anonymized research
Observation date
Scope
1 buyer question · 1 round
Current stage
Initial check complete · expanded testing pending
BUYER DISCOVERYRESEARCH NOTE
Relevant on-site. Absent in this snapshot.
1
buyer scenario
2
captured AI answers
0
target mentions in those answers
Verify capability → clarify the page → repeat
Summary of recorded observations · 2026-10-13

The useful finding

A feature page and a place on the buyer's shortlist are different things to measure.

Neither captured answer named the target product in one non-brand buying scenario, even though its website described a relevant use case.

01

The buying problem

An appointment-software supplier had a relevant workflow on its website. The research asked whether a buyer describing that need, without naming the brand, would encounter the product in an AI-generated shortlist.

02

What we checked

One newly written buying scenario was checked in one web-search query and in fresh ChatGPT and Gemini sessions. Both AI answers were retained as text. This was an initial research slice, not a complete audit or a reproduction of a customer's original question.

03

What the evidence showed

Both assistants named alternatives and neither named the target product in the captured answer. The supplier's site already had a relevant industry page, so recommending another similar article would have ignored an existing asset.

That finding supports a closer look at product facts and query fit. It does not explain why the product was omitted or establish its visibility across a market.

04

The recommended change

Verify the actual appointment workflow and make the existing page specific enough for a buyer to evaluate.

  • Distinguish collecting a preferred time, staff confirmation and reserving a live calendar slot.
  • Verify supported integrations, rescheduling and conflict handling through a product demonstration.
  • Clarify those verified facts on the existing use-case page, link it from the product page and keep the product name consistent.
  • Repeat the original question and add closely related needs and a brand-fact question.
05

Where the work stands

The initial check and proposed page changes were documented. The product was not login-tested, no website changes were made, and no post-change result or sales outcome was recorded.

Evidence & boundaries

Based on two retained AI answer texts and website-review records. Brand, domain, exact question, account identity and private correspondence are omitted from this public summary.

An anonymized research snapshot, not a customer endorsement. Two answers to one question do not establish market share, stable absence, lost revenue or a proven fix.

Public summary published . Findings refer to the dated observations above.
Next stepVerify the booking workflow, refine the existing use-case page and run a broader repeat check.Check your own website →Explore the other cases →
Contact
Contact molthubWhatsApp+86 158 6378 9235Emailchengzhao640@gmail.com