Hans Wang

Hans Wang

Enterprise-Level Customer Service Agent

About

I am the creator of TeliChat.io, it is a code-first, white-box conversational agent designed for enterprise customer service and complex business processes. It is neither a ReAct Agent that lets the LLM run freely, nor a rigid Workflow Agent. Instead, it manages multi-turn conversation state through "ChatTree + InfoItem + Python code."

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Maker History

  • TeliChat
    TeliChatCode-centric white-box conversational agent
    May 2026
  • 🎉
    Joined Product HuntJuly 9th, 2025

Forums

Why ReAct Agents and Workflow Agents Fall Short for Customer Service and Complex Business Processes

The issue is not that they are "not intelligent enough." The real problem is that their engineering paradigms make it difficult to satisfy several core requirements of enterprise-grade customer service at the same time: non-linear conversations, smooth interaction, fast response times, strict rule enforcement, traceability across long conversations, and debuggability for complex business logic.

Let's start with ReAct Agents.

A typical ReAct Agent allows the large language model to autonomously decide, through multi-step reasoning, what to do next, which tools to call, and how to move the task forward. This looks flexible, but in enterprise customer service scenarios, it quickly exposes several problems:

- It behaves more like a black box, making its actions difficult to fully predict;

Hans Wang

17h ago

TeliChat - Code-centric white-box conversational agent

Users don't talk in workflows. They change their minds, provide information out of order, jump across topics, and interrupt ongoing processes. TeliChat helps teams build code-centric conversational agents that handle non-linear conversations while keeping business logic explicit and debuggable. No black-box reasoning. No rigid flows. Just natural conversations backed by code.

Why ReAct Agent and Workflow Agent Fall Short for Enterprise Customer Service

The issue is not that they are "not intelligent enough." The real problem is that their engineering paradigms make it difficult to satisfy several core requirements of enterprise-grade customer service at the same time: non-linear conversations, smooth interaction, fast response times, strict rule enforcement, traceability across long conversations, and debuggability for complex business logic.

Let's start with ReAct Agents.

A typical ReAct Agent allows the large language model to autonomously decide, through multi-step reasoning, what to do next, which tools to call, and how to move the task forward. This looks flexible, but in enterprise customer service scenarios, it quickly exposes several problems:

- It behaves more like a black box, making its actions difficult to fully predict;

View more