Skip to content

Build1 publisher2 min readPublished

Aderant's hourly Nova Lite job routed 109 support tickets with about 96% accuracy

Aderant's ticket analyzer, one Lambda calling Amazon Nova Lite each weekday hour, routed 109 tickets at about 96% accuracy for under $30 a month. The build is small enough to copy, but four misses in 109 tickets is a thin base for a rate another team should plan around.

The Engineer · Build desk

Illustration accompanying Aderant's hourly Nova Lite job routed 109 support tickets with about 96% accuracy

What happened

  • Aderant built a ticket analyzer on Amazon Nova Lite for its 38-person SierraOps team, which runs Expert Sierra across 268 client environments.
  • Each run pulls unassigned Jira tickets and adds Athena client data, Confluence and SharePoint documents, and similar resolved tickets before the model classifies them.
  • Tickets above a configured confidence threshold are reassigned automatically, the rest go to a human, and the team reviews routing corrections every week.
  • Between June 30 and July 17, 2026, the analyzer reviewed 109 tickets and routed about 96% of them correctly.
  • Aderant estimates the system recovers 8 to 14 engineering hours a week for a total operating cost under $30 a month.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint Hourly weekday runs leave a new ticket unrouted for up to an hour, or over a weekend if filed Friday night. Urgent incidents need a separate path.
  • exposure A misroute the model is confident about skips human review and sits in the wrong queue until the receiving team or the weekly review catches it. The analyzer was built to shorten exactly that delay.
  • decision A team choosing its first LLM automation can pick triage and check the payoff within weeks, because the baseline is counted in minutes per ticket and every error shows up as a correction.

Aderant's hours estimate fits its own baseline. At 34 to 40 tickets a week and 15 to 25 minutes of investigation per ticket [10], manual triage took between 8.5 and about 16.7 engineering hours a week [1]. The claimed 8 to 14 recovered hours [9] sits inside that band. At both ends the recovered figure is below the manual one [1].

The accuracy figure rests on a smaller base. About 96% of 109 tickets is roughly 105 routed correctly and four routed wrong [2]. In a sample that size, each misroute moves the rate by almost a full percentage point [3]. Whether the number carries to another queue depends on three values the post does not state: the confidence threshold, how many teams a ticket can be sent to, and whether tickets a human checked before routing count toward the 96%.

The model choice is a result on Aderant's tickets. The team compared several foundation models on real ticket data [12]. Each model got the same ticket content, environment data, runbooks and resolution history. According to the post, Nova Lite extracted more specific resolution steps and correlated past issues better than the others [12]. For that ranking to hold on another team's queue, that team needs context of similar depth to feed in. With no runbooks or searchable ticket history, any model has less to correlate.

The build is small and well made. One Lambda function, triggered by Amazon EventBridge every weekday hour, runs all five stages [4]. Its Act stage posts analysis and acknowledgments, reassigns misrouted tickets, notifies the right Microsoft Teams channel and applies predefined actions for support-resolvable cases [6]. Metrics go to Amazon CloudWatch [5]. There is no always-on service to operate [4]. At under $30 a month in total operating cost [9], the weekly correction review is probably the most expensive part of the system.

The analyzer came after earlier AI work at Aderant, which used Amazon Quick for unified search and on-demand investigation [13]. The account is a guest post on the AWS machine learning blog, co-written by Aderant's Angela Mapes and Adam Walker [1]. One stated reason for choosing Nova Lite was that it runs inside Aderant's existing AWS environment, reducing the need for an additional external model provider or vendor contract [14].

What to watch

  • Routing accuracy over a full quarter of tickets, after several rounds of weekly prompt and routing changes.
  • Whether Aderant publishes its confidence threshold and the share of tickets routed with no human involved.
  • Whether the predefined actions for support-resolvable tickets grow from routing into closing tickets outright.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories