Public Roadmap
Last updated: September 9, 2026
The public roadmap shows visitors and customers which features are planned, in progress, or delivered.
Create a Roadmap Item
- Feedback → Roadmap → "New Item"
- Fill in the fields:
| Field | Description |
|---|---|
| Title | Feature name (max. 300 characters) |
| Description | Detailed description |
| Status | Planned, In Progress, Done |
| Category | Thematic assignment |
| Target Date | Planned delivery date (optional) |
| Sorting | Order on the roadmap |
| Public | Whether the item is visible on the public roadmap |
Status
| Status | Display |
|---|---|
| Planned | "Planned" — Feature is planned but not yet started |
| In Progress | "In Progress" — Feature is actively being developed |
| Done | "Done" — Feature is delivered |
Link Feature Requests
Roadmap items can be linked to Feature Requests:
- Open Feature Request → Change Status → Assign Roadmap Item
- Or: Open Roadmap Item → See Linked Requests
This way, you can see which customer wishes are behind a roadmap item.
Public View
The roadmap is accessible via a public endpoint:
GET /api/v1/public/roadmap/:tenantId
Only items with "Public = Yes" are displayed. You can integrate this URL into your website or set a link from the chat widget.
Control Visibility
- Public = Yes: Visible to everyone via the public endpoint
- Public = No: Only visible in the dashboard (for internal planning)
Tip: Only set items to "Public" when you are sure the feature will be delivered. Disappointed expectations do more harm than no information.
Best Practices
- Not too many items — 5–15 items on the public roadmap are ideal
- Keep status up to date — Outdated roadmaps appear unprofessional
- Celebrate "Done" — When a feature is complete, link it in the changelog