The customer taps instead of typing
A menu of buttons instead of a conversation: a tap re-enters the same scenario and takes the right branch.
What the scenario looks like
- Execute + Data
Half the questions a bot gets are three or four recurring topics. Making a person phrase them and a model guess them is unnecessary and expensive: a button answers instantly and costs less, because no model is involved in that branch at all.
What is inside
- Message or tap — the entry. One way in for both cases.
- What was tapped — a branch on
data.telegram.command. An ordinary message leaves that field empty, so it takes the default branch. - Button menu sends a message with two command buttons and one link.
- Two branches answer a specific topic with ready text.
A button does not “navigate” anywhere: the tap re-runs this same scenario and puts its
command into data.telegram.command. That is why one branch serves both a tap and a typed
command, and why there are exactly as many branches as topics.
What to set up for yourself
- The buttons and the answers. The button list is configured on the node and is the same for everyone. A menu that differs per customer is written into the answer text, and the buttons are kept for the sections that never change.
- Command length. The caption plus the command must fit in 64 bytes — that is Telegram’s limit, not the platform’s.
- The default branch. Any text currently shows the menu. The natural next step is to put an agent with a knowledge base there, so buttons cover the common questions and the model covers the rest.
What to connect
A Telegram bot and the Telegram target on the Publish tab. Nothing else needs enabling: button taps reach a bot in a private chat by default.