Share your product feedback!

Please tell us what we can do to make Featurebase the best product for you.

Custom feedback scoring setups

There should be 1 simple way to set up the scoring method you prefer using custom post fields. Custom fields can be both public and internal, making them the perfect choice for them. We also already support number custom fields. To make them support different scoring setups like RICE, User impact score, and more, we should have these: Custom post fields visible in the dashboard view Sort based on custom fields There should be a way to set up an equation field that calculates the final value based on your inputted equation (be it RICE, Value/effort, etc.) This would make very comprehensive scoring setups possible, both customer-facing and internal, or both.

Markus from Featurebase About 1 month ago

3

Feedback & Roadmaps

HubSpot bidirectional custom field sync (for tickets & deals)

Enable full, bidirectional sync of key HubSpot custom fields between tickets/deals and Featurebase, so all teams see the same structured data in either tool. Problem Current integration only shows a link + basic widget in HubSpot No detailed hubspot ticket/deal fields are synced to Featurebase; users must click out to see context Many internal users don’t have HubSpot access, so Featurebase users miss the structured info captured there. Product/engineering working in Featurebase can’t see fields like impact, use case, product area, retention/upsell context. Syncing these fields so teams can see them in both tools would solve the core use case for such integration and give teams a single source of truth across HubSpot and Featurebase. It would reduce tool‑switching and eliminates need for everyone to have access to both tools.

Markus from Featurebase 29 days ago

Feedback & Roadmaps

Support 301/302 Redirects for Language-Prefixed Help Center URLs to Prevent Duplicate Indexing

When per-language settings are enabled in the Help Center, articles are accessible via both language-prefixed and non-prefixed URL structures (e.g., /articles/... and /en/articles/...). Currently, both versions return HTTP 200 with identical content, which can lead to duplicate indexing in search enginesβ€”even if canonical tags point to the language-prefixed version. This behavior may split ranking signals, impressions, and backlink equity across duplicate URLs, negatively impacting SEO performance. Instead, only one URL variant should return HTTP 200, and the alternate variant should 301 (or 302) redirect directly to the designated locale-specific URL (e.g., /articles/... β†’ /en/articles/..., or vice versa). This ensures a single authoritative, indexable URL per article per locale while consolidating ranking signals and preserving backlink equity.

Team HelloShift About 11 hours ago

Help Center

Next

Email replies create new conversations instead of threading

When a customer replies to an existing support email, Featurebase creates a new conversation instead of continuing the original thread. This fragments discussions, duplicates issues, and makes reporting and tracking harder. Even when replying directly to the Featurebase parse address, the reply does not attach to the original conversation and instead creates a new one. Email replies should automatically continue the existing conversation using standard email threading logic, so each issue stays in a single unified thread. To rule out our email routing setup, I tested by emailing your parse address directly (67bf384531699adad8f294e6@parse.featurebase-mail.com), received the reply from Featurebase, and replied back from my email client. It still created a brand new conversation rather than continuing the existing thread. So the issue appears to be on the Featurebase side rather than our DNS or Google Workspace routing.

Axel Molist Cordina 1 day ago

Support platform