NEXO · Technical support agent
Support that connects knowledge, diagnosis and human follow-up
A custom-code prototype for a support agent: documented guidance, escalation rules and a reviewable ticket draft. Explore the interface and the code behind each step.
Own prototype · Custom code · Guided demo
What problem would it solve?
Support teams often receive incomplete requests and repeatedly explain the same checks. The proposed agent organizes the enquiry, consults approved information and hands a specialist a structured case when needed.
Knowledge with a source
The sample knowledge base links each answer to an article. Unknown topics go to human review.
Escalation by impact
An issue affecting the whole team or unresolved after initial checks prepares a specialist handoff.
A useful ticket
The draft contains the topic, impact, checks and source. The GitHub adapter shows how it could be submitted.
01 / User experience
Explore the prototype
The interface executes local business rules with sample data. Its responses are guided; AI inference and external services are not active.
NEXO/ Technical support
Custom software · Interactive prototype
Choose a scenario
Sample customer
I can't access my workspace. How can I get back in?
NEXO · Guided response
Let's review the steps in the access guide.
- Check that you are using the email address that received the invitation.
- Request a new link from “Recover access”.
- Open the most recent link in the same browser.
Execution trace
Request structured
Topic and impact come from the selected scenario.
Knowledge consulted
KB-001 · Approved sample article
Documented guidance
Steps are taken from the local knowledge base.
Case context
- Source
- KB-001
- Priority
- Normal
- GitHub Issues API
- Adapter only
Guided scenarios with sample data. Rules run in your browser; no AI model or external account is connected. Reset clears this demo.
The automation, step by step
- 01
Structured request
- 02
Knowledge lookup
- 03
Impact rules
- 04
Guidance or handoff
- 05
Reviewable draft
02 / Behind the interface
Real code, with each connection explained
These excerpts are extracted from this project's source files at build time. Each tab identifies whether the code runs in the demo or belongs to an adapter awaiting connection.
Runs in the demo
The selected scenario provides structured input. This function looks up the article and decides when human review is needed.
export function triageSupport(
request: SupportRequest,
articles: KnowledgeArticle[],
): { article?: KnowledgeArticle; action: "guide" | "handoff"; ticket?: TicketDraft } {
const article = articles.find(item => item.topic === request.topic)
const needsHuman = !article || request.impact === "team" || request.alreadyTried
if (!needsHuman) return { article, action: "guide" }
return {
article,
action: "handoff",
ticket: {
title: `[${request.topic}] Support review`,
priority: request.impact === "team" ? "high" : "normal",
body: JSON.stringify({ topic: request.topic, impact: request.impact,
alreadyTried: request.alreadyTried, knowledgeSource: article?.id ?? null }, null, 2),
},
}
}
Connections and implementation status
| Component | Responsibility | Current status |
|---|---|---|
| Knowledge base | Local sample articles | Implemented in the demo |
| Ticket preparation | Typed draft and impact rules | Implemented in the demo |
| GitHub Issues REST API | Server-side submission adapter | Prepared; no account connected |
| AI model | JSON Schema tool contracts | Designed; no model connected |
API references reviewed on 21 October 2026: GitHub Issues REST API
