New Feature Requests
Use this process to submit enhancement suggestions or entirely new capability requests to the product team.
When to Raise a New Feature Request
- A client repeatedly asks for a capability that does not exist on the platform
- The current workflow requires a manual workaround that could be automated
- A competitor platform has a feature that would significantly benefit clients
How to Submit
- Check if the feature has already been requested — search the Internal Feature Tracker to avoid duplicates
- If new, raise a CFR (Customer Feature Request) with:
- Client Org ID(s) requesting the feature
- Feature description — what it does and why it's needed
- Business impact — how many clients would benefit, estimated revenue impact
- Priority — Low / Medium / High
- The product team reviews CFRs in the weekly sprint planning session
- You will be notified of the decision (Accepted / Deferred / Rejected) within 5 business days
info
Accepted feature requests go into the product backlog. Timeline for delivery depends on sprint priority — do not commit delivery dates to clients without confirmation from the product team.