I built an AI support-agent prototype and realized the hard part is not the chatbot it is the handoff and audit trail. Looking for critique from people who run support/CX workflows.
Summary
The author built RelayOps, an AI support agent prototype for telecom/subscription support, and shares results from a 50-ticket sample, seeking critique on handoff records, unsafe actions, audit fields, and usefulness for testing.
Similar Articles
I built a control plane for AI support agents instead of another chatbot — looking for architecture feedback
The author describes RelayOps, a prototype control plane for AI support agents that emphasizes a separation of concerns where the model proposes actions, a broker decides, and human approval is required for high-risk actions, seeking feedback on the architecture.
I tried building a support agent and the handoff was where everything got weird
A developer shares experience building a customer support AI agent, highlighting that the human handoff and state management are the hardest parts, not the conversational ability.
Need brutal feedback: I built a recorder for AI agent runs
A developer built agentproof-recorder to record AI agent runs and detect rule violations, seeking feedback on whether this is a common pain point.
Experience sharing: building an AI Agent to Triage GitHub, Discourse, and Email (A Real-World Use Case for OSS Maintenance)
The author shares a case study on building an AI agent for Seafile that triages support requests across GitHub, Discourse, and Email by synchronizing knowledge and providing actionable suggestions to maintainers.
I built an AI support agent where the main metric is unsafe auto-action rate, not just accuracy
A technical walkthrough of building a telecom customer support agent that prioritizes safety metrics over classifier accuracy, using a deterministic access gate, scoped tool execution, and route-level evaluation.