Few-Shot KGs support all features below except: Default terms, Lemmatization using POS, Search in Answer, and Contextual Path Qualification. Path-Level and KG Synonyms apply only to Mandatory Terms and Tags. See Knowledge Graph Types Comparison.
Add FAQs
- Go to Automation AI > Knowledge AI > FAQs > Manage KG.
- Click Add Intent (top-right) and select FAQ.
- In Add Question, enter the primary question.
- (Optional) Add alternate questions in + Alternate Question. Precede a question with
||to define it as a pattern. - (Optional) Add tags to improve KG intent detection.
- (Optional) Enter a Display Name shown to users in ambiguity scenarios.
- In Bot Response, enter the default response.
- (Optional) Add alternate responses in + Alternate Response (selected randomly at runtime).
- (Optional) Enable Conditional Response for rule-based responses. See FAQ Conditional Responses.
- (Optional) Add a Reference ID linking to an external source.
- (Optional) Toggle Intent Status — disabled intents are excluded from intent recognition.
- Click Save.
Manage Default Responses
Responses use the same prompt editor as other dialog nodes. See Prompt Editor. Channel-specific responses: Select a channel before typing the response. Always include an All Channels response as the fallback.Handle Long Responses
- Add Extended Response — splits the response into sequential chunks.
- Add Alternate Response — adds a separate response variant (selected randomly at runtime).
Add FAQs from an Existing Source
| Method | When to use |
|---|---|
| Knowledge Graph Generator | Auto-generate a KG hierarchy from an FAQ list, then import it. |
| Import | Import a KG exported from another AI Agent. |
| Knowledge Extraction | Populate FAQs from an existing Q&A list. |
Move FAQs Between Nodes
- Click the source node. FAQs appear in the right pane.
- Check the FAQ(s) to move (supports multi-select).
- Drag and drop onto the target node.
Edit and Delete FAQs
- Select the node. FAQs appear in the right pane.
- Hover over the question or response and click Edit.
- Make changes and click Save.
- To delete: click the Bin icon.
- Select multiple FAQs to delete in bulk.
FAQ Conditional Responses
Define rule-based responses that vary based on conditions such as customer location, session variables, or channel.How It Works
- The platform identifies the FAQ using normal intent recognition.
- Conditions are evaluated in the order defined.
- If a condition matches, its response is used.
- If no condition matches, the default response is used.
- Channel-specific responses take priority within matched conditions.
- Channel-specific response (within the matched condition) → All Channels response (within the matched condition) → Next condition → Default response.
Setup
- Open the FAQ and enable the Conditional Response toggle.
- Define conditions using context, content, or environment variables.
- Example:
context.session.BotUserSession.location Equals To "United States"
- Example:
- Select an operator: Exists, Does Not Exist, Equals To, or Not Equals To.
- Enter the comparison value.
- Add multiple rules with AND / OR logic.
- Enter the Then Response for each condition.
- (Optional) Add channel-specific response variants by selecting from All Channels.
Limits
- Max 10 conditions per FAQ.
- Max 10 nested rules per condition.
Best Practices
- Identify key variables (location, customer type, product).
- Order conditions from most to least specific.
- Use AND for narrow scenarios, OR for broad ones.
- Always define a default response.
- Use only
context.session.BotUserSessionvariables — they persist across the session. - Create context, environment, or content variables before referencing them.
- Save and train after changes; publish to update end channels.
- New apps default to Few-Shot model; imported apps may use Ontology. Check under NLU Config > Knowledge Graph > KG Type.
- Enabling conditional responses removes extended responses. Disabling conditional responses permanently deletes all conditional response data.
- Exporting as JSON includes conditional responses; CSV export does not.