Feedback and Nest

Feedback from visitors

• The maker turns feedback on per drop in the Sharing window, under "For visitors". It is off by default. On a drop with Password access it switches on directly. On an open drop (anyone with the link) Toolcrow first asks the maker to confirm, because then people they don't know can send feedback too; for a known group, Password access is usually the better fit.
• When it is on, visitors see a "Feedback" button (a speech bubble) in the small white Toolcrow pill in the bottom right corner of the drop, next to "What's new" (see below), the Toolcrow crow and, on open drops, the share button. Visitors can drag the pill elsewhere by its grip. They pick a category (bug, idea, unclear, love or other), write a message or attach screenshots, and can leave their name and email. No account is needed. The pill speaks the drop's language (English or Dutch) and stays out of the way of the drop's own buttons.
• The button never appears on private drops, and the maker does not see it on their own drop.
• Submissions are rate-limited per drop, per hour and per day, against spam.

What's new and "your report is fixed"

• Next to Feedback, visitors can see a What's new button with short notes about what changed in the drop, newest first. A small blue dot on the button means there is a note they have not seen yet. A first-time visitor gets no dot for older notes.
• The notes come from the maker: when publishing a new version, the side panel and "Upload new version" have a field "Note for your visitors". In the side panel it sits right under "What your AI changed" (the explanation for the maker), so it is clear which text visitors see. The maker's AI can suggest the sentence when it prepares a draft; the maker edits it or leaves it empty. Publishing is the approval of the note. Empty means that version gets no note. In the Versions panel of the drop page (click the version in the header) the maker sees the note of each version in a table and can remove one.
• What's new is part of Pro. It is off by default; the maker switches it on per drop in the Sharing window, under "For visitors" ("What's new"). When What's new is still off and the maker publishes with a note, Toolcrow asks once, showing the exact note: "Publish and show to visitors" turns What's new on and publishes, "Publish without the note" publishes the update without a note and leaves What's new off. The button only appears once there is at least one note. Never on private drops.
• The pill only appears when there is something in it. If a drop's code wipes the page after it has loaded, Toolcrow puts the pill back.
• A visitor who sent feedback keeps a receipt in that browser, for that drop only. When the report is fixed (by a published update that closes it, or by "Mark as fixed"), the visitor sees a small card "Fixed: what you reported" with their own words the next time they open the drop, once. In What's new the note of that version is marked "You reported this". Reports closed without a fix show nothing.
• This works without accounts or emails, so it only works in the same browser on the same device. Visitors who clear their browser data or switch devices do not see it.
• "Restore" (see Versions, backups and drafts) hides the notes of the versions it rolls back, and a report fixed in such a version no longer shows as fixed to the visitor. The same report is open again in Nest, so the maker and the visitor see the same thing.

What Toolcrow watches, and what it can't see

• Toolcrow watches a connected Google Sheet (the connection and the file, every morning and each time the tool saves to it) a drop's built-in database (whether it is full) and forwarding to a webhook (whether messages arrive). It also notices a form that saves nothing. When something breaks it says so in Nest (below); see Saving data.
• Toolcrow doesn't warn yet about errors on the page in visitors' browsers, the libraries a drop loads, or AI requests. No warning about those doesn't mean all is well.
• Toolcrow can't see the services a drop calls itself from the visitor's browser, what is inside a Google Sheet, what visitors keep in their own browser, whether an AI answer is right, or what a service does with a message after it arrives. Things only a person notices, like a button that does nothing, come in through feedback.

Nest: one place for everything that needs the maker

• Nest (/nest, in the sidebar) is the one list of everything around the maker's drops. It has four kinds of items:
• Problem: Toolcrow noticed something broken by itself that loses what people send: a Google connection that stopped working, a connected Google Sheet that was deleted, moved to the trash or can no longer be edited, or a drop whose built-in storage is full (see Saving data). It also tells the maker when messages to a webhook stop arriving; the submissions themselves are saved, so that one is marked "Needs a look" instead of "Broken" and comes without an email. One problem is one item, however often it happens. Toolcrow checks first that the problem is real, so a short hiccup does not show up here.
• Feedback: one item per report from a visitor.
• Request: someone is waiting on the maker, for example a visitor who asked to turn a switched-off drop back on.
• Update: the maker's AI (or Toolcrow) prepared a new version that is waiting to be checked (see Versions, backups and drafts).
• The list can be filtered on Needs you (exactly what the counter counts), All, Problems, Feedback, Requests and Done, and on one drop. Nest opens on Needs you. From a drop page, "Open in Nest" in the Usage panel opens the list for that drop only, and the home page of the app shows the top 3 under "Needs you", with a link to the rest in Nest. Publishing never happens from the home page: "Check update" opens the drop page, where the maker reviews the update first.
• Selecting an item shows it on the right: what the visitor wrote (with the browser and device it came from, and any screenshots) or what Toolcrow noticed, what Toolcrow suggests, and one next step: "Fix with your AI", "Check update", "Reconnect Google", "Choose a Sheet", "Open Google Drive trash", "Make room", "Check webhook" or "Turn back on".
• Status is simple: an item is open, fixed (with the date, for example "Fixed on Oct 22") or closed without a fix. A report is fixed by publishing an update that fixes it, or by "Mark as fixed". "Dismiss" closes it without a fix; closed items can be reopened.
• The orange counter in the sidebar counts only what needs the maker: bug reports, problems, requests and waiting updates. Ideas, questions and love are in the list but do not count.

What Toolcrow suggests

• When a report comes in, Toolcrow's AI reads the open reports of that drop together with the drop's code. For each report it writes a short title, its advice in plain words (the likely cause and what to do) and an instruction for the maker's own AI ("Show the prompt Toolcrow wrote").
• Reports with the same cause are grouped: the advice says so, and "This fix also covers" lists the other reports, so one fix can close several.
• The advice is a starting point, not a change: Toolcrow does not edit the drop. The maker's AI makes the change as a draft and the maker publishes it.
• Toolcrow pays for this AI. It runs at most once every few minutes per drop and only on open reports.

Fixing a report with the maker's own AI

"Fix with your AI" opens a new chat in the maker's connected AI app (Claude or ChatGPT) with a prompt: the drop, the selected reports with their ids, Toolcrow's analysis, and the steps. With the maker's AI connected to Toolcrow (see Connecting your own AI), that AI reads the code, prepares a fix as a draft linked to the reports it fixes, and the maker reviews it, confirms which reports it closes and publishes it (see Versions, backups and drafts). "Copy prompt" copies the same prompt. Toolcrow does not pay for or run the maker's AI.

Emails

• When something breaks (a Google connection is lost, the connected Sheet is gone or in the trash, or the built-in storage is full, so what people send is not being saved), Toolcrow emails right away: one email per account, at most once a day, listing every tool that broke. This one cannot be turned off.
• The summary email: one email for all drops, weekly (the default) or daily, and only when new feedback came in since the last one. It lists what is still broken, the new feedback (with Toolcrow's title for each report), and what is waiting on the maker. Every line links to the item in Nest.
• There are no other feedback emails: no email per bug, no email when the maker's AI prepared an update, and no email per request. Those are in Nest and in the summary.
• The summary is set under Account, Notifications: weekly, daily or off, which drops are included, and "Send me a test summary".
• What's new: also under Account, Notifications, a switch for an email when Toolcrow itself ships something new (the items on the What's new page). It is off until the maker turns it on, and every such email has a link to turn it off again without signing in.