This guide is meant to serve as a living document to help you, the ScopeStack user, utilize the Feature Request Forum in the most effective way possible.
Make a feature request here: https://feedback.scopestack.io/
What the Feature Request Forum is for:
The ScopeStack Feature Request Forum is a place for ScopeStack users to discuss feature requests with each other and the ScopeStack Product Team. We want you to tell us what features you'd like built! It’s our goal to make the feedback process as streamlined as possible for both ScopeStack users and our product team.
What the Feature Request Forum is not for:
- Requesting features that already exist — If a feature exists in any ScopeStack subscription, that feature is considered delivered. Threads requesting it be available at a different subscription will be removed.
- Discussing how to use features and capabilities — ScopeStack KB is home to numerous resources dedicated to discussing how to utilize existing features.
- It is not a Support Forum — ScopeStack Support works around the clock to provide users with the know-how to best utilize their account. As the Feature Request Forum is not the appropriate medium to ask questions on how to utilize existing features, threads that are better directed to ScopeStack Support will be removed.
- It is not a Product Roadmap — While we continually update the statuses of Feature Requests in order to give our users a timeline of a feature’s development, there may arise instances where a feature’s development might have to be paused, or set aside. Unfortunately, unexpected roadblocks do arise, and we’d much rather be honest with our users and let them know if the development status has changed. For this reason, a thread’s status should not be viewed as set in stone, but rather a reflection of the current development plan.
Customer FAQs
I see each Feature Request has a status, what do they mean?
- Idea Submitted — Your Idea has been submitted to the ScopeStack Feature Request Forum. Help bring it to our Product team’s attention by socializing it with others.
- Being Reviewed — This feature request has been reviewed by our Product team and is currently being evaluated. All updates will be communicated on this thread.
- In Planning — This feature request is actively being developed. Stay tuned, as all updates about this feature will be shared through this thread. With “In Planning,” no news can be good news. We’re busy developing the boring back end stuff, but all the fun and exciting updates you should know will be communicated through this thread.
- In Beta — This feature is currently in Beta. If you are interested in testing Beta features, please reach out to support@scopestack.io.
- Delivered — The feature is live in all portals with the proper subscription
- Not Currently Planned — At this time the Product team has no plans to develop this feature. “Not Currently Planned” doesn’t mean that the feature will never be developed, just that we don’t have plans to do it at this time, so feel free to upvote and leave your feedback. Any updates regarding this feature will be communicated through this thread.
How can I get my feature request to the Product team as quickly as possible?
Before creating a new request, search the Feature Request Forum for an already-existing thread that requests the same feature. The Feature Request Forum hosts hundreds of threads, so it is highly likely that a similar request has already been posted on the forum. By upvoting an already-existing thread, you are consolidating your interest in a particular feature for our Product team, which helps us identify it as a popular feature request.
What if there isn’t a thread that requests my Feature?
If you’ve searched the Feature Request Forum and haven’t seen a thread for your Idea, then it’s time to create one!
When writing your request, be as specific as possible. For example, instead of saying “better email tracking,” say “the ability to track how many recipients opened a Marketing Email on Monday morning.” This is much easier for our Product team to understand and focus on.
Structure your Idea in the form of a user story so other ScopeStack users can relate to it. Instead of saying “I need a list of every teacher in Boston to be automatically created,” say “I’d like the ability to automatically create lists based on location and profession.” This helps other users relate to your Feature, which means it is much more likely to receive upvotes. Similarly, the more our Product Team knows about an Idea – who it’s for, what the motivation is, and what the actual item is, the more accurate they can be when it comes time to prioritize and scope it.
By constructing your idea in the following format, you will help our product team understand your feature request.
- Title: Briefly state the desired capability to help our Product team locate your feedback
- Desired Capability: What is the ScopeStack feature you would like to see to help you reach this goal?
- Goal: What would you like to accomplish?
- Use Case: How does this goal play into your business’s operation?
- Images: Screenshots help us better understand your Idea
Example:
“I want ScopeStack to fold my laundry”
- Desired Capability: At 4 pm every day, I’d like ScopeStack to send a message saying “do you want us to fold your laundry?” If I click “Yes,” I’d like the system to connect to my dry and fold my laundry.
- Goal: I’d like to come after work and have my laundry folded in the hamper.
- Use Case: After a long day of work, the last thing I want to do is come home and have to do more work by folding my laundry. ScopeStack automates a lot of my services scoping functions, I’d like it to automate my laundry folding as well.
Note: Each Feature Request Forum thread should only request one feature. If there are multiple feature requests in one thread, it creates confusion when attempting to communicate the developments of one of the features.
When can I expect to hear back from ScopeStack?
If there is relevant information pertaining to the substance of the thread, it will be provided by a comment from a ScopeStack team member. As the Feature Request Forum is being actively moderated, it is safe to assume that if a thread hasn’t been commented upon, the state of a feature request is best reflected through its status.
How long does it take for my Feature to get built?
It entirely depends on the traction your Feature receives from other users and the feasibility of the feature request. While the general rule is that the more popular a thread, the more likely it is to receive consideration from our Product team, this is not a certainty. A Feature may receive a high amount of upvotes, but if the feature isn’t able to be produced due to a technical, ethical, or legal reason, no amount of upvotes will be able to change that. That being said, sometimes our Product team finds a unique Feature with only a handful of upvotes and decides to move it into development.
Why isn’t there a date saying when a Feature will be delivered?
The status “In Planning” means your feature request is actively being worked on. However, as a rule, we never provide specific dates for when you can expect that feature to be in beta or live. To best serve users like you, we need to maintain flexibility in our product development process, including how and when we role features out. This ensures we meet your expectations and deliver great products that solve your needs today and in the future.
See you on the forum!
ScopeStack Product Team