Request classification and routing
I build automation that classifies each inbound request, routes it by role, and holds risky changes for human approval.
Try it
Paste an inbound request, such as a support ticket, and a demo model returns the same JSON contract my pipeline uses. The page shows the parsed fields, the routing decision, and whether the task would wait for human approval.
How it works
- Map the inbound flowI sample real requests with the team and agree on the labels, the required fields, and the route for each label. Every sample enters through the public intake API on api.onluca.ai, POST /api/requests, which returns a stable request id.
- Pin the output schemaI write the strict JSON contract first: intent, kind, risk, effort estimate, suggested role, and approval flag. A regex fast path labels the obvious requests, and I call the model only when confidence falls below 0.75.
- Validate the outputI check every field before routing: risk must match its allowed values, and effort estimates are clamped to a fixed range. A failed model call falls back to medium risk with human approval required, so it fails closed.
- Plan and routeThe dispatch loop classifies the request, then the planner I build writes a bounded task envelope. Each envelope names the agent role, the paths it may touch, and the checks it must pass. Read-only questions close as an answer instead of opening work.
Tools
| Tool | What it does here | Status |
|---|---|---|
| Agent dispatcher and planner | Captures each inbound request, classifies intent and risk into the JSON contract, then writes bounded task envelopes for workers. | Early access |
| Agent runtime and tool bridge | Runs one routed task inside its envelope, calls only the tools that role allows, and reports status back. | Available |
| CRM sales automation engine | Runs event-triggered workflows with conditional steps and templates, and stores each step result, error, and duration. | Available |
| Policy engine approvals and audit | Parks a gated action until a named approver with the required capability decides, then writes that decision to the audit trail. | Early access |
| Demo classifier on Workers AI | Returns the same JSON fields my pipeline uses, so a visitor sees real classification output without an account. | Demo only |
Available means shipped and in use. Early access means built but not generally available. Roadmap means designed, not built. Demo only means it powers this public demo, not customer deployments.
The full write-up covers access control, evaluation and how this runs inside a customer environment.
Read it on gusit.deThe other answers
Gus IT LLC. Contact gus@gusit.de. Claude is a product of Anthropic PBC. Cloudflare and Workers AI are trademarks of Cloudflare, Inc. Llama is a trademark of Meta Platforms, Inc. Other names are trademarks of their respective owners. Gus IT LLC is an independent engineering firm and is not affiliated with or endorsed by these companies.