Guru offers multiple ways to create content and incorporate outside content into Guru Cards. Read on to understand in what instances each of these paths may be most helpful.

When to create a Card

Break up your long documents and make each smaller piece of knowledge its own Guru Card. Examples of when you might do this:

  • On-the-phone questions that reps need to find an answer to fast. Think of how you'd want your reps to use AI Suggest: the rep should only see the answer to the question at hand.

  • Paste-able answers like email templates, code snippets, and FAQs. The rep simply needs to hit the Copy Card Content button to paste their response where they need it.

  • Process how-to's that walk through how to complete a single task. If there are many interdependent tasks, you can link several Guru Cards here.

πŸ’‘ Tip

Once your long-form document or process is spread across several Guru Cards, you can make one "Overview" Card that links out to the relevant individual Cards. If your Card is really long and the knowledge has to stay in one Card, consider using anchored text with Guru's Markdown functionality to create a table of contents at the top of the Card.

When to import content

Guru's content migration tool allows you to import content from other sources. This is especially helpful upon first onboarding onto Guru to consolidate your team's knowledge.

When to link out to or embed content

If you want to provide your team with coaching on when & how to use an asset, it's better to create a Guru Card with a short blurb about that asset, link out to it, and embed the asset so that your team can scroll through the asset without leaving the Guru Card.

Some things you could put in a Guru Card about the linked or embedded asset:

  • Recommended email templates or social language to use when sharing the document externally

  • Guidance on when in the sales cycle it's appropriate to send this asset

  • Customer segments this asset works well with

When to sync content

Sometimes it doesn't make sense to bring the document into Guru, but that shouldn't stop you from accessing it from Guru! Examples of when you might sync knowledge into Guru:

  • Help Center documentation: Make it easy for your team to access external and internal knowledge all in one place.

  • Analyst Research: Reports like this are often licensed and must not be altered.

  • Other team's tooling: Make content managed across other platforms accessible to more users to view.

πŸ“‘ Related articles

Did this answer your question?