Ticket subject
textRequired input
Noderan MarketplaceCustomer Support
Support Ticket Router
Makes routing decisions explainable with matched rule evidence.
Route tickets by subject, category, priority, and keyword rules.
Workflow summary
Route tickets by subject, category, priority, and keyword rules.
What is Support Ticket Router?
Support Ticket Router is a ready-to-run Noderan marketplace workflow for customer support teams. It helps users move from a manual process to a repeatable automation with visible credit cost and app-based execution.
- Who is it for?
- Support operations and customer success teams
- What problem does it solve?
- Route tickets by subject, category, priority, and keyword rules.
- How does it work?
- Route tickets by subject, category, priority, and keyword rules.
- How does pricing work?
- 1 credit per run.
- What is the next action?
- Open the app marketplace to activate this workflow, or review credit pricing.
Support Ticket Router FAQ
Short answers for activation, pricing, inputs, and execution review.
Makes routing decisions explainable with matched rule evidence.
Expected inputs
Category
selectRequired input
Options: billing, technical, account, general
Priority
selectRequired input
Options: low, medium, high, urgent
Ticket description
textareaRequired input
Example input
Subject
Urgent refund requestDescription
The customer was charged twice and needs a refund.Category
billingPriority
urgentView raw JSON
{
"subject": "Urgent refund request",
"description": "The customer was charged twice and needs a refund.",
"category": "billing",
"priority": "urgent"
}Output highlights
- assigned team
- queue
- matched rules
Example result
Assigned Team
Billing OperationsQueue
billing-urgentPriority
urgentMatched Rules
Billing categoryRefund keywordUrgent priority
View raw JSON
{
"assignedTeam": "Billing Operations",
"queue": "billing-urgent",
"priority": "urgent",
"matchedRules": [
"Billing category",
"Refund keyword",
"Urgent priority"
]
}Use cases
- Send every support ticket to the right queue.
How it works
- 1
Review the workflow and expected credit cost.
- 2
Connect the tools or inputs required for execution.
- 3
Run the workflow and inspect outputs in the app history.