Description
When you request a new feature or enhancement, it is essential for us to understand the business need and the impact that the lack of the feature is having on you and your customers.
Request a Feature
Submit a ticket with as much detail as possible to explain the feature. This information will be used to determine if a solution already exists or if we will provide it to our Product team for future consideration.
What to Include
Summary: A short, clear statement describing the requested feature.
Product: Provide the name of the product the feature request applies to.
Problem or Need: Explain what business issue or challenge this feature would address.
Proposed Solution: Describe what the feature should do and how it would function.
Use Case: Provide context of who would use the feature, when, and why.
Benefits / Value: Outline how this feature improves efficiency, accuracy, or user experience.
Current Workarounds: Note any temporary or manual solutions currently used, if applicable.
Supporting Details: Include screenshots, examples, screen mockups, or references to similar tools.
Priority / Impact Level: Indicate how critical this is. We suggest using the following choices:
Nice to have
Helpful improvement
High impact
Critical to workflow
What to Expect
A member of our Support team will work closely with you to gather all necessary information and fully understand the problem you are trying to solve. Mailprotector's development process is unique, and "feature requests" are looked at through a problem identification lens. It is important for the Support team to gather information that will help the Product team to understand the use case.
The Product team then determines potential solutions, which may often be incorporated into another existing feature or solved in another unexpected way. Please note that feature requests and use case submissions do not guarantee a solution or inclusion in future development cycles.
Related to
Updated