Send feedback to the team
submit_feedbackSign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. Send feedback about Avokata to the team that builds it: a bug, a wrong answer, missing data, a missing feature, a workflow idea, or praise. Every item is read by a person. When to offer it: an answer came back empty or wrong; the user corrected you or the result; a workflow was missing a step the user needed; the user repeats a manual step the service could do for them; the user says they need something the service does not do. Offer once, in one sentence; the user's task comes first. Ask first. Show the user what you will send and send it only after they agree. Their own words, and any client, case, company or personal detail, go only with their explicit OK; then set confirmed=true. With authored_by='agent' you may report your own observation of the service (the tool, what you expected, what came back) without asking, as long as it holds none of the user's words or confidential content. Fill kind and what (the task, and what went wrong or what is needed). For a wrong answer add expected and got. Add tool and query for context (the query only with the user's OK), severity, and contact_email only when the user wants a reply. Length: what up to 50,000 characters; expected and got up to 20,000 each; query up to 5,000; 80,000 for one item in all. A detailed analysis with context, evidence and proposals is welcome in one item; longer than that, send numbered parts (1/n, 2/n ...), each a complete item. The reply carries a reference id. Tell the user it reached the team; do not promise a reply or a date.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| got | No | For a wrong answer: what came back instead (up to 20000 characters) | |
| kind | Yes | One of: bug (something failed or errored), wrong_answer (an answer was returned but it was wrong or misleading), missing_data (a document, record or source the user expected is not covered), missing_feature (something the user needs that the service does not do), workflow_idea (a step, sequence or repeated manual task the service could handle), praise (something that worked well and should be kept), other (anything else) | |
| tool | No | The tool the feedback is about, if one (e.g. the tool that answered wrongly); several: comma-separated | |
| what | No | The task and what went wrong or what is needed (3-50000 characters) | |
| query | No | The query or arguments that produced it; only with the user's OK (up to 5000 characters) | |
| message | No | Older name for `what`, kept so earlier callers still work; prefer `what` | |
| session | No | The `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key. | |
| expected | No | For a wrong answer: what the right answer or result would have been (up to 20000 characters) | |
| severity | No | low | normal | high | blocking (blocking: the user cannot do their work) | |
| confirmed | No | true once the user approved sending this; required for authored_by user or agent_drafted | |
| authored_by | No | user (their words) | agent_drafted (you wrote it, they approved) | agent (your own observation) | |
| workflow_id | No | When the feedback is about a workflow (did it work, what was missing): its `workflow_id`, so the item is linked to it. Ask the user before sending; nothing else about the workflow is sent. | |
| contact_email | No | Only if the user wants a reply: the address to reply to |