Overview
When the response engine generates new responses, it can automatically suggest tags based on the content used. You can control this behavior for each tag category by selecting a tag assignment strategy that best fits your needs.
Understanding Tag Assignment
Tag assignment helps maintain consistency in your knowledge base by automatically suggesting appropriate tags when new responses are created. Different categories may need different approaches based on how your content is organized and used.
Available Tag Assignment Strategies
1. From the content used
What it does: Inherits tags that appear in both the project settings and the source content used to generate the response.
When to use:
Your content is already well-tagged and you want to maintain that tagging
It's critical that tags remain consistent with the source content
Mixing tags could cause serious issues (compliance, security, etc.)
Example use case:
This content is related to a partner product you sell and when used the new response should still be tagged with that partner.
Financial services where fund-specific content must never be tagged with other funds
2. AI Auto-tagging
What it does: Uses AI to analyze the response content and intelligently suggest the most appropriate tags from your project settings.
When to use:
Your content boundaries are flexible or overlapping
Older content might not be perfectly tagged
You want tags based on actual response content, not just source material
Example use case:
You have responses that cover multiple features and products but the final responses often use a subset of that information. AI auto-tagging would ensure that it only gets assigned tags that match the final response not everything that was on the original item.
3. Manual
What it does: Never suggests tags from this category for new responses.
When to use:
The category is purely organizational or metadata
Tags indicate source type rather than content topic
The tags don't make sense for customer-facing responses
Example use case:
Tags like "Research," "Internal Policy," or "Archive" that indicate document type
Administrative tags used for internal organization
Choosing the Right Strategy
Consider these questions for each tag category:
Choose "From the content used" if:
✓ Your content is accurately tagged
✓ Tag boundaries are strict and important
✓ Incorrect tagging could cause compliance or security issues
✓ You want complete control over tag inheritance
Choose "AI Auto-tagging" if:
✓ Content often spans multiple tags within the category
✓ You want flexible, content-aware tagging
✓ Historical tagging might be incomplete or imperfect
✓ Tag boundaries are more like guidelines than rules
Choose "Manual" if:
✓ Tags are for internal use only
✓ The category describes metadata, not content
✓ Tags would confuse or mislead if applied to responses
Best Practices
Start conservatively: If unsure, begin with "From Content" for critical categories and "AI-Powered" for flexible ones
Mix strategies: Different categories can use different strategies - choose what works best for each
Regular review: As your content evolves, revisit your auto-tagging strategies
Quick Reference
Strategy | Best For | Behavior |
From the content used | Strict boundaries, well-tagged content | Inherits only matching tags |
AI Auto-tagging | Flexible boundaries, overlapping content | Intelligently suggests relevant tags |
Manual | Metadata, internal organization | No auto-tagging |
By thoughtfully configuring tag assignment strategies, you can maintain a well-organized knowledge base while reducing manual tagging effort.