Submitting a request
The fastest way to ask for new functionality is the + Request a feature button at the top of every page in the portal.
Step 1: Click + Request a feature
A small dialog opens with three fields.
Step 2: Title (required)
A short summary of what you want, up to 200 characters. Treat this like an email subject line, specific enough that someone scanning a list of titles understands the ask.
Tip: Good titles describe the outcome, not the implementation. “Filter season-pass holders out of the no-show report” reads better than “Add a checkbox to the report page”.
Step 3: Description (optional but recommended)
Up to 5,000 characters of context. The more concrete the better: who’s affected, when it’s needed, what alternatives you’ve already tried. Plain text; no formatting required.
Step 4: Priority
Pick how urgent the request is for your team:
| level | when to pick it |
|---|---|
| Urgent | Blocking work right now; you can’t ship without it. |
| High | Painful workaround in place; would unblock real value soon. |
| Medium | Default. Worth doing, no specific deadline. |
| Low | Nice to have, no rush. |
Note: This is your priority, the one we use to understand what matters most to you. It doesn’t change our internal engineering priority, our team will discuss timing with you.
Step 5: Send
Click Submit request. You’ll see a confirmation message:
Sent, our team will follow up with commercials.
The dialog closes after about a second. The request appears under Your requests in the right column of your roadmap shortly after.
What happens next
- Your account team is notified by email.
- A teammate reviews the request, asks any clarifying questions directly, and either schedules it on the roadmap or sends you a draft estimate for the work.
- If pricing applies, the estimate shows up in Billing → Awaiting approval for you to accept.
Note: Requests are visible to your account team only. They aren’t posted publicly or shared across customers.