Feedback Triage

Classify pasted customer feedback and inspect its sentiment, urgency, and summary.

Feedback Triage turns pasted feedback into a structured list that is easier to scan and route. Its triage workflow assigns a category, sentiment, urgency, and summary while retaining the original feedback for comparison. No external customer-service connection is required for the starting template.

Triage feedback

1. Create Feedback Triage and open the app.
2. Paste the feedback into its input area. Preserve enough original context to distinguish a request, a problem report, and a general comment.
3. Choose Triage feedback and wait for the workflow to finish.
4. Review the returned rows and select a feedback item to inspect its detail.

The category filter includes All categories, bug, feature request, complaint, praise, and question. Use it to focus the result list. A filter changes what you see; it does not rerun classification or delete other categories.

Interpret the labels

A category captures the main intent, sentiment describes the tone, and urgency estimates how soon the item merits attention. These are generated labels rather than a customer’s explicit priority setting. Compare them with the original text, especially for sarcasm, mixed praise and criticism, brief messages, or missing context.

The summary should help you scan the item without losing its concrete request. Use the original text when responding to a customer or opening a work item. If one message contains several distinct issues, adapt the workflow or split the input deliberately instead of assuming one row captures every issue.

Customise the workflow

Open the app’s triage workflow to change the classification instructions or output fields. Keep the category values aligned with the interface filter and table bindings. If you add a category to the model output but leave the filter options unchanged, that category may only be visible through the unfiltered view.

To connect a feedback source, replace or extend the pasted-input source with a suitable records connection. Validate the mapping and preserve identifiers that help trace a row back to its source. Add an external write step only when you intend to create tickets or update another service; the starting classification result does not itself create a support response.

If results are absent, inspect the selected run, input records, and model budget. Repeating a successful request can spend budget again and can produce different classifications.

Parameter reference

These are the starting template’s declared parameters. Your saved app can have its own version of the schema. A default applies when no explicit value is supplied; a required field still needs a valid value.

• title: exposed as an app interface parameter.

Connection slots

Choose compatible saved connections for user-supplied slots. Managed slots are supplied by Strive. Disabling an optional slot stops its use without necessarily deleting the saved binding. See connector policy.

Included workflows

Inspect the saved app’s workflows for changes made after creation. A workflow’s presence does not mean that every interaction runs every workflow.

Output format: feedback_item

One piece of customer feedback as triaged: the text, its category, sentiment, urgency (1 low to 3 high) and a one-line summary.