Tags: Definitions

Roles: Read Only, Members, Admins


One of the main benefits of using Guru is the ability to find accurate information quickly. With Tags, your team can search for knowledge in a swift, intuitive way.

Utilizing Tags

  1. Tags enhance Guru's search functionality by allowing your team to zero in on highly specific attributes. For example, while on a call, a rep can remain in their workflow and search for case studies by industry (e-commerce, SaaS, etc.) or objections by persona (manager, rep, etc.)
  2. You know your team best! Create Tags that reflect the terminology they're most familiar with, and update them at any time.
  • Tags are Collection-specific, meaning they exist in only one Collection, it's important to utilize Tags that are not repetitive and pair well with the Tags of other Collections your team utilizes.
  1. Tags aid in accessing and organizing knowledge, especially as new content is added. For example, as you identify a new competitor, adding a "competitor" Tag to its Card ensures that your reps can perform streamlined searches to easily find strategic knowledge on their next call.

How many Tags should I put on a Card?

  1. When it comes to Tags, less is more. While we recommend no more than 4 Tags per Card, it's always best to opt for fewer, more meaningful Tags. This way, you can be sure that searching for information remains simple, uncluttered, and effective.
  • On a Card containing a case study, a great option would be to include Tags that indicate it's a case study in a particular industry and the size of the company. For example:
  • On a Card listing a FAQ about a certain product, a successful Tag sequence might include the feature the FAQ details, that it's a FAQ, and the product's name, like so:

To help you get started, we compiled some sample use cases of common Tags:

Sales

Competitor

  • This Tag would be used on all cards that have relevant information on your competitors. The goal being that if someone on your team is looking for details on how you compare to a competitor they could easily search and find it.

Case Study

  • This Tag would be used to distinguish all case studies, and could be used in tandem with tags on the use case or industry of the company. For example, a case study on Guru being used to help a sales team by a company in the healthcare space would be tagged: #case study #health care. This allows your reps to immediately find the case study that is pertinent to the needs of the prospect.

Category: Industry

  • Organizing Tags into Categories provides for a more structured search.
  • Tagging Cards by the industry to which they correspond gives your reps more information to work with while culling through knowledge on a call or responding to an objection.

Category: Size

  • The Tags in this category would be the sizes of your different customer segments, so your reps can easily sort customer facing information to ensure that applies to the size of their prospect.

Category: Features/Products

  • The Tags within this category would be based on the products/features that your company offers. Tagging information on the product would allow your rep to quickly find the messaging and FAQs on that particular product or feature.

Support

Category: FAQs

  • The Tags within this Category would represent the type of FAQ, so your reps could easily sort through the FAQs without having to worry about billing vs. product FAQs in their searches.

Category: Features/Products

  • The Tags within this Category would be based on the products/features that your company offers. Tagging information on the product would allow your rep to quickly find the messaging and FAQs on that particular product or feature.

Internal

  • This Tag could be used to denote information for internal use only. It would signify to reps that the information on this Card is not to be shared with the general public.

Published

  • A Published Tag can be used to denote information that is already published and publicly available.

Unpublished

  • Unpublished or external information is not published, but unlike internal information, can be shared publicly with customers. This Tag can indicate that to your team, so they know how to share the information with the customer.

Troubleshooting

  • This Tag would represent the accepted methods used to troubleshoot issues. Reps could easily search this Tag and a product or feature Tag to access a specific troubleshooting procedure by product.