From 3de773f592ddb47f242e940baca91cdd64e5eb07 Mon Sep 17 00:00:00 2001
From: Andy Vandervell <92976667+andyvan-ph@users.noreply.github.com>
Date: Tue, 11 Feb 2025 17:47:47 +0000
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Ian Vanagas <34755028+ivanagas@users.noreply.github.com>
---
 contents/handbook/content-and-docs/docs.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/contents/handbook/content-and-docs/docs.md b/contents/handbook/content-and-docs/docs.md
index a86693c71c6a..726c35850af0 100644
--- a/contents/handbook/content-and-docs/docs.md
+++ b/contents/handbook/content-and-docs/docs.md
@@ -66,6 +66,7 @@ Each week the Content & Docs crew picks someone to review the state of feedback
 - #content-docs-ideas
 - #ask-max for questions missing content
 - Zendesk tickets [where **root cause** is `documentation unclear`](https://posthoghelp.zendesk.com/agent/filters/33465387985947)
+- [Inkeep chat sessions](https://portal.inkeep.com/posthog/projects/clz7fyu8i001bomqpr7t8lds8/chat/chat-sessions?filters={%22isOnTopic%22:%22yes%22,%22isClear%22:%22yes%22,%22firstMessageTime%22:%2230d%22,%22isDocumented%22:%22no%22}) where there is a documentation gap
 
 Where appropriate and actionable, the gardener should create new issues to capture what surfaces from such feedback. This should occupy no more than 2-4 hours of effort each week.