Release notes

April 14, 2025

BCP 47 support in article upserts

The language field on the article object in the upsert API now supports BCP 47 language tags (e.g., en-CA, fr-FR). The previously supported locale field is deprecated but still accepted for backwards compatibility if language is not provided.

API responses from GET /v2/knowledge/articles and GET /v2/knowledge/articles/{id} will continue to return locale, but it is no longer documented. In these responses, the language field contains the ISO 639-1 two-character language code, not the full BCP 47 tag.

This is part of a gradual migration. Eventually, locale will be removed from both persisted records and API responses, and language will consistently use BCP 47 tags across all endpoints.

April 14, 2025

New Toggle for AI-Generated Topics

You can now toggle AI-generated Topics on or off, allowing for greater control over how conversations are categorized—and ensuring that Topic taxonomy in Ada aligns with what matters to your business.

What’s New?

  • AI-Generated Topics Toggle – You can now toggle off AI-generated Topics entirely from the Topics view.
  • Fallback Topics – When AI-generated Topics are off, unmatched conversations are automatically sorted into:
    • Other Inquiries – For conversations with understood intent that don’t match any existing Topic.
    • Unclear or Incomplete Inquiries – For conversations where the intent is unclear.
  • Smarter Matching Behavior – When AI generation is off, conversations won’t match to inactive Topics—preserving your intended structure.
  • No Change by Default – AI-generated Topics remain on by default. You can turn them off at any time.

Why This Matters

Previously, AI-generated Topics were always on. While helpful in many cases, some of you shared that:

  • The generated Topics created were too broad or duplicative.
  • You wanted more control over what gets added.

Now, you can decide whether to rely on AI-generated Topics—or only use the Topics you’ve defined.