user_existsboolean required
user_emailstring required
user_countrystring nullable required
user_gradestring nullable required
school_namestring nullable required
source'user' | 'attio' | 'store' | 'admin'
Where the feedback came in through.
origin'widget' | 'chat_answer_report' | 'rating_prompt'
Which door of the app a user feedback came through.
Both are written by the person they belong to, so they share the user
source and the inbox; what differs is what the team has to read. A widget
message is the user's own words. A chat answer report is one click under
a chat answer (EXC-796): the text is ours, the question and the answer
are what to look at.
nature'misunderstanding' | 'bug' | 'suggestion'
What kind of feedback it is, which is also how it gets triaged.
A dysfunction of what exists is a bug and goes down the fast lane;
everything that changes or adds behaviour waits for the weekly review.
image_urlsstring[] required
status'new' | 'in-progress' | 'waiting-user' | 'done' required
timestampstring date-time required
last_status_changed_bystring nullable required
last_status_changed_by_namestring nullable required
status_changed_atstring date-time nullable required
user_feedback_historyobject[] required
screenshot_urlstring nullable
diagnostics_captured_atstring date-time nullable
owner_namestring nullable
owner_assigned_by_namestring nullable
owner_assigned_atstring date-time nullable
user_last_read_atstring date-time nullable
resolved_by_user_atstring date-time nullable
origin_pageobject nullable
assistant_chat_idstring nullable
chat_answer_reportobject nullable