Support & Feedback

Inquiries, feature requests, improvement suggestions, and bug reports for Picaro.AI can be sent directly to the dev team through the AI agent. No need to open a dedicated form — feedback travels straight from a Claude or ChatGPT conversation to the team.

When to use this category

“It is not working as expected — want to report it.”
“This feature would be useful to have.”
“Want to share a usability friction point.”
“Want to check on a previously submitted piece of feedback.”

Prompt 1: Send feedback

🎯 Purpose

Deliver a bug report, feature request, or improvement suggestion directly to the Picaro.AI dev team via the AI agent. No separate form or alternate channel required.

📋 When to use

A tool is not behaving as expected, or an error appeared
A “this feature would be useful” moment shows up mid-task
Want to share a usability rough edge or behavior that should change
A small annoyance comes up during operations and should be logged before it is forgotten

📝 Prompt

Send feedback:
- Type: Bug report / Feature request / Other
- Title: <one-line summary>
- Details: <reproduction steps, expected behavior, actual behavior, etc.>
- Contact email: <optional, if a follow-up is desired>

⚙️ What the AI does

Sorts the input Checks that Type, Title, and Details are all filled in before sending. Why: the dev team needs these minimum fields to triage and route the feedback quickly.
Auto-attaches context The following items are added automatically — no extra input required:
- The version of Picaro.AI in use
- The account being operated on
- Send timestamp
Why: in bug reports, “which environment did this happen in?” is critical for reproduction, so this skips manual entry every time.
Registers the feedback Posts directly into the dev team’s feedback tracker. Why: it is less prone to drop-off than email and easier to follow up on later.
Confirms the follow-up channel When a contact email is included, the entry is registered so that individual follow-up is possible when the case is resolved. Why: this serves the “want to know later when it is fixed” need.
Returns a send confirmation Replies with a ticket number and current status (Received). Why: it confirms on the spot that the report was delivered.

📊 Example Output

Feedback submitted.

Ticket #: FB-2026-0518-001
Type    : Bug report
Title   : N-gram analysis results come back empty
Status  : Received (awaiting triage)
Sent at : 2026-05-18 14:32

Thanks for the report.
The dev team will review the contents and follow up.
Since a contact email was provided, a direct message
will go out when the issue is resolved.

🔒 Safety guards

Auto-masking of sensitive data: anything in the Details field that looks like an access token or API key is masked before sending.
Email format validation: malformed contact emails are flagged before send, to avoid a follow-up that never arrives.
Pre-send preview: the exact body the dev team will receive is shown before sending. If unintended information appears, the send can be canceled.

🚦 Execution mode

One-shot (conversational logging). Submission wraps up in one or two turns while details are confirmed. This is not a background or long-running process.

👉 Next steps

To track the status afterward, use Prompt 2: Check past feedback on this page.
For urgent bugs or outages, reach out directly via the Support contact at the bottom of this page.

❓ FAQ

Q. Can screenshots be attached? A. Not at the moment — submissions go through the AI agent, so image attachments are not supported. Describing the error message, the on-screen text, and the operation flow in writing conveys roughly the same amount of information to the dev team.

Q. Is it OK to send the same content multiple times? A. No problem. The dev team consolidates duplicates. Sending each time something is noticed often speeds up response, since more context arrives.

Q. Unsure whether to pick “Feature request” or “Other”? A. “Other” is fine when in doubt. The team re-classifies after receipt.

Prompt 2: Check past feedback

🎯 Purpose

Show a list of feedback previously submitted by the current user, with the current status of each item.

📋 When to use

Want to know how a previously submitted piece of feedback is being handled
Want to check whether a reported bug has been fixed
Want to see whether a feature request has been marked Resolved or Not pursued this time
Want to review recent submissions

📝 Prompt

Show the list of feedback I have submitted:
- Filter by type: Bug report / Feature request / Other (optional)
- Filter by status: Received / Under review / Resolved / Not pursued this time (optional)

⚙️ What the AI does

Identifies the sender Pulls only the feedback submitted by the user currently operating the agent. Why: by design, feedback from other users is not shown — privacy must be preserved.
Applies filters When specified, narrows by type and status. Why: as the list grows, this keeps the focus on the topics that matter right now.
Attaches a status label Each item shows one of Received / Under review / Resolved / Not pursued this time. Why: this conveys the dev team’s progress without internal jargon.
Pulls in response comments For items marked Resolved or Not pursued this time, the dev team’s comment (fix details, reason for not pursuing, etc.) is shown alongside. Why: knowing “why this outcome” — not just the outcome — helps shape future requests and related tickets.
Read-only display This list is for viewing only — editing and deletion are not available from this prompt. Why: past exchanges are intentionally preserved as a record.

📊 Example Output

Feedback you have submitted (most recent 5):

| Ticket #          | Type            | Title                                       | Status                 | Sent       |
|-------------------|-----------------|---------------------------------------------|------------------------|------------|
| FB-2026-0518-001  | Bug report      | N-gram analysis results come back empty     | Received               | 2026-05-18 |
| FB-2026-0502-014  | Feature request | Add a "nighttime only" mode to bid tuning   | Under review           | 2026-05-02 |
| FB-2026-0420-007  | Bug report      | KPI target display disappears after save    | Resolved               | 2026-04-20 |
| FB-2026-0405-003  | Other           | Persist report sort order                   | Not pursued this time  | 2026-04-05 |
| FB-2026-0322-011  | Feature request | Bulk-edit labels on competitor ASINs        | Resolved               | 2026-03-22 |

[Resolved] FB-2026-0420-007:
  Dev team comment:
  "Fixed the reload timing on the save handler.
   Shipped in the 2026-05-10 update."

[Not pursued this time] FB-2026-0405-003:
  Dev team comment:
  "Based on current usage patterns, frequency was judged
   too low. Exploring an alternative approach instead."

🔒 Safety guards

Other users’ feedback hidden: only items submitted from the current account appear.
Read-only: editing and deletion are unavailable through this prompt, to prevent tampering with the record.
Contact email masked: the registered contact email is partially masked in the list view.

🚦 Execution mode

One-shot (immediate display). List retrieval only — no background monitoring or continuous execution.

👉 Next steps

To submit a new piece of feedback, use Prompt 1: Send feedback on this page.
When adding more information to an existing topic, send it as a new piece of feedback and include the previous ticket number in the body — the dev team can then link the items.

❓ FAQ

Q. Is there a cap on how many items appear? A. By default, the most recent several dozen items appear. To view older records, apply a date range or type filter.

Q. The status has been “Under review” for a long time. A. Some items require time for reproduction or design discussion. To check on a long-running case, send a new piece of feedback saying “Please share the status of FB-XXXX”, or reach out via the Support contact at the bottom of this page.

Prompt cheat sheet

Goal	Prompt to use
Send a bug report / feature request / improvement suggestion	Prompt 1
Check the status of past feedback	Prompt 2

How to write effective feedback

To help the dev team respond quickly, please include the following when possible:

Reproduction steps as a bulleted list (a numbered list works best)
Account / product / keyword IDs (when the issue is specific to those)
“Would be nice if…” level requests are welcome — the team handles prioritization
Screenshots are not required at this stage (submission goes through the AI). A written description of the situation is enough

Support contact

For urgent inquiries, please use the contact form.

For regular feedback, sending it through the prompts on this page is the fastest path.