Request a feature

Tell us the problem, not the button.

The best requests we’ve had described a moment in a room that went badly. We’d rather hear that than a feature name — it usually leads somewhere better than the button you had in mind.

WHAT HAPPENS NEXT

A person reads itWithin one working day. Not triaged by a form robot.

We may ask you one questionUsually “how often does this happen?” — it’s the difference between an annoyance and a blocker.

You get a straight answerBuilding it, thinking about it, or not doing it — and if it’s a no, the reason why.

If it ships, we tell youYou hear from us on the release, before you’d read about it in the notes.

Why there’s no public roadmap

A voting board rewards whoever has the biggest customer base, not the room with the worst problem. And a dated roadmap becomes a promise the moment someone screenshots it. So we answer each request directly instead — slower to read, more honest to hold.

SOMETHING BROKEN INSTEAD?

If a room is down, don’t use this form — it goes into the product queue, not the support one.

Go to support →

RECENTLY, FROM REQUESTS

The dock grip on medium displays — asked for by an integrator fitting 55-inch rooms.

Speed steps in replay, so a coach can skim a two-hour session.

“Kept with the board” retention, after a school asked who owns a replay.

Read the release notes →