Support tickets and pre sale questions are different signals

A website assistant on a marketing site collects two very different kinds of conversation, and most teams analyse them as one pile. The result is an average that describes neither group.

Pre sale questions come from people deciding whether to buy. Post sale questions come from people who already did. They differ in what they reveal, who should act on them, and what a good outcome looks like.

What each one tells you

A pre sale question is a marketing signal. It says the site did not communicate something a buyer needed. The owner is whoever owns the website. Success means the question stops appearing because the page now answers it.

A post sale question is a product or documentation signal. It says the product was unclear or the docs were incomplete. The owner is product or support. Success means the question stops appearing because the product got clearer, or it gets answered faster because the docs improved.

Both are useful. Averaging them hides both.

How to tell them apart without asking

You usually can, from context that is already available:

• Page location. Pricing, features and comparison pages skew pre sale. Docs, help and account pages skew post sale.
• Phrasing. "Can I" and "do you" are usually pre sale. "How do I" and "why is" are usually post sale.
• Specificity. Pre sale questions are about capability in general. Post sale questions reference a specific thing the person is looking at.
• Session context. A visitor who arrived from search and asked one question is likely evaluating. A returning visitor deep in a workflow is not.

None of these is perfect on its own. Together they sort most conversations correctly, and the ambiguous remainder is small enough to read by hand.

The routing consequence

Once separated, the two streams should go to different places. Pre sale questions belong in the content roadmap. Post sale questions belong in the documentation backlog and, when they repeat enough, in the product roadmap.

Sending everything to support is the default failure. It buries marketing signal under operational load, and the people best placed to fix a pricing page never see the evidence that it needs fixing.

The metric that changes

For pre sale, the useful metric is the rate at which a question category disappears after you publish the answer. For post sale, it is time to resolution and whether the same issue recurs.

Deflection rate, the number people usually reach for, is a post sale metric wearing a marketing badge. On a pre sale conversation, deflecting a question is not obviously a win. Sometimes the right outcome is a person, because the question signals a serious buyer with a specific concern.

A caution about mixing them in a dashboard

If your analytics view shows one number for questions answered, you will optimise for the wrong thing. A pre sale question answered by a page edit and a post sale question resolved by a support reply are both successes, but they are not the same success and they do not trade off against each other.

Split the view. Two smaller honest numbers beat one large misleading one.