Inbox Cardinal

The feedback loop

Feedback that comes back.

Most feedback forms are where ideas go to be thanked and forgotten. Inbox Cardinal is built around the opposite: a loop that starts with your report and doesn’t close until you say the problem is gone.

Every Cardinal product ships with this loop. It isn’t a support channel bolted on at the end. It is how the products get built.

Five steps, one promise: nothing disappears.

Say it where it happened.

A small form inside Inbox Cardinal: bug, idea, or question, one text box, an optional screenshot. Fifteen seconds. The app attaches the technical context (version, where you were, what just happened) so you never have to write a support essay. Spot a message the score got wrong? Report it without leaving your feed.

It gets read. Every time. And a person makes every call.

Every report is read, and every decision about it is made by a person. Nothing you send can be auto-declined, auto-closed, or quietly dropped: build, decline, or defer is always a human call. That’s why the form doesn’t promise you an outcome. We promise you a reading, an honest answer, and human judgment, because those are promises we can keep every single time.

The roadmap tells the truth.

Inside the app, the roadmap shows everything we’ve committed attention to, in four stages: Under consideration → Planned → In progress → Shipped. Stages, never dates: dates create promises a small team shouldn’t make; stages create transparency without hostages. You can vote on what matters to you, right in the app: one person, one vote. Whether you connect two inboxes or ten, you speak once, so votes measure how many people need something, not how loudly anyone asks. Votes rank our attention. They never rule it. And when the answer is no, you get the no, with the reason. “Not now” means parked and revisited, not quietly forgotten.

We ask before we fix.

If your report can be read two ways, we don’t guess. We ask, in the app and by email, before anything gets built. Fixing the wrong thing fast is still fixing the wrong thing.

You hear back. And you get the last word.

When the thing you reported goes live, you get an email saying exactly that. If ten people reported it, all ten hear. And that email asks one question: did this fix what you reported? One tap, yes or no. A “no” reopens the report at the top of the pile, because the only person qualified to say the loop is closed is you.

A “no” at step five starts the loop again at step one. That is what makes it a loop.

The rules we hold ourselves to.

Every report is read.

Not sampled, not lost in a queue, and nothing is ever auto-declined. Every decision is made by a person.

Stages, never dates.

The roadmap shows where things stand, not deadlines we’d have to break.

One person, one vote.

Whether you connect two inboxes or ten, you speak once.

Votes rank, never rule.

Voting orders our attention; judgment decides. We will ship an unglamorous fix ahead of a popular wish when the product needs it.

A “no” comes with a reason.

Declining your idea to your face costs us a sentence. Silence would cost you months of false hope.

Your words, never your data.

A report carries your description of the problem, never the content it happened in. Personal details are stripped before a report is stored. More on our Trust page.

Not a feature. The way Cardinal is built.

Every product in the Cardinal family ships with this exact loop from day one: same form, same four stages, same shipped-it email, same last word. Inbox Cardinal runs it today, in beta, which means beta users aren’t testers. They’re the people steering.

We run it this way because the loop is the development process, not a suggestion box beside it. The distance between “a user noticed” and “the product changed” is the number we care about most, and the loop is how we keep it short without ever letting speed outrank honesty.

“We won’t promise you an outcome. We promise you a reading, an honest answer, and the last word.”

Honest answers to the fair questions

Do you really read everything?
Yes. Every report is read, and no decision about one is ever made by anything but a person. Nothing gets auto-declined or quietly closed; build, decline, or defer is always a human call. The moment that stops being true we’d have to take this page down, which is the point of publishing it.
Why won’t you give dates?
Because a date on a roadmap is a promise, and we don’t make promises we can’t be certain of keeping. Stages tell you the truth about where a thing stands right now. That’s more honest than a date that slips.
What happens to my personal information?
Your report is stored as your description of the problem plus technical context. Personal details are stripped before storage, and the content your report happened in (your actual messages) is never included. The same commitments as everything else here: we never train AI models on your content, and disconnect means delete. See the Trust page.
What if you decide not to build my idea?
Then you’ll hear that, with the reason. Some ideas get a “not now” and a place in the parking lot we revisit; some get a clear no. Either way you won’t be left checking the roadmap for a ghost.
Can I see the roadmap without signing in?
No. The roadmap lives inside the app. It’s a benefit for the people whose reports and votes shape it, not a marketing page. This page is the public half: the rules, so you know how you’ll be treated before you ever file a report.

The fastest way to shape it is to be in it.

Inbox Cardinal is in beta, and the loop above is live. Beta users’ reports are already becoming the product.

Join the beta

Questions first? hello@inboxcardinal.com