Sent Feedback

Use feedback.send only when the user asks to pass feedback to Sent or accepts your offer to report friction, and only after they explicitly authorize the exact sanitized report. Never send unsolicited reports, conversation transcripts, or automatic feedback after a tool error.

Offer feedback after meaningful friction

Sent wants to hear about friction even when the user would not think to report it. During any Sent workflow, notice meaningful friction that you or the user hit: missing functionality, an error that persists after diagnosis, confusing or contradictory results, repeated workarounds, or user frustration with Sent.

1. Diagnose the friction and try to resolve it first with the skill that owns the task.
2. If it remains meaningful, keep the original task first. At a natural pause or after answering, offer once in one sentence, for example: "Sent has no tool to cancel a scheduled send; want me to draft a feedback report for the Sent team?" Never hold the task on the answer.
3. Do not offer for routine errors you resolved, expected restrictions such as validation, permission, compliance, balance, or rate limits working as documented, problems unrelated to Sent, or an issue already offered in this conversation. If the user declines or ignores the offer, drop it.
4. Accepting the offer permits a draft, not a send. Prepare the report below and send only after confirmation.

Prepare an authorized report