Duaer

Office tasks

Route support tickets by department and urgency with Duaer

In Duaer, each support message goes to Duaer Judgment, which picks a department and urgency, then routes it to the right channel.

Build the ticket triage flow in Duaer

  1. Add an entry: Form Trigger for a web form, Webhook for your help desk, or Email Trigger (IMAP) for a support inbox.
  2. Add Duaer Judgment, pick TypeSafe Jev under Model, and set Text to the message body, such as {{ $json.message }}.
  3. Under Questions add two: department, Type Choice, Options one per line: support: How to use the product, billing: Payments and invoices, sales: Buying questions, engineering: Bugs and errors, other: Anything else; urgency, Type Score, Levels one per line from low to high: low, medium, high, critical.
  4. Duaer Judgment outputs only its verdict. Add Merge with Input 1 from the entry node and Input 2 from Duaer Judgment, Mode Combine, Combine By Position.
  5. Add Switch on {{ $json.judgment.department }} with five outputs: support, billing, sales, engineering, other.
  6. On each output add Slack or a WeCom group bot, with {{ $json.judgment.urgency }} and the message {{ $json.message }}.

Values from Duaer ticket triage

  • judgment.department: a key from Options, such as billing.
  • judgment.urgency: low, medium, high, or critical.
  • answers: the probability of each option; send close calls to a person for review.

Add an If for critical to page someone. Each message is one Duaer Judgment call at the selected model’s price in AI credits. Refer to Duaer plans and credits.

Questions

Can Duaer ticket triage use my own department names?

Yes. The departments are the keys and descriptions you write in the department question’s Options; update the Switch rules to match.

Does Duaer ticket triage need a model API key?

No. Duaer Judgment needs no credential and charges your AI credits at the selected model’s price.

In this section