How to Submit a Feature Request

Paige is built to grow alongside the people who use it, and that only happens when we hear directly from you. Whether you're an end user managing your own legacy plan, a bank or channel partner supporting clients, or a fellow member of the Paige team, your perspective helps shape what we build next.

If there's something you'd love to see added or improved in Paige, the Feature Request Form is the best way to tell us. This article walks you through what the form asks for and how to fill it out.

Open the Feature Request Form

Table of Contents

Before you start
How to fill out the form
What happens after you submit

Before you start

Filling out the form only takes a couple of minutes, but a little prep makes your request easier for our team to evaluate. Before you begin, it helps to have:

• A clear picture of the problem you're trying to solve, not just the feature you're picturing. Telling us why something would help is often just as valuable as what you'd like to see.
• An idea of which part of Paige your request relates to (for example,Will Creation or Documents).
• Any specific examples or situations where the current experience fell short. Concrete details help our team understand the real-world impact. 

How to fill out the form

The form asks for a handful of fields. Here's what each one means and how to approach it.

1. First Name and Last Name (optional). These help us know who to thank, and who to follow up with if we have a clarifying question.
2. Email (required). Use an email address you check regularly, in case our team wants to learn more about your request.
3. Feature Request Name (required). A short summary of the improvement you'd like to see — think of this as a headline. For example, Add reminders for expiring passwords.
4. Feature Request Description (required). This is the heart of your request. Describe the improvement in as much detail as you can: what you'd like to happen, what happens today instead, and why the change would matter to you or the people you support. A best practice is to include a real scenario — walking through a specific moment where you needed this feature helps our team understand the full context.
5. Requestor (required). Let us know who's submitting the request: End User, Bank Partner, Channel Partner, or Other. This helps our team understand the perspective behind each idea.
6. Product Area (required). Choose the part of Paige your request relates to most closely: Will Creation, Documents, Passwords, Contacts, Business, Memories, Messages, Sharing Experience, Delegate Experience, User Experience, Profile / Settings, Dashboard, or Entire Platform. If your idea touches more than one area, choose whichever feels like the closest match.
7. Select Submit. 

What happens after you submit

Every feature request is reviewed by our team. We look closely at the merits of each idea, weighing the value it would bring against the time and effort it would take to build. This kind of thoughtful evaluation is a best practice because it helps us focus our energy on the changes that will make the biggest difference for the people who rely on Paige.

Because of this, we can't promise a specific timeline, and not every request will end up getting built. But every submission is read and genuinely considered, and your feedback helps inform how Paige continues to evolve.