Introduction
The Product Ideas Portal is our dedicated space for you to share your vision for TripBuilder and help us improve the platform. We believe that our expert users, you, know best what features will bring the most value to your daily operations and business.
This portal is not customer-specific; it is a shared space for the entire TripBuilder Community. By connecting expert users (Tour Operators and Admins) from various organizations, we can identify the most impactful features and enhance TripBuilder together.
Who can access this? Access is strictly reserved for users with TourOperator or CompanyAdmin roles within TripBuilder.
Accessing the Portal
If you hold the required permissions, there are three ways to access the portal:
Account Menu: Open the user dropdown menu in the top navigation bar.
Dashboard: Look for the "Product Ideas" tile on your main dashboard.
Direct Link: Navigate to
/ideason your specific TripBuilder instance URL.
Community Guidelines & Philosophy
This portal is designed to foster collaboration and discovery. To maintain a productive environment, we ask that you adhere to the following policy:
Be Constructive: Focus on solutions and forward-looking improvements.
Be Respectful: Respect the differing opinions and workflows of other community members.
No Bug Reports: Please continue to send bugs or urgent technical issues directly to our Support Team. This portal is exclusively for feature requests and improvements.
Note: Nezasa reserves the right to reject ideas or remove comments that violate these guidelines. Repeated violations may result in a user being blocked from the community portal.
How to Contribute
1. Views
The ideas portal comes with two section:
Share Ideas: a flat list of all ideas. It is searchable and filterable. This is also the view where you can share new ideas.
Community Ideas: this is a Kanban-like board of all ideas with columns for the different states of ideas:
Submitted: newly submitted ideas by users.
Under Consideration: ideas that were already looked at by the team.
Planner: ideas that have been picked up in our planning and thus, we are working on.
Released: ideas that we have launched already.
2. Sharing a New Idea
Have a feature in mind? Check first if it already exists in the search bar. If not, click the "Share Idea" button.
To help our Product Team understand your request, please provide the following details:
Use Case: Describe the specific scenario where this feature is needed.
User Value: Explain how this improves your workflow or business potential.
Categorization: Select the matching Product Area and 3rd-party integration (if applicable).
3. Voting on Ideas
If you see an idea you like, cast your Vote. Upvoting helps us identify the most popular requests across the entire user base.
4. Adding Context (Impact Feedback)
Beyond a simple vote, you can provide detailed feedback on your own ideas or ideas submitted by others. You may be asked three specific questions to help us gauge impact:
Usage Frequency: How often would you use this feature?
Urgency: How critical is this for your current operations?
Importance: How much value does this add to your business?
Example:
5. Commenting
Join the discussion by commenting on ideas. You can clarify requirements, add alternative viewpoints, or support the original author.
Note: Nezasa may update the original idea description to incorporate valuable insights from the comment section.
The Moderation Process
To ensure clarity and prevent duplicates, all new ideas undergo a review process by Nezasa.
Approval: We review every submission. We may edit the title or description to ensure it is easily understood by the wider community.
Timeline: Approval typically takes a few days, depending on submission volume.
Frequently Asked Questions (FAQ)
When will an idea be picked up for development?
We closely monitor ideas that have high engagement - specifically those with a high number of votes and feedback from multiple different companies. These have a higher chance of being prioritized by our Product Team. However, please note that there is no guarantee; every idea must also align with our broader product strategy and technical roadmap.
Why was my idea rejected or closed?
If an idea is closed, it is usually due to one of the following reasons:
Low Engagement: The idea did not receive significant votes over a considerable period.
Strategy Mismatch: The request does not align with the current product vision.
Wrong Channel: It was a bug report or support complaint (please send these to Support).
Merged: It was merged with a similar, existing idea. This is a positive outcome! Merging consolidates votes and focuses attention on a single entry.