All of this is optional. With no configuration, every ticket can use your full knowledge base.
1. Create your products
- Go to Settings and click Manage products on the Product Catalog card.
- Under Create product, enter a Product name and Product ID (a lowercase slug, for example
billing). The ID is locked after creation. - Click Create product. Repeat for each product.
2. Assign knowledge to products
- Whole knowledge base: in Data Sources, set the Default product for the knowledge source. It is used when no URL rule matches.
- Mixed help center: use the Article Product Classifier to override the default for specific article URLs:
- In Settings, click Configure on the Article Product Classifier card.
- Click Add Group, then pick one or more Products.
- Add regex patterns matched against article URLs, for example
^https://help\.example\.com/billing/.*. - Repeat for each product, then click Save.
3. Assign tickets to products
- In Settings, click Configure on the Case Product Classifier card.
- Click Add Group and pick the Product.
- Add any of these signals:
- Brand ID (Zendesk only): exact match on the ticket’s numeric Zendesk brand ID.
- Tags: exact tags applied when the ticket was created.
- Keywords: whole-word, case-insensitive match in subject or description (
billmatchesBillbut notbilling). - Regex patterns: matched against subject and description.
- Repeat for each product, then click Save.
- Zendesk Brand ID (Zendesk only)
- Regex
- Keyword
- Tag
4. Scope a chatbot to a product
- Go to AI Products > Chatbot, click Configure and deploy, and open the chatbot configuration.
- On the Advanced tab, under Product segmentation, pick the Product.
- Click Update Configuration.
Example
Productsbilling and shipping:
- Knowledge: URL rule
^https://help\.example\.com/billing/.*forbilling, and^https://help\.example\.com/shipping/.*forshipping. - Tickets:
billinghas Brand ID123456789, keywordinvoice, and regex(?i)\b(invoice|payment)\b.shippinghas tagshippingand keywordship.
123456789 matches billing before IrisAgent checks its text or tags. A ticket from another brand saying “my payment failed” matches the billing regex. Both are answered from billing articles only.