Why Wanderer Chatbots Don't Block and What That Means in Practice

Most chatbots work like forms in disguise. They ask a question, wait for your answer, then move on. It's a simple, linear, turn-based pattern. You'll find it everywhere. But it's also a fundamental limitation that rarely gets questioned.

Wanderer works differently. Wanderer chatbots are non-blocking, meaning the conversation keeps moving even while interactive elements are on screen. Buttons can appear, forms can be open, timers can be running, and the bot keeps talking, reacting, and adapting in parallel.

This isn't a workaround. It's a direct consequence of the underlying technology: Reactive Graph Sequencing (RGS).

The blocking problem

In a traditional chatbot builder, every interactive element acts as a roadblock. When the bot shows a set of buttons, it stops. It waits. Nothing else happens until the user clicks. The entire conversation is paused by a single UI element.

For simple FAQ bots, that's fine. But as soon as you want something that responds to time, to external events, or to multiple things happening at once, the blocking model breaks down.

In a real conversation, the other person doesn't freeze mid-sentence just because they asked you a question. They might add context, react to your body language, or change the subject entirely. Traditional chatbots can't do any of this. Wanderer can.

How Wanderer stays non-blocking

The key is how Wanderer models conversations. Instead of a linear flow that moves from step A to step B to step C, Wanderer uses a reactive graph. Every element in the conversation (messages, buttons, input fields) is a node in that graph. These nodes don't wait for each other unless you explicitly tell them to.

In practice, that means:

• A question node can display suggestion buttons while the bot continues sending messages.
• A form node with text inputs, number fields, or email fields can sit open while the graph processes other logic in the background.
• A button node can fire a short event into the graph without interrupting anything else.
• A select node can render a dynamic list of options from an array, and that list can update while the conversation moves on.
• A panel node can display rich, interactive content using Markdown and Handlebars (live data, formatted output, embedded visuals) without halting the flow.

None of these elements block the graph. They participate in it.

A concrete example: the quiz

One of Wanderer's flow templates illustrates this well: a quiz game.

The bot asks a question and presents multiple-choice answers as buttons. A timer starts counting down. So far, nothing unusual. But here's where it gets interesting:

• The 50/50 joker: Press the joker button and two wrong answers disappear from the screen instantly, while the timer keeps running and the bot keeps talking.
• Time runs out: If the user doesn't answer in time, all answer buttons vanish. The bot announces that time is up. No stale buttons sitting around, no leftover UI from a previous state.
• The bot keeps talking throughout: While buttons appear and disappear and timers tick, the bot can still send messages. It can mention how much time is left, react to the joker being used, or comment on hesitation.

In a traditional chatbot builder, this would require custom code, complex workarounds, or simply wouldn't be possible. In Wanderer, it's just nodes in a graph.

Why this matters beyond quizzes

The quiz is a useful demo, but the underlying principle has broader applications. A non-blocking chatbot can react to events that don't originate from the user.

A few examples:

• E-commerce: A product goes out of stock while the user is configuring it. The bot reacts immediately without waiting for the user's next input.
• Customer support: A live agent joins the conversation. The bot adjusts seamlessly without resetting the flow.
• IoT and real-time data: A sensor triggers an alert. The bot notifies the user mid-conversation, regardless of what they were doing.
• Time-sensitive workflows: A deadline passes, a session expires, or a price changes, and the bot adapts in real time.

None of this works in a blocking model. There, the bot is frozen, waiting for a click that might never come while conditions change around it.

The technology: Reactive Graph Sequencing

So how does this work under the hood? The answer is Reactive Graph Sequencing (RGS), a paradigm that rethinks how chatbot logic is structured.

Traditional bots are event-driven: something happens, then the bot decides what to do next. RGS is state-driven: the graph continuously evaluates the current state of the entire conversation and determines what should be happening right now.

Concretely:

• Nodes can activate and deactivate based on conditions, not just user input.
• Multiple branches of the graph can be active simultaneously.
• UI elements appear and disappear as the state changes, with no cleanup code and no leftover artifacts.
• The graph can re-sequence itself when conditions change.

All of this happens visually, in the browser, without writing code. You connect nodes, define conditions using Must/May/Not edges, and the graph handles the rest.

Non-blocking as architecture, not feature

Most chatbot builders treat non-blocking behavior as an edge case, something you patch in when the default flow isn't enough. In Wanderer, non-blocking is the default. It's not bolted on top; it's built into the architecture.

Every node is independent. Every node is reactive. Every node can respond to state changes from any source: user input, timers, external events, other nodes. The graph doesn't block because there's nothing to block. There's no single thread of execution waiting for a response. There's a graph that reacts to the world as it changes.

That's why Wanderer chatbots feel different. They don't wait, they don't freeze, and they don't leave stale buttons on the screen. They move with the conversation and with everything happening around it.

Wanderer is a visual chatbot builder powered by Reactive Graph Sequencing. Build non-blocking, reactive conversations without code. Learn more at wanderer-flow.de.

Title image: https://unsplash.com/de/fotos/ein-kleiner-wasserfall-mitten-im-wald-LTDMP9v21cc