Back to Help Center
Troubleshooting

Submit a feature request product can act on

Make feedback easier to evaluate by explaining the job, the workaround, the impact, and a concrete example.

4 min readUpdated Jun 22, 2026
Submit requestAsk support
Audience

Hosts, attendees, and collaborators who want to suggest product improvements.

User need

I want to request a feature and make it useful for the product team.

Use this page before sending product feedback

A useful feature request helps the product team understand the real problem. A vague request like add more options is hard to evaluate.

A better request explains who needs the feature, what they are trying to do, what happens today, why the workaround is painful, and what outcome would help.

Write a useful feature request

1

Name the workflow

Say whether the request is about creating events, templates, publishing, registrations, payments, check-in, recaps, analytics, or support.

2

Describe the job

Explain what you are trying to accomplish in plain language.

3

Explain the current workaround

Tell us what you do today and why it is slow, confusing, risky, or impossible.

4

Add impact

Mention whether the issue affects publishing, registrations, paid tickets, attendee trust, event-day operations, or repeat hosting.

5

Include a safe example

Share an event link or anonymized example when useful, but do not include private attendee or payment details.

Good request format

Part
Example
Workflow
I am managing registrations for a capacity-limited workshop.
Job
I need to move one waitlisted person into a confirmed spot after a cancellation.
Workaround
Right now I export the list and track it manually, which is error-prone.
Impact
This affects event-day confidence and attendee communication.

Best feature requests are concrete

A specific user job with a real example is more useful than a broad request for more customization.

FAQ

Will every feature request be built?

No. Requests help the team understand needs and prioritize, but they do not guarantee a specific build timeline.

Should I send screenshots?

Only if they are safe and redacted. Avoid exposing attendee, payment, identity, or private account data.

What if the issue is a bug, not a feature request?

Use the bug report path and include expected result, actual result, page, event link, and visible error.

Related guides

Troubleshooting5 min read

Ask AI support or report a bug

Clear support requests are faster to diagnose. Include the route, event context, expected result, and actual result.

Read guide
Troubleshooting4 min read

What the AI support assistant can help with

AI support is best for guidance and triage. Sensitive account, payment, and data requests may need human review.

Read guide
Troubleshooting6 min read

Troubleshoot attendee registration problems

Registration issues usually come from capacity, closed registration, form validation, payment state, or link problems.

Read guide