Back
Product

we closed the loop

people asked. we shipped. now they get an email. comments on the card, a note for the team, and a ping when it actually goes out.

Jessé Cruz 4 min read

people vote. you ship. nobody hears about it.

that's the whole bug. not the roadmap. not the board. the silence after.

so i shipped the missing half.

comments stay on the card

every card now has a thread.

you can reply in public. the person who asked sees it on the board.

you can leave an internal note. only the team sees that one. triage stays private. the customer never has to.

newest first. form stuck at the bottom. the conversation doesn't bury the write box.

the agent can do this too. add-comment and list-comments are on the mcp server. you don't even have to open the tab.

guests don't post. on purpose.

i turned guest comments off.

an open form on a public board is a spam machine. votes already measure demand. i don't need a flood of "me too" from emails we never verified.

the team talks. the board shows the public replies. that's enough for now.

then we tell them it shipped

this is the part that actually matters.

when a card moves to done — from the board or from publish-changelog — hoot emails:

  • the person who submitted it
  • everyone who voted for it

one mail. "this thing you asked for just shipped." link to the changelog if you have one. link to the board if you don't.

no more "did we tell them?"

the loop is: they ask → you build → they hear about it.

that's it. that's the product.

why this and not ten other features

i don't need more columns.

i need the person who voted last month to find out we actually did the thing.

comments make the wait less dead. the email makes the ship real.

if you're already on hoot, open a card. leave a note. mark something done. check your inbox.

if you're not: usehoot.app

ask. ship. tell them. 🦉

Related