New Flow Builder and Knowledge Base are live. What changed

Configure an Order Request node

Reads the variant the flow already picked and opens an order request that waits for operator approval. Wire the created, duplicate and error branches.

Short answer

This node is a pilot, and the Chatinbox team sets it up. It opens requests only in a store whose Ticimax connection that team set up. In a store without that connection the earlier steps produce no selection, so the node cannot open a request. The node sends no payment link. It reads the selected variant and opens a request that waits for a decision; the flow continues from the exit you wired. By default an operator decides. The Chatinbox team makes Otomatik mode available on your account and sets the approval limits; you then choose Otomatik line by line on the Hatlar screen. On a line in that mode some requests can be approved without waiting for a person, and a request that is not approved waits for an operator; a request with no decision within six hours expires. The request appears on the Siparişler tab of Sohbet Gözetimi. Approve or reject it with the green check (Onayla) and red cross (Reddet) icons on its row. On a row whose address badge shows a warning, first confirm the address with the map icon (Adresi teyit et).

This page also exists in Turkish with the same scope: Türkçe okuyun

Before you start

  • An account with the Ticimax integration connected
  • A Varyant Seçimi step before this node
  • An operator who will decide on the request

Step by step

These screens sit inside the Intent AI section. Sign in, open Intent AI; the menu names below are in that section's left menu.

Add the node to the canvas

Drag the Sipariş Talebi (Order Request) node out of the Aksiyon group in the palette.

Connect it after the variant selection

That step writes the choice to the selected_variant variable.

Leave the selection variable alone

Keep the default name in the Seçim Değişkeni field.

Fill the three messages and wire the branches

Write the Talep Alındı Mesajı, Mevcut Talep Mesajı and Hata Mesajı texts, then give each output its own step.

See the request land on the Siparişler tab

Save, try it from a real line, then open the list in Sohbet Gözetimi.

Result check

If it did not work

Check these

  • If the node keeps leaving through HATA (the red-icon exit on the card) in live chats, first check that Sonuç Değişkeni in the Varyant Seçimi node and Seçim Değişkeni in this node carry the same name. If they do, contact Chatinbox support.
  • While one request is open in a chat, no second one is created; the flow takes MEVCUT TALEP (the amber-icon exit on the card). Close the open request on the Siparişler tab of Sohbet Gözetimi first.
  • The Flow Testi window never really runs this step: a simulated session carries no chat identity, so the node always takes HATA there.

Does this step look different in your panel?

We can review the screen and exact error text together.

Write to support

This guide was checked against the product UI and code inventory on 4 October 2026.

Chatinbox chatinbox

Looking into Chatinbox? I answer setup, pricing and channel questions right here.