Changelog
Last updated: September 9, 2026
The changelog communicates product changes — new features, improvements, and bug fixes — to your team and your customers.
Create a changelog entry
- Feedback → Changelog → "New entry"
- Fill in the fields:
| Field | Description |
|---|---|
| Title | Headline (e.g., "AI Copilot for Agents") |
| Body | Detailed description (Markdown supported) |
| Category | feature, improvement, fix, announcement |
Categories
| Category | Usage | Example |
|---|---|---|
| feature | Completely new feature | "New survey system" |
| improvement | Improvement of an existing feature | "Faster Knowledge Base search" |
| fix | Bug fix | "Chat widget now loads correctly on Safari" |
| announcement | General announcement | "Maintenance window on 04/15" |
Publish
New changelog entries are initially unpublished (Draft):
- Create an entry and check the content
- Click on "Publish"
- The publication date is set automatically
- The entry is now publicly visible
Withdraw: Click on "Unpublish" to hide an entry again.
Public view
The changelog is accessible via a public endpoint:
GET /api/v1/public/changelog/:tenantId
Only published entries are displayed, sorted by publication date (newest first).
Best practices
- Publish regularly — at least 1–2 entries per month
- User perspective — Describe the benefit, not the technical implementation
- Short and concise — 3–5 sentences per entry are sufficient
- Screenshots — Optional, but helpful for UI changes
- Link to the roadmap — If a roadmap item is "Done", write a changelog entry about it
Changelog structure example
# AI Copilot for Agents
Agents can now generate AI-powered response suggestions.
**New features:**
- Response suggestions based on chat history and Knowledge Base
- Text improvement with tone adjustment (formal, friendly, precise)
- Conversation summary for quick context
Activate under Settings → AI Chatbot.