From 14e65f69acc8d7032f30543b00c0d9cf44ad63a4 Mon Sep 17 00:00:00 2001 From: daniel-azoulai Date: Tue, 11 Nov 2025 05:04:58 -0800 Subject: [PATCH] Update case-study-xaver.md --- qdrant-landing/content/blog/case-study-xaver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/blog/case-study-xaver.md b/qdrant-landing/content/blog/case-study-xaver.md index d479793b9..62c2b42b5 100644 --- a/qdrant-landing/content/blog/case-study-xaver.md +++ b/qdrant-landing/content/blog/case-study-xaver.md @@ -62,7 +62,7 @@ To meet latency goals and maintain precision, Xaver implemented a two-tier retri This architecture enables the Xaver platform to deliver knowledge for the most common conversational situations instantly, while supporting rare or complex cases through a second-tier retrieval layer. The approach minimizes computational overhead, reduces response time by two to three seconds in typical cases, and preserves conversational flow, which is crucial for voice and video experiences. -![Xaver Retrieval Process][/blog/case-study-xaver/xaver-retrieval-process.jpg] +![Xaver Retrieval Process](/blog/case-study-xaver/xaver-retrieval-process.jpg) *Figure: Xaver’s retrieval process*