2 Labels and review rules
Start from a rules preset
A preset fills the instructions and labels below. Edit either field before you run: only what those two fields show is sent.
Support classificationSelected
Route each message to the team that owns it.
Decision instructions Choose the team responsible for resolving the main customer issue.
Allowed labels, separated by commas billing, technical support, account access, feedback, other
Review threshold 0.85
SentimentSelected
Sort each message by how the writer feels.
Decision instructions Judge the overall sentiment of the writer towards the product or the service, not the topic they mention.
Allowed labels, separated by commas positive, neutral, negative, mixed, unclear
Review threshold 0.8
ModerationSelected
Flag comments a human moderator should review.
Decision instructions Choose the label that best describes the comment. Use "unclear" when the text cannot be judged, and never infer intent that is not written.
Allowed labels, separated by commas acceptable, insult, harassment, spam, unclear
Review threshold 0.9
Multi-question preset
A preset fills the questions below with typed questions a visitor can inspect and edit before running.
Support triageSelected
Route each message, flag defects and set urgency in one request.
team choice Which team should own this ticket?
billing Invoice, refund, plan or payment issue.technical Broken or unexpected product behaviour.account Sign-in, permissions or profile issue.other Anything that does not fit the three above.is_bug noul Is the writer reporting a defect in the product?
true They describe broken or unexpected behaviour.false They ask a question or request a feature; nothing is broken.urgency score How urgently does this need an answer?
0 Can wait for the next release.1 Should be answered this week.2 The customer cannot work right now.
Review threshold 0.85
Allowed labels, separated by commas
Decision instructions
Questions for each row
Every row is asked the same questions. Edit the ID, type, instructions or criteria, and the run sends exactly what these fields hold.
Add a question
Generate the rules with AI
Describe the decision you need. The model proposes the typed questions, and you review and edit them before anything is sent.
What should each row decide?
Generate rules · 1 credit
Generation costs 1 credit, and a failed generation is refunded. It is not a decision: each row still costs 1 credit, and nothing runs until you press Run.
Review threshold
Keep an "other" or "unclear" label, and review a low-confidence row before acting on it.
One completed row uses one credit. Running out of credits stops the batch, and nothing is purchased automatically. Keep this tab open and export before you leave.
Run batch
Stop after this row
Retry failed rows
Start over
Guests can run 1 row per source address per UTC day. New accounts get 20 credits; one completed row uses one credit, and nothing is purchased automatically. Sign in and keep this batch · Pricing