How do Product Managers submit updated product docs so Guru—and all chatbots—stay in sync?

How do Product Managers submit updated product docs so Guru—and all chatbots—stay in sync?

⚡Quick answer -

Send the final, approved product documentation to the AI Knowledge Manager. They will create a Guru FAQ card, route it for SME verification, publish it, and trigger the standard bot-update flows to Zoho Desk, Crisp, and the internal Enum-powered LMS chatbot.

When should I use this guide?

Use these steps any time official product documentation changes and the information must reach customers or employees through our chatbots or knowledge bases.

End-to-end workflow

  1. Product Manager (PM) finalises the updated product documentation.
  2. PM sends the docs to the AI Knowledge Manager.
  3. AI Knowledge Manager converts the docs into a Guru FAQ card using the approved framework.
  4. Subject-Matter Experts (SMEs) verify the card inside Guru.
  5. Once verified, the card is published in Guru (our single source of truth).
  6. Guru automatically pushes the verified card to Zoho Desk and Crisp knowledge bases.
  7. The HR team performs its regular Guru export → CSV → PDF → Enum upload process, allowing Enum to re-index and refresh the internal LMS chatbot.

Roles & responsibilities

Role

Primary actions

Hand-off point

Product Manager

Provide final docs

Sends docs to AI Knowledge Manager

AI Knowledge Manager

Create Guru card; coordinate SME review

Publishes verified card

Subject-Matter Experts

Verify accuracy

Approve in Guru

HR Team

Export Guru cards; upload to Enum

Enum re-indexes LMS bot

How each chatbot updates

• Zoho Desk & Crisp: Guru pushes the verified card automatically; the new content replaces any mapped article.

[Zoho, Crisp]

• Internal LMS chatbot (Enum): HR’s routine export/upload cycle feeds Enum, which then refreshes the bot’s knowledge base.

(Internal Bot Access)

Workflow diagram

image.png

Alt-text: “Data flows from Product Manager to Guru, then to external and internal chatbots”