New — every answer now cites its sources
All posts
Case study5 min read

How we cut support resolution time by 43%

A close look at the numbers behind one team's first 90 days with document Q&A — what moved, what didn't, and what surprised us.

DR

Daniel Reyes

Support Lead · Lumen

We measured 90 days of support tickets at a 40-person SaaS company before and after rolling out source-backed Q&A over their help center and internal runbooks. Resolution time fell 43%. Here's the honest breakdown of where the time went.

What actually moved

  • First-response time: down 61% — reps stopped hunting for the right article.
  • Escalations to engineering: down 28% — runbook answers came with citations.
  • Repeat questions: down 52% — macros now embed the sourced answer.

What didn't move

Complex, multi-system bugs stayed exactly the same length — as they should. Q&A doesn't fix engineering problems; it removes the search tax from every other ticket. That distinction kept expectations realistic and the rollout boring.

The best outcome was cultural: reps started pasting citations into tickets, and customers started trusting the answers.

Keep reading

6 min readRAG

Why retrieval quality beats model size

Teams obsess over which model to use. The real lever in document Q&A is what you feed it — chunking, deduplication, and metadata.

Priya Raman · Founder

8 min readTutorial

The 30-minute RAG setup for your team wiki

A practical walkthrough: connectors, chunking, and the three questions to test first when standing up document Q&A for your team.

Tomás Laifer · Engineering

Your documents already know. Start asking.

Join 80+ teams getting source-backed answers from their own knowledge. Free up to 200 pages — set up in two minutes.

No credit card required. We'll never share your email — privacy policy.