Skip to content
Picaro.AI Picaro.AI Prompt Library

Send feedback and support requests

On this page you can send inquiries about how to use Picaro.AI, along with requests, improvement suggestions, and bug reports for the tool, straight to the dev team through your AI agent. There’s no need to open a dedicated form — it reaches the team directly from your conversation. You can also check the status of the feedback you’ve sent so far.

About this page

Section titled “About this page”
ItemDetails
What you can doSend bug reports, feature requests, and improvement suggestions to the dev team, and review a list and status of the feedback you’ve sent
Applies toFeedback about the Picaro.AI product (tool defects, usability, feature requests). Ad settings and ad data are out of scope
Data & connection neededA connected Picaro account (MCP connection)
ScopeSending and viewing. Prompt 1 sends to the dev team (an external send that cannot be undone); Prompt 2 views the list of what you’ve sent (read-only). Does not change any ad settings

When to use this

Section titled “When to use this”
  • You’ve found a defect (bug) while using the tool and want to report it to the dev team
  • You want to share a “it’d be handy if…” request or improvement suggestion
  • You have a question about how to use the tool
  • You want to check where a piece of feedback you sent earlier now stands (in progress or done)

Before you run

Section titled “Before you run”
  • Sends cannot be undone … Prompt 1 is an external send to the dev team. Because it can’t be canceled or deleted after sending, review the content before you send it.
  • Keep personal information to a minimum … the contact email is optional. Do not write secrets such as passwords or access tokens in the details field (strings that look like access tokens or API keys are masked automatically before sending).
  • Adding reproduction steps speeds things up … for defect reports, writing the reproduction steps, expected behavior, and actual behavior helps the dev team respond faster (see “How to write good feedback” below).

Prompt cheat sheet

Section titled “Prompt cheat sheet”
GoalWhat you learn / getChangesPrompt
Send a bug report / feature request / improvement suggestionA reference number and its statusSends to the dev team (cannot be undone)Prompt 1
Check the status of feedback you’ve sentA list of what you’ve sent and each item’s statusNo change (read-only)Prompt 2

Prompt 1: Send feedback

Section titled “Prompt 1: Send feedback”

Deliver a bug report, feature request, or improvement suggestion straight to the Picaro.AI dev team through your AI agent.

When to use — when you want to report a defect you’ve found, or share a feature request or improvement suggestion.

What you need — the type (bug report / feature request / other), a one-line summary as the title, and the details. The contact email is optional.

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

What you can change — the type (bug report / feature request / other) / the title and details / whether to include a contact email.

What you get back — a confirmation message with a reference number (e.g., FB-2026-0518-001) and its status (Received). The Picaro version, account information, and send timestamp are attached automatically, and strings that look like access tokens or API keys are masked automatically before sending.

Changes — sends to the dev team (cannot be undone after sending). Does not change ad settings.

Next steps — you can check the status after sending, by reference number, with Prompt 2.

Prompt 2: Check past feedback

Section titled “Prompt 2: Check past feedback”

Review a list of the feedback you’ve submitted so far, along with the current status of each item.

When to use — when you want to check whether a piece of feedback you sent earlier is in progress or done.

What you need — nothing (everything can be shown). Specify filter conditions only if you want to narrow by type or status.

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

What you can change — the type filter / the status filter (both optional).

What you get back — a list of reference number / type / title / status / send date (the most recent 5 to a few dozen items). Items marked Resolved or Not pursued this time include a comment from the dev team.

Changes — no change (read-only). Viewing the list only; you cannot edit or delete feedback.

Next steps — if you have something more to add, send it as new feedback with Prompt 1.

How to write good feedback

Section titled “How to write good feedback”

To help the dev team respond quickly, it helps to include the following:

  • Reproduction steps as a bulleted list (a numbered list is ideal)
  • Account / product / keyword IDs (when the issue is specific to those)
  • “It’d be handy if…” level requests are welcome too — the team decides on implementation priority
  • Screenshots aren’t needed, since submission goes through the AI. Please describe the situation in writing

If something isn’t working, also check the Troubleshooting page. For regular feedback, sending it through the prompts on this page is the fastest path.

Section titled “Related”