Suggest New Features

Last Updated: October 24, 2025

Your ideas drive our innovation! We're committed to building features that matter most to our users. This page explains how to submit feature suggestions, what happens to your ideas, and how you can influence our product roadmap.

Why Your Ideas Matter

Building Together

Your suggestions help us:

• 🚀 Prioritize Development - Focus on features users actually need
• 💡 Innovate Better - Discover creative solutions to real problems
• 🎯 Serve You Better - Build products that match your workflow
• 📈 Stay Competitive - Keep pace with industry trends
• 🤝 Foster Community - Create a platform shaped by users

Our Track Record

Features Built from User Suggestions:

2024-2025 Highlights:

• ✅ Dark Mode - Requested by 456 users, shipped Q1 2025
• ✅ Bulk Email Actions - Requested by 234 users, shipped Q3 2024
• ✅ Advanced Search Filters - Requested by 189 users, shipped Q4 2024
• ✅ Email Templates - Requested by 321 users, shipped Q2 2025
• ✅ Two-Factor Authentication - Requested by 567 users, shipped Q2 2024
• ✅ Mobile Responsive Design - Requested by 892 users, shipped Q1 2024

In Development (Based on Your Votes):

• 🔨 AI-Powered Email Composer - 523 votes
• 🔨 Team Collaboration Tools - 412 votes
• 🔨 Calendar Integration - 389 votes
• 🔨 Email Scheduling - 367 votes

How to Submit Feature Suggestions

Feature Suggestion Portal

Access: ideas.pupam.com or Dashboard → Help → "Suggest Feature"

Step-by-Step Process

Sign In:

• Use your existing account credentials
• Or submit anonymously (limited tracking)

Search Existing Ideas:

• Check if someone already suggested it
• Vote for existing ideas instead of duplicating
• Add your use case in comments

Submit New Idea:

• Clear, descriptive title
• Detailed description of the feature
• Explain the problem it solves
• Describe how it would work
• Add mockups or examples (optional)
• Select category and priority

Track Your Submission:

• Receive confirmation email
• Get notifications on status updates
• See vote count and community discussion
• Receive notification when implemented

What Makes a Great Feature Suggestion

Essential Elements

Clear Title:

• ✅ Good: "Add ability to schedule emails for future sending"
• ❌ Poor: "Email thing"

Problem Statement:

• What problem are you trying to solve?
• How does this issue affect your workflow?
• How often do you encounter this problem?

Proposed Solution:

• Describe how the feature should work
• Include specific functionality
• Consider edge cases
• Think about user interface

Use Case Examples:

• Real-world scenarios
• Specific examples
• Target audience
• Expected benefits

Supporting Materials:

• Screenshots or mockups
• Links to similar features elsewhere
• Data or research supporting need
• User testimonials or feedback

Suggestion Template

Copy and use this template:

**Feature Title:** [Clear, descriptive name]

**Problem:**
[Describe the problem or pain point this addresses]

**Proposed Solution:**
[Explain how this feature would work]

**Use Case:**
[Provide specific example of how you'd use this]

**Benefits:**
- [Benefit 1]
- [Benefit 2]
- [Benefit 3]

**Priority:** [High / Medium / Low]

**Target Users:** [Who would benefit from this?]

**Similar Examples:** [Links to similar features in other products]

**Additional Notes:** [Any other relevant information]

Feature Suggestion Categories

Email Management Features

Examples of Suggestions:

• Email scheduling and delayed sending
• Smart folders and automatic categorization
• Advanced search with saved queries
• Bulk operations and batch actions
• Email threading improvements
• Read receipts and tracking
• Undo send with configurable delay
• Quick replies and canned responses

User Interface Enhancements

Examples of Suggestions:

• Dark mode and theme customization
• Customizable dashboard layouts
• Keyboard shortcuts and power user features
• Mobile app improvements
• Accessibility enhancements
• Multi-language support
• Font and display options
• Compact/comfortable view modes

Productivity Tools

Examples of Suggestions:

• Email templates and snippets
• Task management integration
• Calendar and scheduling features
• Note-taking capabilities
• Reminder and follow-up systems
• Email analytics and insights
• Time-saving automations
• Smart compose suggestions

Security Features

Examples of Suggestions:

• Additional authentication methods
• Encryption options
• Suspicious activity alerts
• Device management
• Session control
• Password policies
• Security audit logs
• Compliance features

Integration Requests

Examples of Suggestions:

• Third-party app integrations
• API enhancements
• Webhook capabilities
• CRM system connections
• Project management tools
• Cloud storage integration
• Communication platforms
• Marketing automation tools

Team & Collaboration

Examples of Suggestions:

• Shared mailboxes
• Team inbox features
• Collaborative email management
• Assignment and delegation
• Internal notes and comments
• Team performance metrics
• Role-based permissions
• Workflow automation

Voting and Prioritization

How Voting Works

Vote for Features

On Feature Portal:

• Browse all submitted ideas
• Click upvote (👍) on features you want
• One vote per user per feature
• Change or remove your vote anytime
• Add comments with your use case

Why Voting Matters:

• Shows demand for features
• Helps us prioritize development
• Demonstrates business value
• Validates problem importance
• Builds community consensus

Priority Tiers

Features are categorized by vote count:

Tier 1: High Priority (500+ votes)

Status: Actively planned for development

• Added to product roadmap
• Timeline communicated
• Progress updates provided
• Beta testing opportunities

Current High Priority:

• AI Email Composer (523 votes)
• Team Collaboration Tools (412 votes)

Tier 2: Medium Priority (100-499 votes)

Status: Under consideration

• Technical feasibility review
• Resource assessment
• Competitive analysis
• User research planned

Current Medium Priority:

• Calendar Integration (389 votes)
• Email Scheduling (367 votes)
• Advanced Analytics (298 votes)

Tier 3: Low Priority (25-99 votes)

Status: Tracked for future review

• Monitored for vote growth
• Combined with similar requests
• Evaluated quarterly
• May be implemented if aligned with strategy

Tier 4: Backlog (25 votes)

Status: Logged but not prioritized

• Kept for reference
• May gain traction over time
• Reviewed annually
• Can be closed if superseded

Feature Scoring

We evaluate features based on:

Impact Score (1-10):

• How many users benefit?
• How significant is the improvement?
• Does it solve a major pain point?
• Business value and revenue impact

Effort Score (1-10):

• Development complexity
• Required resources
• Technical dependencies
• Testing and QA requirements

Strategic Alignment (1-10):

• Fits product vision
• Market differentiation
• Competitive necessity
• Long-term value

Final Priority = (Impact × Strategic) / Effort

Feature Development Process

From Idea to Reality

Stage 1: Submission & Review (Week 1-2)

What Happens:

• Suggestion submitted and assigned ID
• Product team reviews for clarity
• May request additional information
• Similar ideas merged
• Initial categorization

Your Role:

• Respond to clarification requests
• Engage with community discussion
• Gather supporting data
• Rally votes from other users

Stage 2: Community Validation (Ongoing)

What Happens:

• Idea published to community
• Users vote and comment
• Product team monitors engagement
• Use cases collected
• Priority tier assigned

Your Role:

• Share with your network
• Provide detailed use cases
• Answer questions from other users
• Vote for related suggestions

Stage 3: Feasibility Analysis (2-4 weeks)

For features reaching consideration threshold:

Technical Assessment:

• Architecture review
• Integration requirements
• Performance impact
• Security considerations
• Scalability analysis

Business Evaluation:

• Cost-benefit analysis
• Resource availability
• Market research
• Competitive analysis
• ROI projection

Stage 4: Design & Specification (4-8 weeks)

For approved features:

Activities:

• User experience design
• Mockups and prototypes
• Technical specifications
• User testing
• Design iteration

Community Involvement:

• Design preview shared
• Feedback collected
• Beta testing signup
• Feature refinement

Stage 5: Development (6-16 weeks)

Engineering Process:

• Sprint planning
• Development work
• Code review
• Quality assurance
• Security testing
• Performance optimization

Updates Provided:

• Development status
• Expected timeline
• Preview access (for beta testers)
• Documentation preparation

Stage 6: Beta Testing (2-4 weeks)

Beta Program:

• Selected users get early access
• Feedback collected
• Issues identified and fixed
• Performance monitored
• Documentation refined

How to Participate:

• Sign up for beta program
• Test new features
• Report issues
• Provide feedback
• Suggest improvements

Stage 7: Launch (Week 1-2)

Release Process:

• Gradual rollout to all users
• Release notes published
• Tutorial content created
• Support team trained
• Monitoring and optimization

Post-Launch:

• Usage metrics tracked
• Feedback collected
• Quick iterations
• Success measured
• Thank you to contributors

Your Feature Suggestion Status

Tracking Your Ideas

Dashboard Access:

• Dashboard → Account → "My Feature Suggestions"
• View all your submitted ideas
• Check vote counts and comments
• See current status
• Edit or withdraw suggestions

Status Labels

🟡 Submitted

• Awaiting initial review
• Typically 1-2 weeks

🔵 Under Review

• Product team evaluating
• May request more information
• Typically 2-4 weeks

🟢 Planned

• Approved for development
• Added to roadmap
• Timeline communicated

🔨 In Development

• Engineering in progress
• Regular status updates
• Beta testing upcoming

🧪 Beta Testing

• Available to beta users
• Gathering feedback
• Near completion

✅ Shipped

• Released to all users
• Feature live and available
• Thank you recognition

⏸️ On Hold

• Paused for strategic reasons
• May be reconsidered later
• Explanation provided

❌ Not Planned

• Will not be implemented
• Reason explained
• Alternative solutions suggested

Feature Suggestion Best Practices

Do's ✅

Research First:

• ✅ Search existing suggestions
• ✅ Read product roadmap
• ✅ Check recent releases
• ✅ Review documentation

Be Specific:

• ✅ Clear problem statement
• ✅ Detailed solution description
• ✅ Concrete use cases
• ✅ Expected outcomes

Engage Constructively:

• ✅ Respond to questions
• ✅ Collaborate with others
• ✅ Accept feedback gracefully
• ✅ Update based on discussion

Think Big Picture:

• ✅ Consider all users
• ✅ Think about scalability
• ✅ Address edge cases
• ✅ Suggest alternatives

Don'ts ❌

Avoid These Mistakes:

• ❌ Duplicate submissions
• ❌ Vague or unclear descriptions
• ❌ Demanding immediate implementation
• ❌ Being rude or aggressive
• ❌ Suggesting illegal features
• ❌ Ignoring feedback
• ❌ Spamming or vote manipulation

Feature Request Examples

Excellent Suggestion Example ✅

**Title:** Add Email Scheduling for Future Delivery

**Problem:**
I often write emails late at night but don't want to send them 
outside business hours. Currently, I have to save drafts and 
remember to send them later, which is inefficient and error-prone.

**Proposed Solution:**
Add a "Schedule Send" button next to the regular Send button. 
Clicking it opens a date/time picker where I can select when 
the email should be sent. The email would be saved and 
automatically sent at the specified time.

**Use Case:**
1. Marketing team wants to send newsletters at optimal times
2. Sales reps in different timezones want to respect local hours
3. Managers want to send emails during business hours even when 
   working evenings
4. Users want to queue multiple emails for strategic timing

**Benefits:**
- Improved work-life balance
- Better email deliverability
- Professional communication timing
- Reduced cognitive load (don't have to remember)

**Priority:** High

**Target Users:** All users, especially:
- Marketing teams
- Sales professionals
- Global teams across timezones
- Individual power users

**Similar Examples:**
- Gmail's "Schedule Send" feature
- Outlook's "Delay Delivery"
- Superhuman's "Send Later"

**Additional Notes:**
Should include:
- Calendar view for selection
- Timezone awareness
- Ability to edit scheduled emails
- Option to send immediately if needed
- Mobile app support

Poor Suggestion Example ❌

**Title:** Make emails better

**Problem:** Emails are hard

**Solution:** Just fix it

**Use Case:** Everyone needs this

**Priority:** URGENT!!!

Why It's Poor:

• Vague and unclear
• No specific problem described
• No concrete solution
• No real use cases
• Demanding tone

Recognition and Rewards

Contributor Recognition

Feature Champion Badge:

• Awarded for implemented suggestions
• Displayed on your profile
• Community recognition
• Special perks and benefits

Innovation Leaderboard:

• Top contributors by votes received
• Most implemented suggestions
• Most active participants
• Monthly and annual rankings

Rewards Program

For Implemented Features:

Tier 1: Minor Features

• Public thank you in release notes
• Feature Champion badge
• 1 month free premium upgrade
• Early access to future features

Tier 2: Major Features

• Feature named after you (optional)
• 6 months free premium upgrade
• Exclusive swag package
• Beta tester privileges for 1 year
• Direct line to product team

Tier 3: Game-Changing Features

• Annual free premium subscription
• Invitation to product advisory board
• Public recognition (blog post, social media)
• Exclusive event invitation
• Lifetime beta access

Top Contributors

Hall of Fame (2024-2025):

🏆 Sarah Chen - 12 implemented features, 5,234 total votes 🥈 Michael Rodriguez - 8 implemented features, 3,891 total votes 🥉 Aisha Patel - 7 implemented features, 3,456 total votes

Public Roadmap

See What's Coming

Access: roadmap.pupam.com

Roadmap Includes:

• Currently in development
• Planned for next quarter
• Under consideration
• Recently shipped
• Beta testing opportunities

Transparency:

• Feature status updates
• Expected timelines
• Development progress
• Blockers or delays
• Community-driven prioritization

Frequently Asked Questions

How long does it take for a feature to be implemented?

It varies greatly:

• Small features: 1-3 months
• Medium features: 3-6 months
• Large features: 6-12+ months

Priority, complexity, and resources all affect timeline.

Can I suggest multiple features?

Yes! Submit as many ideas as you like. However, focus on quality over quantity. Well-thought-out suggestions get more traction.

What if my feature doesn't get votes?

Not all features resonate with the broader community. Consider:

• Is there a different way to frame the problem?
• Could it be combined with other suggestions?
• Is it too niche for the general user base?
• Might it work better as a plugin or integration?

Can I work with your team on feature design?

Absolutely! For high-priority features, we often involve suggesting users in the design process. We'll reach out if we'd like your input.

Why was my suggestion marked "Not Planned"?

Reasons include:

• Doesn't align with product strategy
• Technical limitations or impossibilities
• Security or privacy concerns
• Too costly relative to benefit
• Better alternative solution exists

We always provide explanation.

Can I suggest removing a feature?

Yes! Submit removal suggestions if features are:

• Rarely used
• Causing confusion
• Making product complicated
• Better replaced with something else

Do employees' suggestions get priority?

No. All suggestions are evaluated equally based on merit, votes, and strategic alignment.

Contact the Product Team

Feature Suggestion Support

General Questions:

• Email: features@pupam.com
• Portal: ideas.pupam.com
• Response Time: 2-3 business days

Product Management

Complex or Strategic Ideas:

• Email: product@pupam.com
• Schedule Call: Book 30-min session
• Partnership Proposals: partnerships@pupam.com

Join Our Community

Product Community:

• Forum: community.pupam.com/features
• Discord: #feature-requests channel
• Monthly Calls: First Tuesday, 2pm EST
• Newsletter: Product updates and roadmap

Get Started

Ready to Share Your Ideas?

Submit Your First Feature:

1. Visit ideas.pupam.com
2. Search existing ideas
3. Submit new suggestion
4. Rally votes and engagement
5. Track progress and updates

Need Inspiration?

• Browse existing suggestions
• Read our product blog
• Join community discussions
• Review our roadmap
• Talk to other users

Your ideas shape our future. Every great feature starts with a user suggestion. Don't hesitate to share your thoughts—we're listening!

Submit Feature Suggestion → ideas.pupam.com