DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to route support tickets to the right team with fixed choices with Type LLM

Assign each incoming ticket to one team from a fixed list, with a description for each choice.

Who it is forA support lead whose tickets arrive unsorted and who needs each one assigned to billing, technical, shipping or another queue without invented team names.

The problemModel answers can name teams that do not exist, which sends tickets to queues nobody watches.

The outcomeEach ticket gets exactly one queue value from the list you define, so the routing step only sees valid teams.

What you need first

  • Python with pip installed
  • A TypeLLM API key from typellm.ai (includes $5 free credit), or a GPU server running SGLang with a compatible model such as Qwen3.8-27B
  • Documents or text to process, and a list of the fields you want back

Steps

  1. Run pip install -U typellm
  2. Run export TYPELLM_API_KEY="tl-sk-..." or start your SGLang server and pass its URL to TypeLLMClient
  3. Define a queue question with type string and a choices list where each item has a value and a description
  4. Call generate() with the ticket text as context for each ticket
  5. Send each ticket to the queue named in response.result

Prompt for your agent

In the TypeLLM/TypeLLM repo, call TypeLLMClient.generate() on each ticket in <tickets_file> with a queue field whose choices are billing, technical, shipping and other, each with a description. Return a list of ticket IDs with their queue. Verify that every queue value is one of the four choices.

Caveat. The README says choices take optional descriptions and that enum allows 2 to 26 values, so keep your team list inside that range.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page