Skip to content

Use case · Support deflection

Answer the questions your docs already answer

Most support queues are the same thirty questions asked a thousand ways. PageTruth answers them from your help center the moment they are asked, with the page that proves it, and routes everything else to your team.

The problem

Your docs are good. Nobody finds the right page.

Keyword search on a help center returns ten articles for "export". The customer gives up and opens a ticket, and an agent pastes a link to the article they could not find.

How PageTruth handles it

What changes

  1. Ask in their own words

    Customers type the question the way they think it, not the way your article is titled. Retrieval matches meaning, not keywords.

  2. Answer with the source

    Every answer cites the article and section it came from, so the customer can read on and your team can check it.

  3. Hand off when it should

    When the docs do not cover it, the assistant says so and offers your support email or form — it never invents a policy.

What to put in the knowledge base

  • Your existing help center (import by URL or sitemap)
  • Billing and plan FAQs
  • Troubleshooting PDFs
  • Policies: refunds, data retention, SLAs

What to watch in insights

Resolution rate
Share of conversations that ended without a handoff or a thumbs-down.
Content gaps
Questions the docs could not answer, grouped and counted, so you write the right article next.
Handoffs
How many conversations reached your support channel, and what they were about.

Give your customers answers, not a ticket number

Point PageTruth at your docs, publish a help center and drop the widget into your app. The free plan is enough to see it answer your own questions.