Aha! the Ideas Portal is your space to share, vote on, and track ideas that can shape the future of PaymentWorks. Below, you’ll find answers to common questions about accessing and using the Ideas Portal.
Access to the Aha! Ideas Portal
How many of my users can access Aha!?
Each PaymentWorks customer is allowed two (2) user accounts for the Aha! Ideas Portal. This ensures all customers are represented equally and allows the PaymentWorks Product Team to fairly review ideas across our customer base.
Why are only two (2) users allowed per customer?
Limiting access to two users per customer helps our Product Team manage submissions effectively while allowing every customer to contribute ideas. We recommend that users vet and gather feedback from their organization before submitting ideas.
How do I add, edit, or remove Aha! users?
Submit a support ticket to request changes to your organization’s Aha! Ideas Portal users. If you need to add a user beyond the two-user limit, you’ll need to remove an existing user.
Aha! Ideas: Add, Vote, and Track
What types of ideas should I submit?
The Ideas Portal is designed for suggestions to improve PaymentWorks, including:
- Enhancements to user experience
- Closing functionality gaps
- Proposing new platform features
⚠️ Note: Issues like defects or bugs should be reported through the support team, not the Ideas Portal.
Will I receive updates on ideas I submit or vote on?
Yes! You’ll automatically be subscribed to updates for any idea you submit or vote on. This includes status changes or comments. You can unsubscribe at any time.
When will my idea be implemented?
The PaymentWorks Product Team evaluates ideas based on:
- Business/User Value
- Alignment with Product Strategy
- Feasibility
If more details are needed, the Product Team may contact you or leave comments requesting additional information.
Understanding Aha! Idea Statuses
Here’s what the statuses in the Aha! Ideas Portal mean:
| Status | Description |
|---|---|
| Evaluating the Request | The idea is under review. More votes could increase priority based on potential reach, impact, or interest. |
| Initial Review Complete | The Product Team has reviewed the idea. Sub-statuses include: |
| - Promoted for Further Review | The idea seems promising and will undergo further exploration. |
| - Unlikely to Implement | The idea does not align with product strategy, lacks clear value, or is not feasible. |
| - Need More Info | Additional information is needed from submitters or supporters to decide on implementation. |
| Intend to Build - Awaiting Prioritization | The idea will likely be implemented in the future but is not yet prioritized or scheduled. |
| Already Exists | The requested functionality already exists in the PaymentWorks application. |
| Will Not Implement | The idea will not be implemented due to misalignment with strategy, low value, feasibility concerns, or obsolescence. |
| Planned - Committed to Roadmap | The idea is prioritized for implementation within the next 3-6 months. |
| Shipped | The idea has been implemented and is now available. |