Agents Lookup

Use cases / Decision models (Jev)

Match client requests to the right open issue

Each week, have Jev match every client request to an existing GitHub issue, sending low-confidence matches to a person.

DifficultyIntermediate
Setup time4-8 hours
CategoryDecision models (Jev)

Author's figure: Author's figure: matched Opus accuracy on 40 requests, decisions 150x cheaper, 5 bad matches stopped by reviewers (Akshay Pachaar). Reported by the builder, not measured by us.

The use case

Agencies and product teams collect client requests from email and calls, then lose time working out whether each is already tracked. This agent takes each request and asks Jev to choose the matching GitHub issue from the open list, or none. Confident matches get linked and the client gets a status update drafted from the issue; low-confidence ones go to a person. In the author's test, reviewers still caught a handful of wrong matches, which is why the review step stays. A project manager approves any message to the client.

Example workflow

  1. Collect client requests from email or a form into a weekly batch
  2. Fetch open issues from GitHub
  3. Ask Jev a Choice question over issues plus a none option
  4. Link confident matches and queue low-confidence ones for review
  5. A project manager approves client updates before sending

Tools

Risks and guardrails

Sources

Written by Agents Lookup. Credits and official pages for the tools this use case names: