Submit or follow up website feedback
submit_feedbackCreate feedback or append a message to your own existing feedback using feedback_id. Anonymous reports are one-way and cannot be discussed or claimed. New reports require issue_type and target_type; appends accept only feedback_id, content, source_urls and request_id. Submit user-requested corrections, missing data or other feedback on any topic to One U Education for review. Available anonymously or with a connected account; connected submissions are associated with that account. Compose stand-alone content a consultant can understand without this conversation, using known context and available sources. Do not require the report to match an editable CRM field or verify every claim before accepting it; resource classification and editing decisions belong to OneULink CRM handling. Ask only for missing facts that materially change the target, scope or meaning; do not re-ask known facts or demand exhaustive evidence. Useful incomplete leads are accepted with explicit unknowns. School/course reports require a code or name; never guess a match. Keep user claims distinct from verified facts. A receipt means received for review, not verified, accepted or corrected; submission never edits official data. This public endpoint returns English natural-language text, preserving sources, conditions and pagination.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"content": "<content>"
},
"name": "submit_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Year the report applies to, only if known. Not the submission year by default. Put terms, date ranges or multiple applicable years in content; omit this field if no single year is established. | |
| content | Yes | Stand-alone plain-text report for a reviewer who cannot see this conversation. Preserve the user's meaning and concrete facts: (1) the subject and affected scope, such as school/course, campus, intake or student group; (2) what is wrong or missing and the user-reported correction; (3) known dates, conditions and exceptions; (4) reported impact and what still needs checking; (5) available evidence, how the user learned it and when, without private contact details. Distinguish user reports from independently verified facts and keep relevant unknowns explicit, including currency/year/fee basis for prices. Do not replace specifics with vague labels such as “needs attention”. Use only supplied or actually checked information; do not invent causes, dates, sources or certainty. Concise prose or bullets are enough; do not fill irrelevant sections or include unrelated conversation/private information. | |
| page_url | No | Actual page where the issue was noticed, if known; not proof by itself. HTTP/HTTPS only. Omit unknown URLs and never include credentials or private access links. | |
| issue_type | No | Nature of the report: incorrect_data = an existing fact is reported as wrong; missing_data = information or context is missing; other = another issue. | |
| request_id | No | UUID for this operation. Reuse unchanged with identical content after an uncertain response; use a new UUID for a different operation. | |
| feedback_id | No | Existing feedback reference to append to. Requires the owning account. Omit only for a new report; never fall back to creating a report after an append error. | |
| source_urls | No | Up to 10 actual HTTP/HTTPS evidence URLs supplied by the user or found during checking; never fabricate links or include credentials/private access links. Explain what they support in content. If the source is an offline conversation or document without a shareable URL, describe that context and known date in content and omit this field. | |
| target_code | No | Known school/course CRICOS code; for course_package use the school CRICOS code. Preserve leading zeroes. Omit when unknown. | |
| target_name | No | School/course or other subject name as supplied or found in query results. Preserve it without guessing a record match; include the school in content when a course name is ambiguous. | |
| target_type | No | Choose the actual subject: school for school-wide issues or missing courses at a known provider; course for a specific existing course; website for a site issue; course_package for a multi-course packaged study plan (text and evidence links only; no attachments); other for RTO/RPL or another topic; news for school/visa news submissions (requires login and news_category). Do not widen a course-specific report to the whole school. | |
| contact_email | No | Optional email explicitly provided by the user to receive automated no-reply notifications for staff replies and resolution (anonymous reports receive resolution only). For new signed-in feedback, omitting this field uses the account email on the server. Anonymous email is optional. Never invent an address. Set notifications_enabled=false if the user declines notifications. | |
| news_category | No | Required for target_type=news. News submissions require an account connection; staff rewrite and publish the body later. | |
| attachment_ids | No | Ready attachment IDs returned by file import/upload. Original files are intended for future news downloads; do not parse or rewrite brochures by default. | |
| notification_locale | No | Language for the optional resolution email. Use the conversation language; defaults to English. No need to ask solely for this field. | |
| proposed_school_code | No | Optional proposed main school resource code; staff confirm one school. Preserve leading zeroes. | |
| proposed_school_name | No | Optional proposed main school name; do not guess a database match. | |
| notifications_enabled | No | Defaults to true for new feedback. Set false if the user declines email notifications. Cannot change via an append. |