All guides
Reporting issues during alpha

Reporting issues during alpha

~2 min read

You're a co-builder, not a beta tester. Every time something feels wrong, that's a signal we can act on. The more you complain, the better Closr gets. There are two ways to reach us, and one of them is a button that's always on screen.

The Report Issue button

Look at the bottom-right of every Closr page (except Brief, where the chat input already takes that corner). There's a small amber button with "Report issue" on desktop, just the icon on mobile. Click it, a modal opens with a single textarea, type what happened, hit Send.

That's the whole thing. No category dropdown, no severity slider, no five-field form. One textarea. Ara reads them daily.

What to include

Three sentences usually beats five paragraphs.

  1. 1**What you were trying to do.** "I was trying to log a new APS for 142 Eastern."
  2. 2**What you saw.** "The deal card came back with the wrong closing date."
  3. 3**What you expected.** "It should have read October 4. That's what the PDF says."

Screenshots and short Loom-style videos are gold. Drop a CMD-Shift-4 (Mac) or Snipping Tool (Windows) screenshot, then paste a link to it in the textarea. If you can record a 20-second Loom showing the bug happening, that's the fastest possible bug write-up.

Closr also auto-captures the page URL you were on, your viewport (mobile or desktop), your browser, and the last five console errors. You don't need to include any of that yourself. Just describe what happened in your own words.

Where it goes

The form posts to `/api/feedback`. Two things happen.

  • •A Feedback row gets written to the database, keyed to your account.
  • •An email goes to `ara@getclosr.app` with your description, the auto-captured context, and your email as Reply-To. So if Ara hits reply, the message goes straight back to you.

You'll get a toast confirmation that says "Got it. We'll reply within 24 hours." That's a real number, not a corporate disclaimer.

For urgent things

If the app is fully down, your data looks wrong, or anything safety-related is happening, skip the button and email `ara@getclosr.app` directly. Same inbox, faster routing, full thread history.

The bar

The alpha invite said this, it bears repeating: don't be polite. If something looks ugly, say so. If a flow felt confusing, name the moment it broke for you. If you tried a thing five times and it kept doing the wrong thing, send all five attempts. Vague notes ("the contacts page is weird") are hard to act on. Specific notes ("the search box on the contacts page doesn't return matches for names with apostrophes") get fixed the same day.